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 fails for screen flow



You can set the routing on the Start shape of a screen flow and route it to a workbasket. However, when the work object is created, the assignment fails because there is no operator with the same name as the workbasket.

Error Messages

Example on-screen error
Flow MyScreenFlow had an error in step ASSIGNMENT66: Unable to open assignee's Data-Admin-Operator-ID record HeadingWrap

Steps to Reproduce

1. Create a screen flow.
2. On the Start shape, route the work to a workbasket.
3. Observe that the flow always fails.

Root Cause

Here is the explanation: A screen flow must be processed by a single user; therefore, it can be routed to a worklist only, not to a workbasket.
This is the expected behavior.


To route a screen flow to a workbasket, use the Suggested Approach in the following PDN Article:

Assigning work to a workbasket outside of the screen flow ensures that the assignment before the screen flow is assigned or routed to the workbasket and not to the screen flow itself.

Thus, when a user opens the assignment from the workbasket, it proceeds to the screen flow (using the ActionAutoSubmit method). In this way, the screen flow gets assigned to a single worklist specified in the screen flow Start shape. If no worklist is specified, it gets assigned to the current user's worklist.

Published March 21, 2017 - Updated October 8, 2020

Was this useful?

100% 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