Support Article
Override of property
SA-7312
Summary
Not able to change the max-length of a property once the property is checked in.
Error Messages
Trying to save an invalid page: Trying to save an invalid page: page is not valid .TestProp: "TEST" is too long, maximum length allowed is 3
Steps to Reproduce
1. Create a ruleset Sandbox:01-01-01
2. Create a property TestProp with Text type and max length of 3 in Sandbox:01-01-01
3. Create an activity to popuplate TestProp with strings more than 3 like "TEST" and try obj-save method. This will cause an error and you can't save WO in the database. This is expected behavior.
"Trying to save an invalid page: Trying to save an invalid page: page is not valid .TestProp: "TEST" is too long, maximum length allowed is 3"
4. Now check in both rules and lock Sandbox:01-01-01
5. Create a new ruleset Sandbox:01-01-02 and include in your rulestack
6. Do save as TestProp in Sandbox:01-01-02 and override it as max length of 5
7. Run the activity again to see the error is resolved. However, I get the same error.
Root Cause
The root cause of this problem is a defect in Pegasystems’ code/rules. The referencing rule ( Activity in this case), doesn't always call the highest versioned reference rule( property in the highest version of ruleset). This is causing the issue.
In this case, the activity always refer the property which was created before the activity. Though the property is saved in another higher version of ruleset, it's not being referred.
Resolution
This issue is resolved through the following local change: Doing a RevalidateAndSave of all the referecing or dependent rules solves the issue.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.