With an automatic Assignment Task, you have the ability to
define a team of subscribers that will be inherited as the subscriber set for all subsequent
workflow tasks
until an End Assignment Task is encountered to terminate the scope of
this inheritance.
Note: Assignment and End Assignment Tasks are not in the available subset of allowed tasks under a Progression Lite license.
The Assignment Task subscriber set inheritance scope is also referred to as an ‘Assignment Block’ that has a beginning and an end when an End Assignment Task or a Finish Task is encountered by a work item to terminate its block-scope.
Note: Any End-Assignment Task that is encountered by a work item can serve to terminate the same Assignment Task’s block-scope.
The Assignment Task’s computed subscription set is Always Inherited and Overrides any local task-assignment rules for the user-attended tasks within the scope of its Assignment Block.
The user-attended task types are the Manual User Task and Exception Task. As user-attended tasks are connected in a workflow diagram they may fall within the scope of an Assignment Block and be subject to inheritance of its computed subscriber set for each work-item task.
However, the default and unconnected Exception Task always retains its own explicit Task Assignment Rules that determine its subscriber specialists for each work-item that may arrive when unexpected problems occur even when an Assignment Block scope is in effect.
Since the unexpected-exception condition causes the work item to jump out of the normal workflow to be received by the default-and-unconnected Exception Task, it remains ‘out-of-scope’ so it is unaffected by Assignment Block inheritance and its attended subscribers may perform a ‘Return to Flow’.
A ‘Return to Flow’, where an Assignment Block scope was previously in effect, will resume the workflow within the same Assignment Block scope.
|
Progression Task |
Assignment Task Description |
|
|
An Assignment Task defines the resource(s) to be assigned and accessible when inherited by attended-user tasks within the scope of the Assignment Block it establishes and delimited by either a corresponding End Assignment Task or a Finish Task (i.e., exiting the Process). Tasks within the scope of an Assignment Block will always inherit their subscriber set for the work-item task from the Block-level. Note: Manual User Tasks and Exception Tasks are attended-user tasks. |
The tabs for multiple types of tasks that the Assignment Task has in common with other tasks are listed with x-marks in the grid (above) and they are explained in detail in a previous section (Task Definition – Common Tabs).
