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

Normalise rule is not working as expected



Normalize rules resulting in unexpected substitutions. No definite pattern and replacement of words not defined in the parse rule is happening.

One of the strange replacement is :-


Although "VED" is not present in the parse rule for replacement.

Error Messages

No error message.

Steps to Reproduce

1. Create an activity with step method Text-Normalize
2. Input the string and the parse rule to be used for substituion and run the activity.
3. Input String :

Root Cause

The root cause of the problem is that a word with “.” in it will be considered to be having wild characters as replacement for the dots when you have not selected the string as a “whole word” via the checkbox in the parse rule.

  • V.D.  ( without whole word check box ) is equivalent to replace VEDE. Technically this makes sense as well since “.” is the generally accepted term to demarcate 2 words or end of a sentence.
  • V.D. (with whole word check box) is equivalent to replace “V.D.”

  • This approach also covers the use case
A.B.C.D.V.D.E. ( with whole word check boxed ) … will be replaced for “V.D.” within this sequence as the demarcation of word is already implicitly present by the “.” character.

VALUE is replaced by VALDATE
and VAL is also considered as a string to be replaced. System sees the replaced character VALDATE in the above sequence and replaces it.


Use the “V.D” replacement or for that matter any word with dot in it with “whole word check boxed” always in the parse rule.

Suggest Edit

Published January 31, 2016 - 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