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

A non-existent ruleset version is displayed as locked

SA-18805

Summary



Ruleset version XYZ:01-01-01 is not locked. However, ruleset rule form indicates that XYZ:07-15-11 is locked and hence, it does not allow any configuration changes to the ruleset.
Ruleset version XYZ:07-15-11 does not exist in the system, there are no rules that refer to it.

Error Messages



XYZ:07-15-11 is locked. Check out to branch or save as into unlocked ruleset version to edit.

Steps to Reproduce



Click the lock icon on Ruleset rule form header.

Root Cause



Entry in Data-Rule-Summary is in corrupted state. Querying Data-Rule-Summary class (pr4_rule_vw table in database) displays that the version exists but running a Report Definition on Rule-RuleSet-Version class does not display it.
Value in BLOB is in sync with Data-Rule-Summary but not with the exposed column in the actual rule table (it was updated bypassing Obj-Save method) that left the rule's exposed value and BLOB value out of sync.

Resolution



Revert the rule to a good state:

1. Create a Product rule with only the Ruleset in question and export it. (Backup of the rule in current state)
2. Create a test Activity and perform Obj-Open of the rule
3. In another step, set property - pyRuleSetVersion to blank.
4. Perform Obj-Page on the same Activity. This should update the rule and also the record in the Data-Rule-Summary.

Published January 31, 2016 - 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.

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 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