Difference between revisions of "SsEncrypt"

Revision as of 14:52, 25 June 2013

ssEncrypt and ssEncrypt2 can be used to dynamically generate an encrypted token when creating URLs to access other entities with SmartSimple.

Tokens are created using two different encryption methods. Accordingly, either ssEncrypt or ssEncrypt2 are used, depending on which entity is involved:

Level 1 template page token

<ssEncrypt>typid,rootcompanyid</ssEncrypt>

Level 2 template page token

<ssEncrypt>typid,appid,rootcompanyid</ssEncrypt>

Web Page View token:

<ssEncrypt2>objectid</ssEncrypt2>

Example: To open the Web Page View with custom field ID 123456 on a contact you would use the following syntax:

<input type=button class=Button  value="Open" onclick="_openpageview('123456','<ssEncrypt2>@userid@</ssEncrypt2>',1)" >

Note: if you have URL Parameter Encryption enabled the custom field ID must be encrypted as well using ssEncrypt3. If custom field 654321 is on a Level 1:

<input type=button class=Button  value="Open" onclick="_openpageview('<ssEncrypt3>654321</ssEncrypt3>','<ssEncrypt2>@opportunityid@</ssEncrypt2>',1)" >

Transaction token

<ssEncrypt>userid,typeid</ssEncrypt>

• Visibility Condition
• Advanced Logic
• Determining the Application ID
• Determining the Category ID
• Determining the Company ID
• Determining the Custom Field ID
• Determining the Event ID
• Determining the File ID
• Determining the Folder ID
• Determining the Opportunity ID
• Determining the Report ID
• Determining the Role ID
• Determining the Root Company ID
• Determining the Status ID
• Determining the Type ID
• Determining the User ID
• Determining the Workflow ID