Call activity

A Call activity identifies a point in the Process where a global Process or a Global Task is used. The Call activity acts as a ‘wrapper’ for the invocation of a global Process or Global Task within the execution. The activation of a call activity results in the transfer of control to the called global Process or Global Task.
Exclusive When it receives a special job from a specific process example, it makes jobs run in order.
Complete asynchronously Executes the completion of the call activity in an exclusive asynchronous job. This is for example useful in combination with parallel multi-instance.
Execution listeners Listener of activity. Listeners are created at the start and end of activity.
Called element Reference of a process.
Called element type Sub process type is an attribute that defines whether the sub-process details are embedded within the higher level process or refers ( Reference ) to another, re-usable process.
Input parameters An optional input parameter map. Allows the mapping of parameters and variables which are then available in the newly created process.
Output parameters An optional output parameter map. Allows the mapping of parameters and variables onto the original Case Work Item as the Human task’s Work Item completes.
Inherit variables in sub process Inherit parent process variables in the newly created process.
Start the referenced process from the same deployment Choose true if process that is started is in the same process. Choose false if the newest process definition will always be used. Default value is true.
Fallback to default tenant Look for the definition by key in the default tenant when current tenant search fails.
Process instance name The name of process that will be created. Note: When this field is left blank, the default value is “ProcessName_call_activity_Date” .
Inherit business key Inherit the business key from the parent process.
Business key expression Business key of the newly created process instance. Can be an expression.
Use local scope for out parameters Use local variable scope for out parameters.
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 a transaction sub process Identifies whether this sub process is type of transaction.

Execution listeners examples

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

The “Start” property indicates the moment when a process is initiated. When a workflow process starts, this property can trigger an execution listener. It can be used to perform specific actions at the beginning of the workflow process.

Start

The “End” property signifies the moment when a process is completed. When a workflow process finishes, this property can trigger an execution listener. It can be used to perform specific actions at the end of the workflow process.

End

The “Take” property denotes the moment when a flow transitions from one task or activity to another. Thus, when a step in the workflow moves to another step, this property can trigger an execution listener. It can be used to manage data transitions or conditional operations between tasks.

Take

Called element type examples

Default, creates only one instance:

key

Creates in parallel:

End

Input parameters examples

You can use the Input parameters as shown in the examples.

Source: variablex

Source Expression: variablex is using for …. (any description)

Target: variablex

Target Expression: variablex is receiving from main process. (any description)

Output parameters examples

You can use the Output parameters as shown in the examples.

Source: variablex

Source Expression: variablex is using for …. (any description)

Target: variablex

Target Expression: Sending variablex to main process. (any description)

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

${variable==True}

${dataCount==0}, ${dataExists==”true”}