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.

How to learn whether a rule has a sibling in a higher RuleSet version

Updated on November 15, 2015

Summary

A developer asks: What's the best way to learn that a rule exists in a higher-numbered RuleSet version that the one currently open in the Developer portal?

Our development and QA procedures require that such rules be adjusted once QA team verifies that a bug has been fixed in a separate, lower-numbered RuleSet version. For example, after I change an activity in version 03-07-15, and the QA team tests my change, I may need to repeat this change in version 03-07-16 of the activity, if there is an 03-07-16 version. 

Suggested Approach

Use the Siblings button on the toolbar whenever you make a fix, and it shows you all the rules and versions in the RuleSets with this name. 

This lets you see whether you need to make the updates that your procedures require.

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us