Assignment Finishes on Screen Refresh
In a screen flow, the assignment seems to be finished when screen is refreshed (F5 key) after OOTB "Back" button is pressed.
In a screenflow, after coming back from a step, refreshing the screen will lead to a confirm harness.
Steps to Reproduce
- Create a screenflow with two steps.
- Run the flow, advance to the second step and then come back to the first step.
- Do F5 refresh.
- Instead of showing the step which we were in, before refresh, it shows a confirm Harness.
The root cause of this problem is a defect in Pegasystems’ code/rules.
This behavior is not actually an issue because when the screen refresh is done, a Confirm harness is shown. However, you still have a link in the case contents to enter into the flow.
And the audit trail was clear enough and never showed that the assignment is finished. But displaying the Confirm harness on refresh(F5) can sometimes lead to loss of the data that was entered in the Perform harness.
This behavior is caused by the HarnessID parameter not being passed on before PRPC closes the window.
This issue is resolved in Pega 7.1.7.
Here’s the explanation for the reported behavior:
In Pega 7.1.7, changes are made in code such that the HarnessID becomes a parameter for all the server requests made, before and after closing the window. This helps in loading the correct Harness even after a screen refresh is done.
Published July 27, 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.