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

Screenflow navigation issue

SA-9442

Summary



The navigation in screen flow is not functional. In the final step in screen flow, if there are Page Messages set by Page-Set-Messages method, the screenflow harness does not respond to mouse clicks.

Error Messages



No errors.

Steps to Reproduce



At the last screenflow assignment associate a Post Processing activity with Page-Set-Messages method. The harness will no longer respond to mouse clicks. 

Root Cause



This is a customization issue, the TabbedScreenFlow7 has been changed in the custom application which caused the reported screen flow harness navigation issue. The standard PRPC TabbedScreenFlow7 Harness is using the client runtime version of 05-03 specified in the Advanced Tab. In the custom harness, the Client runtime version 06-02 used.



Resolution



Use Client runtime version of 05-03 in the screenflow harness.
Suggest Edit

Published May 11, 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