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

hasMessages() function not working as expected



hasMessages() function is not returning correct value. Even though the Primary page or StepPage or specific named page got message, it is returning false.

Error Messages


Steps to Reproduce


Root Cause

The root cause of this problem is a defect in customer application code/rules. Using Primay page or stepPage will not return correct value for hasMessages() function.


This issue is resolved through the following local change: 
This function hasMessages() works only when there is no step page defined.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

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