Collapsed sub process

Collapsed sub process activity hierarchial modeling for a high-level, end-to-end overview of the business process by enabling Sub-processes to be collapsed, resulting in hiding all details.


Exclusive	When it receives a special job from a specific process example, it makes jobs run in order.
Data objects	Defines the Data Objects of the process or sub process. Each data object is initialized as a process variable under the defined name.
Execution listeners	Listener of activity. Listeners are created at the start and end of activity.
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

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”}