In Pega 7 Platform, branch identifiers (their names) are system-wide. They can be used by anyone that has a compatibly configured application. However, if another team creates a branch ruleset based on a ruleset that is not in your application or one of its parents and selects a branch identifier that you are using in your development application, the system does not associate that branch ruleset with the branch and associates a ruleset that only it can see in their application. The system displays a warning in the application rule. In this situation, you can either add the missing dependency ruleset to the correct location in your application stack or negotiate with the other team to have them move their work into a new branch for their own use.
Share this page
Share via Facebook
Share via Twitter
Share via LinkedIn
Share via Email
Moderation Team has archived post,
This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 5 years ago
Updated: 5 years ago
Posted: 2 Mar 2016 13:06 EST Updated: 2 Mar 2016 15:19 EST