But due to below reasons, those two approaches are not acceptable by developers. Can anyone give some inputs on how to achieve this?
1) Temporary display of Auto Submit screen is poor behavior and user experience. We stripped the Auto Submit screen down to nothing but the Java Script, so it is just a blank screen, but the unecessary reloads of the screen are poor user experience.
2) Even before reviewing the content of the first screen in the screen flow, the assignment has already been removed from the workbasket and placed in the current viewer's worklist.
Do you have to have the screen before the screen flow auto submit? Could you just have that screen before the screen flow and have the user that picks up th assignment sumbit that flow action to proceed to the screen flow?
The requirement does not allow for this additional screen with no information on it. That is why users attempted auto-submit, which was still too disruptive to the user. We cannot put data on this additional screen, as it’s user experience deviates from that of a screen flow, and the requirement dictates a screen flow user experience. Therefore, this also is not an acceptable workaround.
Posted: 5 years ago
Posted: 9 Oct 2015 5:26 EDT
Marc Alderman (Marc Alderman)
Senior Software Solutions Engineer
That didn't solve the problem, still an unnecessary refresh happens because of auto-submit. And the screenflow will be assigned to worklist of user, who have tried to open the WO from WorkBasket even before they view the first screen of the Screenflow.