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.

Managing development with two unlocked versions of one RuleSet

Updated on September 13, 2021


A developer asks:

We have two unlocked versions of one RuleSet undergoing development at the same time, and I'm concerned about mix-ups and gaps that could occur as a result. 

For example, if Alice copies and changes a Version 01-02-03 activity into 01-02-04, but Harry also copies 01-02-03 into 01-02-05 and makes unrelated changes, Alice's changes might be lost when 01-02-05 is put into production.

Are there any recommendations or suggestions?


The type of concurrent development you describe, while sometimes necessary in a crunch, is discouraged for planned development.

The burden is on the team who make changes in the lower version to ensure that any necessary changes are also made to the higher version.  Use the toolbar Siblings button to see in which versions a given rule exists.

Developers making changes to a rule in a lower version should be on the lookout for changes made to that rule in higher versions. If someone changes a rule in a lower version, and the rule also exists at a higher version, the change will be invisible to everyone on the higher version.  They may need to apply her fix also to the later version.


Pega Platform 7.1.1 - 8.3.1 System Architect Low-Code App Development System Administration

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