Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Developing applications, merging branches, and deploying changes in a distributed development environment

Updated on April 5, 2022

When you work in a distributed development environment, you generally work in branches and merge them to incorporate changes into the base application. The implementation of some of your tasks depends on your specific configuration, such as which automation server you are using.

In general, working in a distributed development environment consists of the following tasks and methods:

  1. On the remote development system, build a team application layer that is built on top of the main production application. The team application layer contains branches, tests, and other development rulesets that do not go into the production application. For more information, see the Pega Community Using multiple built-on applications.

  2. Lock the application ruleset by performing the following steps:

    1. In the header of Dev Studio, click the name of your application, and then click Definition.

    2. In the Edit Application rule form, in the Application rulesets section, click the Open icon for the ruleset that you want to lock.

    3. On the Edit Ruleset rule form, click Lock and Save.

    4. In the Lock Ruleset Version dialog box, in the Password field, enter the password that locks the ruleset.

    5. In the Confirm Password field, reenter the password to confirm it.

    6. Click Submit.

    7. Save the Edit Ruleset rule form.

    8. Save the Edit Application rule form.

  3. Create a branch of your production ruleset in the team application. For more information, see Adding branches to your application.

  4. Work in branches on remote development systems.

  5. Use release toggles to disable features that are not available for general use. For more information, see Toggling features on and off.

  6. Create a review so that other developers can review branch content. For more information, see Creating a branch review.

  7. Conduct developer reviews to review the content and quality of the branch. For more information, see Reviewing branches.

  8. Lock the branch. For more information, see Locking a branch.

  9. Migrate branches to the source development system and then merge and validate the branches. Depending on your configuration, you can either do both steps at the same time or separately. Do one of the following tasks:

    1. To migrate and merge branches at the same time, perform step 10.

    2. To migrate and merge branches separately, perform steps 11 - 13.

  10. To migrate and merge branches at the same time, do one of the following actions:

  11. To migrate a branch and then separately merge and validate the branch, migrate branches to the source development system by doing one of the following tasks:

  12. Merge and validate branches by using the Merge Branches wizard. For more information, see Merging branches into target rulesets.

  13. Migrate the merged rules back to the remote development systems by doing one of the following tasks:

  • Previous topic Understanding the components of a distributed development environment
  • Next topic Migrating and merging branches by using Deployment Manager

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