Difference between revisions of "SsEncrypt"

From SmartWiki
Jump to: navigation, search
Line 1: Line 1:
 
ssEncrypt and ssEncrypt2 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:
+
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
−
Level 1 template page token
 
 
  <ssEncrypt>typid,rootcompanyid</ssEncrypt>
 
  <ssEncrypt>typid,rootcompanyid</ssEncrypt>
  
−
Level 2 template page token
+
[[Level 2 template]] page token
 
  <ssEncrypt>typid,appid,rootcompanyid</ssEncrypt>
 
  <ssEncrypt>typid,appid,rootcompanyid</ssEncrypt>
  
−
Webpage View token:
+
{{WPV}} token:
 
  <ssEncrypt2>objectid</ssEncrypt2>
 
  <ssEncrypt2>objectid</ssEncrypt2>
  
−
Example: To open the [[Web Page View]] with custom field id 123456 on a contact you would use the following syntax:
+
Example: To open the {{WPV}} 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)" >
 
  <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:
 
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)" >
 
  <input type=button class=Button  value="Open" onclick="_openpageview('<ssEncrypt3>654321</ssEncrypt3>','<ssEncrypt2>@opportunityid@</ssEncrypt2>',1)" >
  
−
 
+
[[Transaction]] token
−
Transaction token
 
 
  <ssEncrypt>userid,typeid</ssEncrypt>
 
  <ssEncrypt>userid,typeid</ssEncrypt>
−
 
−
 
  
 
[[Category:Variables]]
 
[[Category:Variables]]
 +
{{DeterminingIDs}}

Revision as of 14:50, 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>
Retrieved from ‘https://wiki.smartsimple.com/index.php?title=SsEncrypt&oldid=15968’