A non-existent ruleset version is displayed as locked
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.
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.
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.
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.
0% found this useful