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 is show on the screen with Property Names



User reported that when the grid is used in a Flow Action of a Screen flow, the errors of the Page entry in a page list is copied to Primary Page.

Error Messages

Error message on the screen displayed by tabbedScreenFlow7 in below format.

<Property Name > : Error Message

Steps to Reproduce

1. Create a Repeating Grid, with data source as Report Definition.
2. Create a 3 different properties with validation (validate using edit validate rule).
3. Create a flow Action addressing the Repeating Grid related section.
4. Create a flow and provide the flow action
5. Run the flow. 
6. Enter some value on the any one text field in the grid and press tab key.
7. The errors on the page list will be shown on the top of the screen with property names.

Root Cause

It's an expected behavior, tabbedScreenflow7 rule form will display error messages followed by property names.


Folloiwng explanation is provided to the user:

xplained user that the OOTB FormErrorMarker HTML Fragment displays the error message in below format:
                      Property name : error message
                      In case if user wants to display the form errors in different format, then can use the custom error section configuration available in harness (tabbedscreenflow7)rule form and write user own logic to  generate the error messages.

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