Circumstance rules are not taking effect
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.
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.
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.
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".
Published June 12, 2015 - Updated October 8, 2020
Was this useful?
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.