Difference between revisions of "SsEncrypt"
From SmartWiki
| Line 1: | Line 1: | ||
| − | ssEncrypt can be used to dynamically generate an encrypted token when creating URLs to access other entities with SmartSimple. | + | 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 2 different encryption methods. Accordingly either ssEncrypt or ssEncrypt2 are used depending on which entity is involved: | ||
| Line 10: | Line 12: | ||
Webpage View token: | Webpage View token: | ||
<ssEncrypt2>objectid</ssEncrypt2> | <ssEncrypt2>objectid</ssEncrypt2> | ||
| + | |||
| + | Example: To open the [[Web Page View]] with custom field id 123456 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. This is not currently possible, but will be added in an upcoming upgrade (ssEncrypt3) | ||
| + | |||
Transaction token | Transaction token | ||
Revision as of 12:34, 3 January 2012
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 2 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>
Webpage View token:
<ssEncrypt2>objectid</ssEncrypt2>
Example: To open the Web Page View with custom field id 123456 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. This is not currently possible, but will be added in an upcoming upgrade (ssEncrypt3)
Transaction token
<ssEncrypt>userid,typeid</ssEncrypt>
