Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

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.

Planning for and naming workbaskets

Updated on April 29, 2019


A system administrator asks:

As a general rule when estimating the number of workbaskets for an application, is it reasonable to assume "one workbasket per role" as an initial approximation?



Suggested Approach

Access roles provide one approach to determining how many workbaskets to include in an application design. Another approach might be to consider the number of unique instructions associated with assignments - and plan to create that number of workbaskets.

For example, if your application has one assignment instructing the users to collect available rates, another to verify employment, and a third to crosscheck references, you may want three workbaskets.  That way, a pool of workers can draw assignments from a designated workbasket to handle common tasks. 

When you create and organize workbaskets based on intent rather than by user role, it allows role reclassification and/or renaming to occur later without impact on the workbaskets specified in flows rules.

Have a question? Get answers now.

Visit the Support 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us