Rule Resolution while having Multiple Branches in Application
Hello All,
Please note that we are implementing Branches to our application now since the no of Parallel development has increased.
However we have few concerns for the Rule Resolution in PEGA with multiple branches in it.
Scenario:-
there is one common activity being saved and has changes done by developers, lets say in branch-1 and branch-2
In-case developer wants to test his changes using the Application portal and his rule resides in Branch-2, During Run time pega will pick rule from Branch-1 since the application hierarchy is like that(Branch-1 then branch-2)
how to resolve this situation?
-we have found out that dragging the branch up and down in the hierarchy can help you set the presidency however this is not a safer way
-also in some contents we saw that people discussed for creating AccessGroups which should contain branch-rulesets and those can be added to every operator relevant to the development team however we are not able to figure out a way to do this implementation.
Kindly help.
Thanks,
Swagat
Pegasystems Inc.
IN
Hi Swagat,
For your scenario if you don't want to drag the branches to set the hierarchy you need to create different applications(which you can create on top of your original application).
Inside access group, we can specify application name.
Open the application rule which is defined in access group and add the branch ruleset in this application.
Then, this access group must be able to use the rules in this particular branch ruleset.
In general you should use multiple branches to work on different features not on the same feature.
If you are using different branches to work on same feature than you should somehow tell pega which branch it should consider for that particular feature first and the order of the branch is the way to tell pega which branch it should pick.
The branch concept is always used in context that each developer is working on each branch.
For example suppose you have two branches B1 and B2 having activity A1 and A2 in both branches (i.e. A1 is in B1 and B2 and A2 is also present in B1 and B2). If you want A1 to be picked from B1 and A2 to be picked from B2 then these statements and contradictory. As at a time you can mention only one branch to be at priority.
Please refer the below link to know the configuration of branch:
Hi Swagat,
For your scenario if you don't want to drag the branches to set the hierarchy you need to create different applications(which you can create on top of your original application).
Inside access group, we can specify application name.
Open the application rule which is defined in access group and add the branch ruleset in this application.
Then, this access group must be able to use the rules in this particular branch ruleset.
In general you should use multiple branches to work on different features not on the same feature.
If you are using different branches to work on same feature than you should somehow tell pega which branch it should consider for that particular feature first and the order of the branch is the way to tell pega which branch it should pick.
The branch concept is always used in context that each developer is working on each branch.
For example suppose you have two branches B1 and B2 having activity A1 and A2 in both branches (i.e. A1 is in B1 and B2 and A2 is also present in B1 and B2). If you want A1 to be picked from B1 and A2 to be picked from B2 then these statements and contradictory. As at a time you can mention only one branch to be at priority.
Please refer the below link to know the configuration of branch:
Please let me know if this helps.
Regards,
Vikash