More about Workbasket data instances
|
|
You can create any number of workbaskets in any structure that fits your organization.
Your flows can route assignments to people or to workbaskets. Your flows can use any of the standard router activities, or your own router activities to place assignments into workbaskets. Your custom router activities can, for example, determine which workbasket is most appropriate to receive the newly created assignment based on how much work is already in the workbasket, skills of those users associated with the workbasket, or other criteria.
Managers can review the assignments placed in a workbasket and distribute them one-by-one to appropriate users for processing. Alternatively, a background agent can reassign assignments from the workbasket periodically to a user's worklist.
As a best practice, create a workbasket named default@<organization> for each organization in your system, and review the assignments in that workbasket from time to time. Certain standard routing activities use this workbasket as a last resort when no other suitable destination can be found for an assignment.
As a best practice, never delete a workbasket that may contain assignments, or a workbasket that may be referenced somewhere in a rule in an application.
|
|
agent, assignment, router activity, skill, worklist |
|
|
Maximizing user productivity with GetNextWork |
|
|
Atlas — Initial workbaskets |