Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Branched application development

Updated on January 14, 2022

Your teams can develop multiple features simultaneously without overwriting work and causing conflicts by implementing branched application development. During branched development, developers can make changes in one ruleset that affect other developers only after you merge the changes into a target ruleset. As a result, you speed up application development and can clearly analyze what changes your application includes.

For example, by using branches, two teams can work simultaneously on different application features, such as case type creation and notifications. Each team can make can make changes that do not affect the changes of the other team during the development process, even if the features use the same base rulesets. When the development process is complete, you can review branches to resolve any conflicts, and then merge the results into a target ruleset in order to make the new features available in the final version of your application.

To learn more about branched application development, see the following articles:

  • Branches and branch rulesets

    Branches help you manage work in development environments in which multiple teams contribute to a single application. You use branches to develop software simultaneously in a version-controlled environment. For example, a team can develop a feature in one branch while another team develops another feature in a different branch, even if the teams share the same rulesets.

  • Branches and unlocked rulesets

    Based on your development model, you can build your application through branched development or by using unlocked rulesets. Before you select an approach, analyze which option suits your requirements best.

  • 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.

  • Branch operations

    After you create branches and develop rules in branch rulesets, you can work with branches in a number of ways. For example, you can create branch reviews with other users, delete branches form the system, and lock branches before you merge them.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us