![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
To support the modeling of workflow patterns, the following sections are available on the Resource tab in the Properties view:
• Resources (user and manual tasks)
• Distribution Strategy (message events and user tasks)
• Piling (user and manual tasks)
• Separation of Duties (user and manual tasks)
• Retain Familiar (user and manual tasks)
In addition to the patterns on the Resource tab, you can also use Chaining, which is configured on an embedded sub-process (see Chained Execution).
You can also access the Retain Familiar and Separation of Duties resource patterns by selecting tasks, right-clicking, and selecting Resource Patterns:The participant in the Resources section is the same as the participant specified on the General tab, and specifies who or what completes the task (see Sub-Processes).You can specify the Initial Priority, which indicates the relative urgency with which the item should be completed. By default, the priority is 200 (normal level). You can edit this to be one of the values 400, 300, 200 and 100, with 400 being the one which would be processed first.
• Offer To All Select this option to specify that you want all users that match the participant definition to have the opportunity to accept or decline the work item. For example, if there is a claims handler organizational entity (such as a group), the work item is offered to all users in that group. Once a user opens the work item, it is allocated to them and removed from the work lists of other users in that group.
• Offer To One Select this option to specify that you want only one user that matches the participant definition to have the opportunity to accept or decline the work item. If the user declines the work item, it is offered to another user that matches the participant definition.
• Allocate To One Select this option to allocate automatically the work item to a user that matches the participant definition.This allows a user task to be configured to re-offer the work item to any valid user (as defined in Distribution Strategy) when the user closes or cancels the work item.To specify piling on a work item, select the May be piled checkbox and specify the maximum number of items to pile. For example:
• On the Resources tab in the Properties view for the task
• On the Task Groups tab in the Properties view for the processIn this example, all three tasks are assigned to the same organization unit. The Take Details task is allocated to a resource from the organization unit. Because the Followup task is in the same Retain Familiar group as the Take Details task, they will be allocated to the same resource as well.
• On the Resources tab in the Properties view for the task
• On the Task Groups tab in the Properties view for the process
You can refactor existing tasks into an embedded sub-process as described in Embedded Sub-processes.The following example shows a very simple chain of two user tasks in an embedded sub-process. Note that you can include other types of task, such as script tasks, in between the chained user tasks. However your system administrator must take into account the time likely to be taken up by these other tasks when setting the properties in the "Chaining" section of the WPProperties.properties file. See the section "Configuring Chained Work Patterns in TIBCO ActiveMatrix BPM" in the TIBCO ActiveMatrix BPM - BPM Administration guide for details of this file.In the Properties view for the embedded sub-process, select Chained Execution in the Properties view:
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |