A development learn plans to enhance functionality of an existing application by changing several user interface rules. The team would like to pilot the enhancements to small group of users before rolling the changes out to the entire user base.
What approach maximizes reuse and maintainability?
1) Place the updated rules into a new minor version of the ruleset and include the new ruleset version in a new application.
2) Place the updated rules into a new minor version of the ruleset and include the new ruleset version In a new version of the application.
3) Place the updated rules Into a new ruleset and include the new ruleset in a new version of the application.
For your implementation, I would suggest going for the branch rulesets concept in Pega. You can create an application rule and add an access-group and point the created application to the access group. Create a branch for that application rule and add the enhancement rules in that branch ruleset. At the end merge those branch rules into the existing application rule-set or create a new version of the application rule-set. PFB article for reference.
When we want to give access to the new changes only for some users, we can create a new access group and mention the application name and version there.
In the given scenario, to make the maximize reuse and maintainability, we will be creating just the new application version so that when we want to roll out for all users we can point to this application version in the user's access group.
We will be creating a new minor version of the same ruleset so that maintainability is easy when we want to do changes in the ruleset stack of application rule.