User task
A task where a user needs to perform a specific activity within a process engine or application. For example, the user is prompted to enter their details on a form.
Attributes: General
Attribute | Description |
---|---|
Model ID | The unique identifier of the element within the process model. |
Name | The name of the element displayed in the diagram. |
Documentation | A description and any additional information about this element. |
Attributes: Assignment
Attribute | Description |
---|---|
Candidate users | Defines a list of users that can become assignee by claiming the task. |
Attributes: Details
Attribute | Description |
---|---|
Form reference | Reference to the form that will be displayed when this task is opened. |
Task listeners | Allows you to invoke Java logic after the creation, reassignment, completion and deletion of the task. |
Task ID variable | An optional variable that contains the ID of the task. |
Form properties | Custom form properties which are used within the legacy or custom form engine. |
Attributes: Execution
Attribute | Description |
---|---|
Asynchronous | When enabled, the activity starts as an asynchronous job. |
Execution listeners |
Allows you to invoke Java logic after certain events:
|
Skip expression |
Defines an expression which is evaluated before executing the task. If it evaluates to true, the task is skipped. You must opt-in to enable this feature by setting a process variable |
Attributes: Multi instance
Attribute | Description |
---|---|
Multi instance type |
Determines if multiple instances of this activity are created:
|
Collection |
Expression to set the loop collection for a multi-instance task. The number of instances is determined by the elements of a collection. For each element in the collection, a new instance is created. A common use case is to loop over lists created by multi-element subforms. For example, if you bound a subform to an array of invoice positions using the expression |
Element variable |
The name of the variable where the currently processed item from the loop collection is stored, for example You can access the element in the process through an expression, for example |
Element index variable |
The name of the variable where the index of the currently processed item from the loop collection is stored, for example, The index starts with 0 and increases with every element that is being looped through. You can access the index in the process through an expression, for example |
Cardinality | A number or an expression that evaluates to an integer, which controls the number of activity instances that are created. If the attribute Collection is empty, a new instance is created for every element of the list. With cardinality, you can overwrite this and only create a given number of instances. You can also use this attribute if you want to loop over an activity a given number of times without specifying a collection. |
Completion condition | A Boolean expression that when true cancels the remaining activity instances, stopping the loop, and produces a token. |
Attributes: Visual
Attribute | Description |
---|---|
Font color | The font color of the element in the diagram. |
Font size | The font size of the element in the diagram. |
Font style | The font style of the element in the diagram. |
Font weight | The font weight of the element in the diagram. |
Background color | The background color of the element in the diagram. |
Border color | The border color of the element in the diagram. |