Posted: 16 Mar 2018 5:25 EDT Last activity: 16 Mar 2018 11:55 EDT
Branches and circumstancing issue
in our enterprise environment we have different projects that have been developed in parallel on the same application so we are using branches.
We noticed a "strange" behaviour with circumstanced rules:
we have to modify a circumstanced version of a rule so we save it in a branch
we launch our application and everything is ok: it uses the base or circumstanced version of the rules according to the expected behaviour
we have to modify the base version of a circumstanced rule so we save it in a branch
we launch our application and it uses only the base version (present in the branch) and never the circumstanced one. Our impression is that the circumstanced version of the rule it is not seen by PEGA anymore
The workaround we found to solve the issue of Scenario 2 is to save all circumstanced versions of the rules in the branch even if we have no modification.
According to your experience what is the correct approach to solve the problem?
Do you face a similar scenario? Is this a standard behaviour when you use branches and circumstances?
You read correctly the "Projects" term, but according to your response we still don't understand why we need to copy all circumstanced version of the rule only if we change the base rule and not if we change a circumstanced one (only in Scenario 2).
So do you confirm that resave circumstanced rules in the branch, even if no modification is needed, is the correct approach to solve the problem?