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

Inconsistency in client side validation behavior



There is a validation check associated with a text field, that a user should not enter special characters in it.

So when user enters the special characters in this field like '12345@!#', the validation error is thrown as expected.

But, if user revisits this field and tab out without making any changes to the value, the field validation error disappears.

  1. Initially enter ‘@’ in the field and tab out.

(As this field accepts only alphabets/numbers the field is promptly flagged)
  1. Now re-visit the same field and just tab out.

(See that flag on field is now gone, this is the issue)

Error Messages

Not applicable

Steps to Reproduce



“@(Pega-RulesEngine:String).pxContainsSpecialCharacters(param.Input)” is the condition used here in when field.

Root Cause

This issue was determined to be a product enhancement request.

With the current error handling infrastructure user cannot identify what messages are related to what error.

In case of blurring from the field without changing any value user evaluates the clientside validations again and clear all the error messages related to that property.

Also this time there is no change in the input text, onchange related actions will not be executed. This is the reason why we are seeing the issue.


An enhancement request, FDBK-16658, has been created for consideration by Pega Product Management. 

Published September 21, 2016 - Updated October 8, 2020

Was this useful?

100% 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