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

Overridden field value rule is not picked



User has overridden a default pyMessageLabel for business requirement. 
For example: pyMessageLabel is not a valid decimal value rule has been saved and the message is modified.

When any non-decimal is entered into input field of Decimal property, the overridden message is displayed. 
But when a On-Change RefreshSection behavior is configured on the input, the new rule is not picked.

Error Messages

Not Applicable

Steps to Reproduce

1. Override pyMessageLabel is not a valid decimal value rule and enter custom label. 
2. Create a decimal property and configure on-change refresh section behavior on the input. 
3. Enter non-decimal into the input and tab-out to observe the error.

Root Cause

When the harness is rendered for the first time the field value is final and the script error is picked from the field value which is already sent to the client. When refreshed again the section is executed and control refers rule-message data to display the error harness and not the field value.


This issue is resolved through the following Local-change: 

Perform a Save-as of DecimalValueBadFormat (Rule-Message) and add the required message.

Suggest Edit

Published June 10, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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