Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Workbasket assignment with screenflow transfers Item to worklist

SA-31840

Summary



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.


Error Messages



Not applicable


Steps to Reproduce

  1. Use a utility shape in a process flow to route work to a work basket.
  2. Connect the utility shape to a subprocess shape that launches a screen flow.
  3. After running the flow, click the assignment from the work basket and close it.
  4. Observe that it is now in your work list.


Root Cause



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.


Resolution



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.

Published January 5, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us