Pratik A (pratik)
Cognizant Technology Solutions
Strategic Solution Architect
Cognizant Technology Solutions
pratik Member since 2013 13 posts
Cognizant Technology Solutions
Posted: March 5, 2020
Last activity: May 13, 2020
Posted: 5 Mar 2020 9:46 EST
Last activity: 13 May 2020 14:40 EDT

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.


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.


The issue was resolved after removing the stale object. Steps:

  1. Update DSS with current application url
  2. Delete the stale DASC instance


***Edited by Moderator Marissa to update Content Type from Idea to Discussion; added Developer Knowledge Share tag***

Pega Platform 7.3 Case Management Workforce Intelligence Developer Knowledge Share