Skip to main content

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.

Support Article

Circumstance rules are not taking effect

SA-909

Summary



After saving the base copy of a circumstanced rule into a higher ruleset version, users are not presented with the circumstanced copy of the rule when the circumstance conditions hold true.  Instead, they see of the base copy of the rule.

Error Messages



No error message is displayed.


Steps to Reproduce



1. Have a ruleset version with base and circumstanced copies of a rule.
2. Save the base rule into a higher version of the ruleset.

Root Cause



The root cause of this problem is software use/operation error.  This behavior can occur if the "Base Rule" checkbox under the "Availability" options is checked for any copy of the base rule within the same minor ruleset version.


Resolution



This issue is resolved through one of the following local change options: 

1. Unchecking the "Base Rule" checkbox under the "Availability" options for all copies of the base rule.
2. If the "Base Rule" checkbox under the "Availability" options is checked for a copy of the base rule that cannot be modified, such as one in a locked ruleset, adjusting the value of the “compatibility/SortBaseRulesBelowCircumstancedRules” prconfig setting to "true".
Suggest Edit

Published June 12, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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

Pega Community 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
Contact us