Service task

Service task activity uses some sort of service, which could be a Web service or an automated application.


Exclusive	When it receives a special job from a specific process example, it makes jobs run in order.
Set service task to be triggerable	Sets service tasks to be triggerable. This makes it possible that an external trigger determines when to continue the execution of the process once the Service Task was executed.
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.
Class	Class that implements the service task logic.
Expression	An expression which is resolved once the task is executed.
Delegate expression	Service task logic defined with a delegate expression.
Class fields	Class fields make it possible to inject field values into your delegated class.
Result variable name	The name of the variable in which the result of the Service Task’s execution is stored.
Use local scope for result variables	Indicates whether to store the result variable as a local variable.
Skip expression	Defines an expression which is evaluated before executing the 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}