Support Article
Clicking Previous button does not return to prior assignment
SA-29682
Summary
A flow has been configured with a question shape, subflow, and question shape.
In the subflow, there are multiple question shapes with a decision shape prior to each to skip over if necessary. If the user runs the flow and all of the questions in the subflow are skipped, the user is not able to use the Previous button to go back to the first question. Instead, the user is returned to the same question.
Error Messages
Not Applicable
Steps to Reproduce
- Navigate through the flow, with all logic in subflow resulting in those questions being skipped.
- When on the third shape in the main flow press the Previous button.
Root Cause
An issue in the custom application code or rules.
The main flow and subflow have been configured as standard flows and a custom Previous button has been configured to execute the "pega.u.d.handleActionEvent" script with ActionScreenFlow as the parameter.
When the Previous button is clicked, the script is executed and calls the GoToPreviousTask activity with the previousEntryPoint parameter set to true.
This results in the flow being returned to the subflow, where the decision shapes are once again evaluated so the questions in the subflow are skipped and flow processing continues back to the third shape in the main flow.
Resolution
Perform the following local-change:
Configure the Previous button to use the same code used for the Back button in the out of the box TabbedScreenFlow7 harness.
The parameter value in the screen shot below is "pyActivity=GoToPreviousTask&previousAssignment=true".
Published November 8, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.