Hi All,
In our application, there is a screen flow( 3 assignments) in which the routing is configured to WB(at the start shape). When user is clicking on Next button of the first assignment then that case is routed back to WB and user again has to click on Go button to work on the next assignment.
User don’t want to click on Go button after every assignment, so how can we achieve this?
In a screen flow, this behavior is expected if the assignments are routed to a workbasket/work queue. After the user submits the current assignment, the next assignment is placed back in the work queue, so the user has to click Go again to pick it up.
Screen flows are typically intended for a single user interaction pattern. So If the requirement is for the same user to continue seamlessly across all 3 assignments, then the screen flow should generally stay on the user’s worklist at the start shape.
You either need to convert the design to standard process flow or include a placeholder assignment just for the sake of routing the task from WB to worklist.
one approach I could think of, which should work in theory but I dont recommend, is to invoke a DT on the connector, and use the OOTB custom router activity to route process to a Worklist.
As above mentioned, this is expected behaviour.
