User Tasks

A "user task" in a BPMN journey is an activity that requires human intervention in a business process. When a process instance reaches a user task, a job is created, and the process instance pauses until the job is completed. Users can use automatically assigend to these tasks, or a job worker can manually subscribe to it.

Key characteristics of a user task:

Attributes:

The following are the attributes associated with the "User" tasks:

Attribute	Description
ID:	The "Id" attribute represents the unique identifier of the user task. It corresponds to the task definition key in the BPMN model.
Name:	The "Name" attribute defines the name or label of the user task.

Assignments:

Assignments determine who can handle the task and can include the following attributes:

Attribute	Description
Assignee: Default:${startedBy}	The "Assignee" specifies the user who is assigned to the task. To dynamically determined during task execution it's represented as an EL (Expression Language) expression. By default it is "${startedBy}" indicating that the assignee is the user who has Started the BPMN journey.
Candidate Users:	The "Candidate Users" attribute can be used to specify a list of users who are potential candidates for completing the task. This field may remain empty or be populated with user identifiers based on the process requirements.
Candidate Groups:	The "Candidate Groups" attribute allows you to specify groups of users who are eligible candidates for the task. This field may contain one or more group identifiers based on the process design.

Scheduling:

User tasks support specifying a task schedule which helps define when users should interact with the task and includes:

Attribute	Description
Follow Up Date:	The "Follow Up Date" attribute is used to define the date when a follow-up action should be taken regarding the task. It can be expressed as an EL expression (e.g., "${someDate}") or in ISO date format (e.g., "2015-06-26T09:54:00"). This date is a reference point for scheduling future interactions with the task.
Priority:	The "Priority" attribute can be used to set the task's priority level. The specific values for priority levels may be defined in accordance with the business process requirements.
	The "Due Date" attribute specifies the deadline for completing the user task. Similar to the "Follow Up Date," it can be expressed as an EL expression (e.g., "${someDate}") or in ISO date format (e.g., "2015-06-26T09:54:00"). The due date serves as a critical time constraint for task completion.

Asynchronous Continuations:

Asynchronous continuations are used to specify whether a task is executed asynchronously, they include:

Attribute	Description
Asynchronous Before:	The "Asynchronous Before" attribute indicates if the task can be started asynchronously before other tasks or events in the process.
Asynchronous After:	Similarly, the "Asynchronous After" attribute denotes whether the user task can be completed asynchronously after other tasks or events in the process.

---