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

Typing in a bad number must display a custom error



The edit-validate rule associated with a property should cause a custom error to appear if a bad number is typed in since you defined a message rule to trigger if a NumberFormatException is thrown. Instead of displaying the custom message, the system shows the out-of-the-box message.

Error Messages

is not a valid decimal value

Steps to Reproduce

1. Create a decimal property.
2. Configure edit-validate and define a custom message rule to trigger if a NumberFormatException is thrown.
3. Put an invalid value in the field associated with the property at runtime.

Root Cause

If client side validation is enabled, it causes controls to comeup with custom JavaScript validation for edit-validates. The JavaScript based validation prevents the value from being passed to the server and evaluated by custom rules.


This issue is resolved through the following local-change:

Turn off client validation.

Published July 22, 2015 - 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