Implementing branched application development
For faster delivery of your products, configure your application development to use branches. By implementing branches, team members can work simultaneously on multiple features, without the risk of interrupting work of different team members.
For example, team members can develop different service-level agreement rules or work on multiple bugs in parallel by using separate branches.To configure your application to use branches and branch rulesets, complete the following steps:
- Create a development application that is built on your base application.For more information, see Creating a development application.
- Add branches to your application, into which you can save the rules that you
develop.For more information, see Adding development branches to your application.
- Work with branches in several ways that meet your business requirements. For example,
create a review, merge branches, or delete branches from the system.For more information, see Branch operations.
- Creating a development application
To speed up application development, you can support branched development by creating a development application that is built on the production application. By providing branches for development, you ensure that different teams and team members can work on different features simultaneously, without a risk of creating errors and conflicts.
- Adding development branches to your application
To avoid conflicts and errors when team members work simultaneously, add development branches to your application so that team members can work simultaneously on multiple features without risking conflicts and errors that can arise from working on the same rules.
- Adding system branches
You can add branches that already exist on your system to your application. You cannot add a branch that contains branched versions of a ruleset that is not in your application stack.
- Creating branch rulesets
Provide your development team with an ability to work on multiple features in parallel by creating branch rulesets. When you save rulesest in different branches, team members can work on isolated rulesets without impacting development of other features. As a result, you avoid overwriting results and generating errors.
Previous topic Branches and unlocked rulesets Next topic Creating a development application