Question
Back button not visible
We are having a screenflow where we have assignment 1, after that we have a decision shape and that decision shape outputs go to separate assignments. But in those assignments we are not able to see the Back button. When traced, hasPreviousAssignment was evaluating to false.
We are facing this issue after upgrading from 7.1.5 to 7.4. in 7.1.5, we traced and found that when rule hasPreviousAssignment was evaluating to true.
Has anyone faced this issue?
***Moderator Edit-Vidyaranjan: Updated SR details***
Hello,
Can you dig a little dipper.
The function basically check like this :
@(Pega-ProcessEngine:FlowUtilities).findPreviousEntryPoint(tools, myStepPage, newAssignPage.pxFlowName)
Can you see the information present in newAssignPage, the pxFlowName and also the step page info at that point of time.
May be running tracer when forwarding the assignment can give you these details.
Hello @avisekmondal,
Upon reviewing the associated Support Request, the resolution was as follows:
- Create custom buttons. The user can see the current configurations in the pyScreenFlow7Footer section.
- Modify the screen flow so the assignments do not loop back to the first assignment. The user could set a flag from Assignment 4 and Assignment 5 flow actions, and then modify the calling flow to re-enter the screen flow when the condition is met.
Accepted Solution
Thanks Pallavi.
I raised one SR for this and got the exact same response u provided. I went with the 2nd approach and it solved my problem. As per the SR update, the reason for not showing the back button was "The screen flow navigation buttons do not support looping back to another assignment. The step data is stored in the pyFlowData page. When an assignment loops back to the first assignment, it causes another entry to be added to the page for the future step. Since the assignment is then listed as a future step, the Back button does not appear.".
My only question was it was working in 7.1.5 but not in 7.4. And I created a new flow in 7.4 and observed the same behavior. So is something updated in this logic?
Hi @avisekmondal,
I took a look at your SR and I see that the Engineer advised that she encountered the same behavior and it doesn't look like the functionality changed, but there may be something different in your flow or maybe different rules were used. She had also confirmed with the subject matter expert of this.
Is the issue only with upgraded screenflows, or for the newly created flows as well? Can you check once and let us know.