Discussion
Resolving issue with a stale WorkLink
Post upgrading from v7.21 to 7.3 to a new infrastructure (a new app url), a case management feature making use of WorkLink correspondence fragment was found degraded. The direct link to work object (embedded in outgoing emails) pointed users to the old environment.
Troubleshooting:
Verified below Dynamic-System-Setting is set with current application url.
Pega-ProCom • PublicLinkURL (Pega-ProcessCommander)
Root cause:
The Data-Admin-System-Configuration object was found stale even after the processes responsible to populate it were rerun. A limitation identified in Pega 7.3, which causes the primary public url (pyPublicLinkURL) to remain stale, pointing to the old environment.
Resolution:
The issue was resolved after removing the stale object. Steps:
- Update DSS with current application url
- Delete the stale DASC instance
***Edited by Moderator Marissa to update Content Type from Idea to Discussion; added Developer Knowledge Share tag***