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

'** ' displays with error message on screen flow



The display of validation message for screen flow with 'Allow errors' enabled is inconsistent. 
For a mandatory field when no data is entered, client side validation is triggered and validation error appears below the property. However, when the user navigates to the next assignment and comes back to the previous assignment, the validation error appears with ** pre-pended to it.

This behavior is observed post Pega 7 platform upgrade.

Error Messages

** Value cannot be blank

Steps to Reproduce

  1. 'Allow errors' is checked on screen flow
  2. With validation error on first screen, navigate to next flow action.
  3. On navigating back to previous flow action '** ' is pre-pended to existing error message on screen.

Root Cause

The behavior of PRPC is correct and explained below.

1. If user does not enter value in a text input field marked as Required, then JavaScript runs and adds message "Value cannot be blank" to this Property. There is no interaction with server during this operation, everything is handled at browser level.

2. User navigates to next screen in Screen Flow that causes a request to be sent to server. While processing this request, the error message on the Property added on client side is updated on Property in the Clipboard.

3. When user navigates back to first screen, it causes a request to be sent to server. While processing this request, server has to send message on the Property to browser and for that, it evaluates the messages on Property. During this evaluation, it tries to find Rule-Message with name "Value cannot be blank", but it cannot find one, and so it pre-pends ** to the message and it becomes "** Value cannot be blank". And, this is the reason, user now sees message as "** Value cannot be blank".

The behavior to pre-pend "** " to message is as per contract of Rule-Message. Check documentation of PublicAPI.getRuleMessage().


This is a valid documented behavior of PublicAPI getRuleMessage which adds '** ' when a Rule-Message is not found.

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