User task

Usert task activity is a typical “workflow” Task where a human performer performs the Task with the assistance of a software application and is scheduled through a task list manager of some sort.


Exclusive	When it receives a special job from a specific process example, it makes jobs run in order.
Execution listeners	Listeners for an activity, process, sequence flow, start and end event.
Multi-instance type	Determines if multiple instances of this activity are created.
Cardinality (Multi-instance)	An expression or numeric value (integer) that determines how many instances are created.
Collection (Multi-instance)	The number of instances is determined by the elements of a collection. For each element in the collection, a new instance is created.
Element Variable (Multi-instance )	The variable under which each element is available to the newly created instance.
Completion Condition (Multi-instance)	An expression that, if it evaluated to `true` , stops the creation of new instances.
Is for compensation	A flag that identifies whether this activity is intended for the purposes of compensation.
Assignments	Defines the assignee of a task. The assignee is the person who is responsible for the completion of a task. By default, the assignee is set to `$INITIATOR` which is a special variable that is set to the user who started the process. It is possible to set the assignee directly or through an expression. In both cases, the expected value is the User ID of the assignee.
Form key	Form key that provides a reference to a form.
Form reference	The form associated with the User Task. Once a user opens the task, he or she is presented with the referenced form. It is possible to create a new form, reference an existing one or delete the current reference.
Validate form fields	If the form is submitted and validate form fields expression evaluates to true, form fields are validated on the back send according to the form model restrictions.
Due date	The due date of the task.
Priority	An integer number denoting the priority of the task.
Form properties	Sets the form properties.
Task listeners	Sets Task Listeners for this task

Execution listeners examples

You can use the Execution listeners as shown in the examples.

Start

End

Take

Multi-instance type examples

You can use the Multi-instance type as shown in the examples.

Default, only one instance is created:

None

Activities are created in parallel. This is a good practice for User tasks activity:

Parallel

Activities are created sequentially. This is a good practice for Service tasks activity:

Sequential

Cardinality (Multi-instance) examples

You can use the Cardinality (Multi-instance) as shown in the examples .

${number}

2

Collection (Multi-instance) example

You can use the Collection (Multi-instance) as shown in the example.

2

Element variable (Multi-instance) example

You can use the Element variable (Multi-instance) as shown in the example.

elementvar

Completion Condition (Multi-instance) example

You can use the Completion Condition (Multi-instance) as shown in the example.

true

Expression examples

You can use the Expression as shown in the examples.

${firstName}

${clientService.createNewClient(firstName, lastName, email)}

Result variable name example

You can use the Result variable name as shown in the example.

resultvar

Skip expression example

You can use the Skip expression as shown in the example.

${firstName}

Task listeners examples

You can use the Task listeners as shown in the examples.

Occurs when the task has been created and all task properties are set:

create

Occurs when the task is assigned to somebody. Please note that the Assignment event is fired before the Create event:

assignment

Occurs when the task is completed and just before the task is deleted from the runtime data:

complete

Occurs just before the task is going to be deleted or completed:

delete