Question
Pega Systems
IN
Last activity: 13 Feb 2017 9:35 EST
Integration rules (created by Wizard) clean up on QA
We ran Connect REST wizard to have integration established. And the code is moved to QA environment from DEV.
Due to a change in the requirement - we had to re-run the wizard for the new service. (NOTE: WE HAVE TO CHANGE SERVICE AND CLASS NAMES TOO)
On DEV, we used "Undo Generation" option to delete the generated rules.
We want to clean up the rules on QA. What is the correct way to achieve it. Though they may not harm the application since there will be no reference to these service rules, we want the rules to be cleaned.
Thanks in advance.
***Updated by moderator: Lochan to add Categories***
Accepted Solution
Pegasystems Inc.
IN
Given the instances are already present in the QA then I would try the following
1. Do not run the undo generation. Rather withdraw them in DEV first and then re run the wizard freshly. Post that move the updated code to QA.
2. If you have already run the UNDO GENERATION then the other preferable option is to withdraw these rules from QA
Pega Systems
IN
Options we have thought about:
- Make list of all those rules and delete them manually from QA. (not my favorite option)
- Delete from backend (not my favorite again)
- pxDataSource instance and Log-BatchRuleSave instances can be shipped to QA and run wizard there (?)
Any clean way?
Accepted Solution
Pegasystems Inc.
IN
Given the instances are already present in the QA then I would try the following
1. Do not run the undo generation. Rather withdraw them in DEV first and then re run the wizard freshly. Post that move the updated code to QA.
2. If you have already run the UNDO GENERATION then the other preferable option is to withdraw these rules from QA
Areteans Technology Solutions
AU
Pega Systems
IN
Usually we should not delete if the code moved to QA. I have not deleted rules yet.
And deleting the ruleset version may have other dependent rules in it. But, yeah - its one of the ways to clean. But probably not the best!!