Page History
...
| Name | Description | Type | Required |
|---|---|---|---|
| Users | Expression which contains the ID of the user to which the task will be assigned, this can be multivalued. | Expression | No |
| Teams | Expression which contains the teams to which the task will be assigned, this can be multivalued. | Expression | No |
| Roles | Expression which contains the role to which the task will be assigned, this can be multivalued. | Expression | No |
| TaskId | The task id of the task to be assigned. | Expression | Yes |
| CaseId | The id of the case for which the task should be assigned | Expression | Yes |
Routing
When calling this service it always sets a value in the task table (column IsUserSet) in the background. This value indicates whether a task is assigned explicitly to someone. In case at least one parameter of this service is specified the value will be 1 in the database; when nothing is defined the value will be 0 (unassigning a task). This value is used for the reevaluation of tasks by the routing algorithm. Please refer to 'Overwrite manual assignments' at the page Routing Algorithms.
Unassign tasks
To unassign tasks add this service with empty parameters in the flow. Triggering this service (at runtime) will clear the assignee. This might be helpful to let the routing algorithm take control of the task assignments
| Note |
|---|
Unassigning a task clears the task of all routing, effectively authorising everybody to execute the task. |
Overview
Content Tools