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

UI no longer displays Page Messages



Your application uses a screen flow with a Tree Navigation Harness. The harness includes the 'errors' section from Base Class. Each Flow Action has a post processing activity that includes screen/data entry validation. This validation generates user messages via Page-Set-Message method. Tracer shows the validation being processed and the messages being attached to pyWorkPage. However, once the processing/request is complete, the messages are no longer on the clipboard. This functioned correctly in 6.1sp2 but no longer functions in 7.1.8

Steps to Reproduce

  1. Create an activity with Page-Set-Messages.
  2. Attach as post-processing on a Flow Action.
  3. Generate a simple Screen flow, utilizing a Tree Navigation Harness.

Root Cause

This is an issue with pega system code,The error messages are set properly but are reset due to a rollback request to pzUpdateElementModel.


This issue is fixed pega 7.1.9 release.

This issue is resolved through the following local change:

Set pzKeepPageMessages to true in the safeURL before executing it. These changes are done in UserWorkForm of Pega-UIEngine:07-10-01 ruleset.

@protected Rollback element updates caused by popups launched from tabs. 
@return $void$ 
pega.u.d.rollBackElementUpdate = function(){ 
var winObj =; 
if(winObj && winObj.document && winObj.document.getElementById('workarea')){ 
var oSafeURL = SafeURL_createFromURL(pega.u.d.url); 


Suggest Edit

Published July 17, 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