Difference between revisions of "SsEncrypt"
From SmartWiki
| Line 23: | Line 23: | ||
* [[Enable URL Parameter Encryption]] | * [[Enable URL Parameter Encryption]] | ||
[[Category:Variables]][[Category:Security]] | [[Category:Variables]][[Category:Security]] | ||
| + | |||
| + | <!--See 17915 - SERVER UPGRADE NOVEMBER - Save to Server displaying externally--> | ||
Revision as of 10:03, 9 December 2014
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>typeid,rootcompanyid</ssEncrypt>
Level 2 template page token
<ssEncrypt>typeid,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>
