Question
DXC Technology
BE
Last activity: 29 Jun 2018 9:33 EDT
PRS deletion on production
Dears,
We follow an approach of creating a Production rule set on Production for any urgent quick fixes that have big impacts. Later on these fixes are built as a jar and delivered to Production formally through the release process. Thus we need to delete the existing quick fix PRS after the actual fix goes in to production. Sometimes the list of such deletions are a lot and take a lot of time to search and then delete.
Is there a way to bulk delete rules which are in PRS so that the time to search and delete each one is considerably saved.
We use Pega 7.1.8
regards,
Jagan
Accepted Solution
Capgemini
IN
You can have an utility activity which takes rule's pzInsKey in csv format and the parse it and delete the rules by looping through the list.
But I still think this is not the right way of mentioning the code. You might think of having multiple production ruleset version and consider withdrawing the rules which are not required to be in production ruleset.
-Saikat
ANZ Banking Group Ltd
AU
Hi ,
Here i would suggest you to use more than one version of production ruleset.
Example : you have got an issue in production, as it is blocker you want to give fix in Production rule set. in this case create new version of the Production rule set add the rules specific to that issue in that version.
once you move the code do production through the process then after your deployment you can delete that specific version itself.
This approach will help you to manage it better way.
Let me know your thoughts around it.
Best,
Mahesh
DXC Technology
BE
Thanks. But i am looking for an answer to delete such PRS after the fixes moves in. If one or two its manually easy. How to delete when there are say 25 such PRS in production.
Accepted Solution
Capgemini
IN
You can have an utility activity which takes rule's pzInsKey in csv format and the parse it and delete the rules by looping through the list.
But I still think this is not the right way of mentioning the code. You might think of having multiple production ruleset version and consider withdrawing the rules which are not required to be in production ruleset.
-Saikat