The End Assignment Task terminates the scope of an Assignment Task
where its subscriber set overrides and is inherited by its in-scope
tasks. In other words, it defines the end of an Assignment Block.The End Assignment Task terminates the scope of an Assignment Task
where its subscriber set overrides and is inherited by its in-scope
tasks. In other words, it defines the end of an Assignment Block.
Note: Assignment and End Assignment Tasks are not in the available subset of allowed tasks under a Progression Lite license.
When an End Assignment task is reached by a work item that is currently within the scope of an Assignment Block, this scope is terminated. Now subsequent user-attended tasks encountered by the work item will have their subscribers determined by their own Assignment Rules configured on their own Assignment Tab – Until the next Assignment Task is encountered beginning a new Assignment Block.
|
Progression Task |
End Assignment Task Description |
|
|
An End Assignment Task is used to terminate the override and inheritance of the computed Assignment Task subscriber set by in-scope Tasks in the Assignment Block. Subsequent user tasks for the current work item will be assigned by either inheritance in another Assignment Block or by the configured explicit assignment rules for each user-attended Task. |
The tabs for multiple types of tasks that the End 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
The following example shows an Assignment Task (#1) followed by its corresponding End Assignment Task (#2) that are used to establish a scope that controls the assignments on all of its paths for Manual-User Tasks and Exception Tasks.
Manual-User and Exception Tasks are the only tasks that have subscribers since they are user-attended. The Assignment Task and the End Assignment Task are both automatic tasks that establish and terminate an Assignment Block where its subscriber set is inherited and overrides the assignment rules that may have been configured locally for its in-scope tasks.
Note: Only the unconnected default-Exception Task, always uses its own Assignment Rules to determine its own subscriber set, even when an Assignment Block is in effect.
The Assignment Block scope – Terminated by the End Assignment task in the above Process diagram is discussed in the in the Subscriber Assignments Overview and the Assignment Task topics.
Note: Should an End Assignment Task be bypassed by exiting the process (e.g., as with the ‘Order Cancelled’ Finish Task, shown above), the Assignment Block is also terminated by default, without raising an exception).
An Assignment Block consists of two parts: Its beginning Assignment Task and its concluding End Assignment Task when encountered.
However like Finish Tasks, multiple End Assignment Tasks can appear in a process diagram and any End Assignment Task will serve to terminate an Assignment Block (i.e., terminate the scope of an Assignment Task).
Should an End Assignment Task be reached when no Assignment Task scope is established, the automatic End Assignment Task has no effect and passes the work item forward to the next task.
Note: An Assignment Task must be completed by an End Assignment Task before another Assignment Task is reached in the workflow; Otherwise, an Exception Condition will be created.
