Chained Execution
Chained Execution allows you to specify that a user will automatically start the next work item in the same process instance as soon as the previous one has completed.
To set up a chained execution pattern, you refactor the required user tasks as an embedded sub-process, and mark the sub-process to use chained execution.
User tasks that are to be chained together must meet the following requirements:
- They can be assigned to different Participants, but they will still be offered to the same user if that user qualifies under the participant definitions for each task. For example, if one task is assigned to a position and the second to a group, a user who both holds that position and belongs to that group can be given both tasks. If the user is not a member of the group, the second task will be offered to each of the group members.
- They must have Offer to All as their Distribution Strategy (see Offering and Allocating Work).
For instructions on chained execution, see the information in the tutorial How to Ensure that a Sequence of Tasks is Performed by the Same User and the TIBCO Business Studio Modeling User’s Guide.
For information on the properties that influence how a chained execution pattern operates at runtime, see the WPProperties.properties file in the "BPM Properties Files" section of the TIBCO ActiveMatrix BPM - BPM Administration guide.