Save in screenflow takes user to Review harness
SummaryScreen flow is used to display screens. Out of the box pyCaseHeader is included in the TabbedScreenflow7 harness. Click Save button to save the work object. Instead of staying on the same screen user is taken back to Review Harness.
No error message. User is directed to the Review harness instead of staying on the same screen.
Steps to Reproduce1. Create screen flow to display the screens.
2. Include OOTBpyCaseHeader in the TabbedScreenflow7 harness.
3. At runtime, click Save button to save the WO while in the screenflow. Instead of staying on the same screen, user is taken back to Review Harness.
The root cause of this problem is a defect in Pegasystems’ code/rules. There is currently no Save button present in the out of the box screenflow harness.
This issue is resolved through the following local change:Approach #1:
Create a stub section with a regular layout and specify the CSS Class as “pyActionArea”
Include this stub section on your TabbedScreenFlow harness. Approach #2:
Change Save button Action from “Save” to “Run Script”.
Call the doSave JS function and pass below parameter/values.
Published March 12, 2016 - Updated October 8, 2020