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 causes OperationFail error



After upgrading from Pega 7.1.6 to Pega 7.1.7 the @hasMessages function does not work as expected. Error is generated when using the function.

Error Messages

@OperationFail() || @hasMessages(Param.WorkObjectPageName) null

Steps to Reproduce

1. Use @hasMessages in an activity.
2. Call this activity from the post action of the flow action to observe the issue.

Root Cause

The issue occurs when you remove pyWorkPage in post processing activity of flow action.


The issue is resolved in Pega 7.1.8.
Suggest Edit

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