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

Error message not displayed on the UI in mobile



User has server side validation that is managed within an activity. The activity sets up an error on property using Property-Set-Messages method.
The activity is fired when user clicks on flow action submit action button.
The Activity sets the message and user can see it on the tracer but it is not displayed on the section.

Error Messages

Not Applicable

Steps to Reproduce

1. Create a mobile application.
2. From a harness set a link that will open up an overlay with a search option with an autocomplete.
3. On select of an autocomplete another overlay is displayed where there is a link to an overlay.
4. On the third level of an overlay when click on Submit action button, a validation activity runs and sets an error on a context page property that is displayed on the screen.
5. Check on a tracer that the error is set on a property.

Expected behaviour:
Expecting the Out-of-the-box (OOTB) error message to be displayed on the property on currently visible overlay.

Incorrect behaviour:
If you run the test on desktop using mobile simulation, you will be able to see that the error msg is displayed on the top of the harness.

Root Cause

A software use or operation error, the page context as pointed incorrectly in the flow action where the target was set as an 'overlay', the page created belonged to the parent work class.


Changing the page context pointing to data class in flow action resolves the issue.
Suggest Edit

Published December 18, 2017 - 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