You need to sign in to do that
Don't have an account?
Stephen Finlay
Assembled URLs now failing if they include a tokenised value ( CipherCloud )
Since Saturday, the Apex class that assembles a URL to be assigned to a button on a VF page is failing to return a value if the string includes a tokenised value. ( We are using the CipherCloud tokenising gateway )
For example, the following piece of code returns nothing at all if the result of aContact.Name would be a tokenised value.
selectedinteractionurl= 'a02/e?CF00N90000007GAuz='+latestcall[0].Name+'&CF00N90000007GAuz_lkid='+latestcall[0].Id+'&CF00N90000005GWKP='+aContact.Name+'&CF00N90000005GWKP_lkid='+aContact.Id+'&retURL=/apex/CallerInteractions?id='+aContact.Id+'&renderToolbar=true';
If aContact.Name returns a non-tokenised value, then it works fine.
This was all working fine until last Saturday.
For example, the following piece of code returns nothing at all if the result of aContact.Name would be a tokenised value.
selectedinteractionurl= 'a02/e?CF00N90000007GAuz='+latestcall[0].Name+'&CF00N90000007GAuz_lkid='+latestcall[0].Id+'&CF00N90000005GWKP='+aContact.Name+'&CF00N90000005GWKP_lkid='+aContact.Id+'&retURL=/apex/CallerInteractions?id='+aContact.Id+'&renderToolbar=true';
If aContact.Name returns a non-tokenised value, then it works fine.
This was all working fine until last Saturday.
selectedinteractionurl= 'a02/e?CF00N90000007GAuz='+latestcall[0].Name+'&CF00N90000007GAuz_lkid='+latestcall[0].Id+'&CF00N90000005GWKP='+EncodingUtil.urlEncode(aContact.Name, 'UTF-8')+'&CF00N90000005GWKP_lkid='+aContact.Id+'&retURL=/apex/CallerInteractions?id='+aContact.Id+'&renderToolbar=true';
reference :
http://help.salesforce.com/apex/HTViewSolution?id=000057334&language=en_US
All Answers
selectedinteractionurl= 'a02/e?CF00N90000007GAuz='+latestcall[0].Name+'&CF00N90000007GAuz_lkid='+latestcall[0].Id+'&CF00N90000005GWKP='+EncodingUtil.urlEncode(aContact.Name, 'UTF-8')+'&CF00N90000005GWKP_lkid='+aContact.Id+'&retURL=/apex/CallerInteractions?id='+aContact.Id+'&renderToolbar=true';
reference :
http://help.salesforce.com/apex/HTViewSolution?id=000057334&language=en_US
I am just wondering why I am needing to do this encoding now? The original code worked fine last week ( and since mid-March when I first deployed it )
Have Salesforce changed something over the weekend?
I cannot think of any particular reason.. but it could be simply the token cipher values didn't had any special characters so far and u hit the first one today.. :-)