Workbasket assignment with screenflow transfers Item to worklist
After a flow routes an object to a work basket, user that opens the assignment and close it without submitting any screen, find the assignment in their own work list when they expect it to remain in the work basket.
Steps to Reproduce
- Use a utility shape in a process flow to route work to a work basket.
- Connect the utility shape to a subprocess shape that launches a screen flow.
- After running the flow, click the assignment from the work basket and close it.
- Observe that it is now in your work list.
As described in the documentation, screen flows may only be routed to work lists and not work baskets.
Even though the utility shape routed the assignment to a work basket, and even all explicit routing was removed from the screen flow, the standard routing to the work list was still performed when the screen flow starts.
A safe way to handle this is to design the process flow to include an assignment shape and flow action that routes to the work basket before the screen flow is launched.
That way, when the user clicks the assignment from the work basket, they will be on that screen, and as long as they close the assignment without advancing the flow, the assignment will remain in the work basket.
0% found this useful