Question
Legato Health Technologies
IN
Last activity: 20 Mar 2018 0:31 EDT
Property with max length of 24 throws an error stating String too long
Got a property set in an activty. The said property has a max length of 24 defined in its advanced tab. After property set, there's a error on the page stating the value for this said property is too long, it should be only 23 characters while the value we have is of 24 characters which exactly complies with the max length constraint. The property is of text type and we don't have any validations running for the same. There's a "Default" control for this property. So, not sure what is causing this error since the value is within the defined constraint of max length.
Any inputs on the same would be helpful.
***Updated by moderator: Lochan to add Categories***
Accepted Solution
Legato Health Technologies
IN
Update: Was a rule cache issue. Revalidate and save helped fix this abrupt behavior.
Pegasystems Inc.
US
Hi Siva,
Tested the similar use case in Pega v7.2.2 by setting the property max length to be 24 and in my activity i am setting the property value as "012345678901234567890123", which is being called in pre-processing of my flow action and the value is being set correctly in the UI field.
Could you share the screenshots of your issue along with the value what is being noticed in clipboard and tracer to make sure your string doesn't contain any special characters.
Regards
Mahesh
Legato Health Technologies
IN
Hi Mahesh,
I'm unable to provide you with the screenshots. Description of the issue and its context:
The application under context is a smart dispute application and the problem stated is with respect to a property called "AcquirerReferenceNumber" which is being used in property set in activity "UpdateCustomerSatisfaction". All the stated rules are out of the box rules. The exact error is:
Legato Health Technologies
IN
Update: Placed a step right after the property-set step in the said activity. In this new step, I haven't defined any method, just defined the step page (the page over which error is being thrown). With this change, I was able to successfully save the data over the page without any error.
Not sure how is this helping the whole process.
Regards,
Siva
Accepted Solution
Legato Health Technologies
IN
Update: Was a rule cache issue. Revalidate and save helped fix this abrupt behavior.