If you create a custom application that uses a workflow, create in-baskets to provide a list of work items in a queue that are to be processed by users who are members of a certain role.
You can define multiple in-baskets for the same queue with each in-basket showing different items, as specified by a pre-defined query. By assigning specific roles to process each in-basket, each user (role member) sees only the types of work appropriate for the role they are performing.
To define an in-basket:
Option | Description |
---|---|
In Process Configuration Console, | Select the queue where the in-basket will display, and click Properties on the toolbar. Click the In-baskets tab. |
In Process Designer, | Select View > In-baskets. Select the queue. |
The name must be unique for each in-basket in the selected queue, and the name should provide a clue about what kinds of work items are in the in-basket.
To use system fields, such as the workflow subject or time a work item was created, select Show system fields and select the fields.
You must select at least one field that is displayed for the items in the in-basket.
The name should give the user a clue of what the filter will show.
The list contains the exposed fields selected as columns for the in-basket. To select from all of the expanded fields on the queue, click the "..." button and select the field.
Example: For a filter named Amount of sale, you might select Field SaleAmount and Operator is less than. This filter enables the user to display only work items where the SaleAmount is less than a number the user enters.
To create a filter to define In-basket contents:
You can also edit the code directly in the box.
If you select Allow all content, you can also optionally select to show work for all users. For example, this option might be useful if you use IBM® Case Manager and you want to give access to one person so that they can delegate work. From an API perspective, selecting Show Work For All Users, sets the flag on the WorkBasket. This flag would allow the user of the WorkBasket to query for all items, not just those the user is bound. This flag is only useful for WorkBaskets that are associated to a QUEUE_TYPE_USER_CENTRIC type queue.
An index optimizes retrieval of the list of items that satisfy the filter, and also ensures that the items in the in-basket are sorted in a logical order. For example, if participants should process items in order as they enter the system, you can select the pre-defined F_fifo index. If there is a more logical order, such as shipping location, you should define an index for the shipping location value on the queue and select it here.