Pattern 24 (System-Determined Work Queue Content)
The ability of the system to order the content and sequence in which work items are presented to a resource for execution.
Depending on the configuration specified in the process model, the workflow engine presents work items to resources either in order of work item priorty or date created.
This pattern provides the system with the ability to specify the ordering and content of work items in a resource's work list. In doing so, the intention is that the system can influence the sequence in which concurrent work items are executed by resources by managing the information presented for each work item.
Where an offering provides facilities for specifying the default ordering in which work items are presented to resources, the opportunity exists to enforce a work ordering policy for all resources or on a group-by-group or individual resource basis. Such ordering may be time-based (e.g. FIFO, LIFO, EDD) or relate to data values associated with individual work items (e.g. cost, required effort, completion time). The ordering and content of work lists can be specified individually for each user or on a whole-of-process basis.
There are no specific context conditions associated with this pattern.
Where this concept is supported by individual PAIS, it is generally done so in terms of a single ordering sequence for all resources. Both Staffware and iPlanet support the ordering of work items on a priority basis for each resource's worklist. In both cases they also support the dynamic reordering of worklists as the priorities of individual work items change.
An offering achieves full support if it satisfies the description for the pattern.
To achieve a + rating (direct support) or a +/- rating (partial support) the product should satisfy the corresponding evaluation criterion of the pattern. Otherwise a - rating (no support) is assigned.
|Staffware||9||+||Directly supported with work items ordered by priority|
|Websphere MQ Workflow||3.4||-||Not supported|
|FLOWer||3.0||+||The system presents work items in order of execution sequence|
|iPlanet||3.1||+||Work items are ordered by priority by default|
|Oracle BPEL||10.1.2||-||Oracle BPEL PM does not impose a default ordering of the work items in the resources work queue, thus offering no support for this pattern.|
|jBPM||3.1.4||-||jBPM does not support this pattern.|
|OpenWFE||1.7.3||-||OpenWFE does not support this pattern.|
|Enhydra Shark||2||-||Enhydra Shark does not support this pattern.|
Summary of Evaluation