User Task Activity
The User Task activity enables the integration of human interaction within a business process by assigning specific tasks to performers. It utilizes a task list manager to schedule work and provides users with necessary forms and applications to complete their assigned actions.
| Field | Description | Requirement |
|---|---|---|
| Exclusive | Ensures that jobs originating from a specific process instance are executed sequentially. | Optional |
| Execution listeners | Configures triggers for events related to activities, processes, sequence flows, or start and end events. | Optional |
| Multi-instance type | Determines whether the activity generates multiple instances and defines their execution order. | Optional |
| Cardinality (Multi-instance) | Defines the number of instances to be created using a numeric integer or an expression. | Optional |
| Collection (Multi-instance) | Specifies a collection variable where each element triggers the creation of a new instance. | Optional |
| Element Variable (Multi-instance) | Sets the variable name used to represent the current element within a specific instance. | Optional |
| Completion Condition (Multi-instance) | Defines a boolean expression that, when evaluated as true, terminates the creation of further instances. | Optional |
| Is for compensation | A flag indicating if the activity is designated for compensation logic within the workflow. | Optional |
| Assignments | Defines the User ID responsible for the task, defaulting to the "$INITIATOR" variable. | Required |
| Form key | Provides a string-based reference or identifier for an external form. | Optional |
| Form reference | Links a specific form model to the task to be displayed upon user interaction. | Optional |
| Validate form fields | Enables back-end validation of submitted form data against defined model restrictions. | Optional |
| Due date | Specifies the deadline for the completion of the task. | Optional |
| Priority | Assigns a numerical value to indicate the relative importance of the task. | Optional |
| Form properties | Configures specific metadata and attributes for the associated task form. | Optional |
| Task listeners | Sets listeners to trigger logic during specific task lifecycle stages. | Optional |
Action Types & Examples
Execution Listeners
- Format: String (event type)
- Example Result: "start"
Multi-instance Type
- Format: String (None, Parallel, or Sequential)
- Example Result: "Parallel"
Cardinality
- Format: Integer or Expression
- Example Result: "2"
Completion Condition
- Format: Boolean Expression
- Example Result: "${variable==True}"
Task Listeners
- Format: String (lifecycle event)
- Example Result: "create"
Implementation Examples
Field Setup - Assignee: ${INITIATOR} - Form Key: registration_form_01 - Priority: 50 - Due Date: 2023-12-31T23:59:59
Execution Parameters - Multi-instance Type: Parallel - Element Variable: elementvar - Skip Expression: ${firstName} - Result Variable Name: resultvar
Technical Notes
The User Task activity is designed for human-in-the-loop workflows. When configuring Multi-instance types, "Parallel" execution is generally preferred for User Tasks to facilitate concurrent work, while "Sequential" is typically utilized for Service Tasks. Note that "Assignment" events are triggered by the system prior to "Create" events within the Task Listener lifecycle. All expressions must follow standard syntax to ensure the Task List Manager resolves User IDs and variables correctly at runtime.