Avoid issues with cached rules after deployment using PDM
We have noticed that we encounter a caching issue from time to time on our testenvironment. This leads to a bug logged for the developers and therefore consumes time/resources which are not really needed. Therefore we would like to trigger the RevalidateAndSave option from the deployment pipeline in Pega Deployment Manager after a deployment to the test environment. Unfortunately I haven't found an option to do that (it is not a standard option and I couldn't find an option to trigger an activity/service in the target environment as a step of the deployment pipeline). Does anybody have a suggestion we can use to either make sure old versions of rules are not still available in cache after a deployment or trigger an activity/service from the deployment pipeline. We are currently using PDM 5.6.4 and Pega Platform 24.2 Many thanks in advance. Kind regards, René van Seuren
Accepted Solution
Updated: 10 Jul 2025 3:37 EDT
HCA Healthcare
US
@Renév545 After deploying code using Pega Deployment Manager (PDM), sometimes old rule versions stay in cache and cause issues in the test environment. To avoid this, you can create a custom activity or REST service in the test environment that runs the RevalidateAndSave process or clears the cache. Then, add a custom step in your PDM pipeline to call this activity or service after deployment. This step can use a REST call or Connect-REST rule to trigger the cache refresh. Make sure the right access group has permission to run this task. This helps to ensure only the latest rules are active and avoids bugs caused by old cached rules.
BPM Company
NL
@Sairohith We were already looking for a solution like this, but couldn't find it in PDM 5.6 (only in DMS 6). But based upon your answer I search again and I found the documentation for custom tasks at: https://docs.pega.com/bundle/deployment-manager/page/deployment-manager/dm/custom-tasks.html Thanks