A branch is a container for rulesets with rules that are undergoing rapid change and development. The rulesets associated with a branch are called branch rulesets. A branch ruleset is a ruleset that:
Because development work is typically iterative, rules are often created and modified quickly on a day-to-day basis. This rapid change can become disruptive to the overall project when this work takes place using multiple teams working in the same application rulesets. Branches allow such development work to take place within an isolated space (the branch) without affecting functionality in the source rules.
This branching ability is especially useful on large development projects, where multiple teams work simultaneously on the rules in an application, and all members on one team need to see each others work, while also isolating their development changes from the other teams. In this way, one team's rule changes do not affect the other teams until the changes are stable, conflicts resolved, and approval granted to make the new functions available to the entire development project team.
You create branch rulesets in the Branch area on the the Application rule form's General tab.
For an example, see PDN article 26427 Using branch rulesets and merging for parallel development.
If your application was developed in v6.2SP2 and uses branch rulesets, and you want to operate in ABA mode for best performance, note that branch rulesets appear higher in the ruleset list in ABA mode than in rules assembly mode. While it is unlikely that this change affects results of your application, some analysis and testing is recommended.
Related terms