Question
Evonsys
LK
Last activity: 2 Nov 2016 13:00 EDT
Screen flow back and next buttons are not working properly for some work objects
We got a production issue in screen flow where person cannot move to previous or Next screen by click on back/Next button . We have observe three cases in production last week
we have traced the issue for back and found out in GoToPreviousTask on step 8 jump condition 2nd conditon getting executed and it get fails and jump into rollback.
@OperationFail() - this is getting true
@determineDeferErrors(newAssignPage, myStepPage) - this is getting false
Can anyone please let us know why these functions getting thoese results
Note: In the screen flow we have checked save last step and proceed with errors.
***Updated by Moderator: Lochan. Removed user added #helpme tag. Apologies for confusion, shouldn't have been an end-user option***
Coforge Tech
US
one reason could be you would have error messages on clipboard, this could be of any reason saying you have some validations on the current flow action and you would not showing that page messages on the screen. So you are unaware of the reason.
Evonsys
LK
We have enable to move back and forth even with errors. this behaviour seen in few cases recently not all the cases. We are unble to find the root cause. In the trace it shows in GoToPreviousTask activity after executing 8th step it jumps to 19th step.
Activities we used to go back and next are ootb final rules
Evonsys
LK
We again got the same issue. please help
Pegasystems
US
If step 7 of GoToPreviousTask is obtaining a value back from determineDeferErrors that seems wrong to you, I suggest you use pega tracer and enabled all event types and all rulesets.
Examine the step page, primary page, and the parameters passed to determineDeferErrors, as well as the properties on those pages, particularly the properties looked at by the determineDeferErrors java, which you should study.
Hopefully, that will enlighten the situation. /Eric
Evonsys
LK
we already traced the. all are pega final rules. could not find any root cause why is behave differently only in production.