Skip to main content

Implementing branched application development

Pega Community logo

Note: The following content, referenced from Pega Community, is included here to help you better achieve the module learning objectives.

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 use branches in your application, create a development application that is built on your base application. You create and save rules in your development application, which results in creating branch rulesets. You can then work with branches in several ways, such as creating branch reviews and merging branches.

To configure your application to use branches and branch rulesets, complete the following steps:

  1. Create a development application that is built on your base application.

    For more information, see Creating a development application.

  2. Add branches to your application, into which you can save the rules that you develop.

    For more information, see Creating branches.

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

  • Creating branches

    Create branches in your application so that you can develop rules in them. The system automatically creates branch rulesets when you save a rule in to the branch.

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

  • Setting branch development preferences

    Define branches where you want to save the changes that you make in App Studio, so that you can work on a feature without affecting other parts of your application.

  • Branches and branch rulesets

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

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

50% found this content useful

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice