Best practice of UAT arrangement when multiple developments on Pega 8.6.2
I had separated multiple applications & multiple ruleset on Pega 8.6.2 to develop different projects. Most of contents are related to CDH actions and campaign/data flow run.
Production will only keep single ruleset so I need to merge multiple ruleset into master ruleset in UAT stage.
As I found "merge" will override content by latest version(raised INC) so I would like to know :
---> any idea how to control ruleset version for Pega 8.6.2.?
The situation is
Cannot merge to become single ruleset
Project A run campaign, setup priority of A ruleset higher than master ruleset
But project B cannot run campaign at this moment as its ruleset is lower than other ruleset so empty after campaign run.
So, this case is not UAT concept as cannot test together.
Updated: 30 Aug 2023 12:27 EDT
Pegasystems Inc.
GB
@SunshineL To merge multiple rulesets into a master ruleset in Pega 8.6.2, follow these steps:
- Ensure all rules are checked into their base rulesets before merging.
- Lock the branches after development is complete to include only the changes you want to merge.
- In Dev Studio, navigate to the App Explorer and click the Branches tab.
- Select the branches you want to merge and follow the appropriate steps for merging a single branch or multiple branches.
- Resolve any conflicts or warnings that occur during the merge process.
- In the Target ruleset section, select the base ruleset version you want to merge the rulesets into. You can either create a new ruleset version or reuse an existing one.
- Click Merge to complete the process.
After merging, you can control the ruleset versions by managing the ruleset stack in your application definition. Adjust the order of the rulesets to prioritize the rulesets for different projects. Ensure that the rulesets are properly configured in the Built on applications section and the Application rulesets section of the application definition.
This answer came from a Pega gen-AI assistant using the below references. As a Support Center moderator, I reviewed the answer and references for accuracy:
Merging branches into target rulesets
@SunshineL To merge multiple rulesets into a master ruleset in Pega 8.6.2, follow these steps:
- Ensure all rules are checked into their base rulesets before merging.
- Lock the branches after development is complete to include only the changes you want to merge.
- In Dev Studio, navigate to the App Explorer and click the Branches tab.
- Select the branches you want to merge and follow the appropriate steps for merging a single branch or multiple branches.
- Resolve any conflicts or warnings that occur during the merge process.
- In the Target ruleset section, select the base ruleset version you want to merge the rulesets into. You can either create a new ruleset version or reuse an existing one.
- Click Merge to complete the process.
After merging, you can control the ruleset versions by managing the ruleset stack in your application definition. Adjust the order of the rulesets to prioritize the rulesets for different projects. Ensure that the rulesets are properly configured in the Built on applications section and the Application rulesets section of the application definition.
This answer came from a Pega gen-AI assistant using the below references. As a Support Center moderator, I reviewed the answer and references for accuracy:
Merging branches into target rulesets
About the Ruleset Maintenance wizard > Merging rulesets and ruleset versions
Merging a development branch > 4 Merge the branch contents