How to have persistent custom url parameters
Hi,
We have a requirement for having a set of custom url parameters to be persistent as part of the url across all Pega CM pages. Currently, if we add a set of custom url parameters on login these gets stripped off as soon as we navigate to another Pega CM page.
Would anybody know if a way to do this in a global way through configuration or similar? (We would not be able to do this manually on every single control that triggers a POST of a Form.
Appreciate any help.
Accepted Solution
Commonwealth bank of australia
AU
Pegasystems Inc.
IN
Hi
Can you please provide bit more detail on how you are doing the design currently. Screenshots can help.
Accepted Solution
Commonwealth bank of australia
AU
Hi,
The issue is simple as described in the initial post: Pega CM does not allow 'non Pega CM' parameters in the query string to survive form posts. We needed these parameters to manage an integration aspect of Pega which runs as an embedded application in a portal.
We have resorted to a different design where we one the initial launch of Pega CM get the url parameters we are interested in as at this point in time the custom parameters are present in the query string; Then we write the parameters to the a more persistent store - in our case the browser's local storage - which survives the form post. We can pick up the values on the new pages being rendered and use it for our custom logic.
I will close the thread. Perhaps this post can help other people with similar needs.
Hi,
The issue is simple as described in the initial post: Pega CM does not allow 'non Pega CM' parameters in the query string to survive form posts. We needed these parameters to manage an integration aspect of Pega which runs as an embedded application in a portal.
We have resorted to a different design where we one the initial launch of Pega CM get the url parameters we are interested in as at this point in time the custom parameters are present in the query string; Then we write the parameters to the a more persistent store - in our case the browser's local storage - which survives the form post. We can pick up the values on the new pages being rendered and use it for our custom logic.
I will close the thread. Perhaps this post can help other people with similar needs.