Collapsed Sub-process Activity
The Collapsed Sub-process activity enables hierarchical modeling for a high-level, end-to-end overview of the business process by allowing sub-processes to be collapsed, thereby hiding their internal details.
| Field | Description | Requirement |
|---|---|---|
| Exclusive | When the activity receives a special job from a specific process, it ensures jobs run in order. | Optional |
| Data objects | Defines the Data Objects for the process or sub-process. Each data object initializes as a process variable under its defined name. | Optional |
| Execution listeners | Configures listeners for the activity. Listeners are created at the start and end of the activity's lifecycle. | Optional |
| Multi-instance type | Determines if multiple instances of this activity are created. | Optional |
| Cardinality (Multi-instance) | An expression or numeric integer value that determines the number of instances to create. | Optional |
| Collection (Multi-instance) | The number of instances is determined by the elements of a collection. A new instance is created for each element in the collection. | Optional |
| Element Variable (Multi-instance) | The variable under which each element from the collection is available to its newly created instance. | Optional |
| Completion Condition (Multi-instance) | An expression that, when evaluated to true, stops the creation of new instances. | Optional |
| Is a Transaction Sub-process | Identifies whether this sub-process is a transaction type. | Optional |
Action Types & Examples
Execution Listeners
- Format: String
- Example Result: "Start", "End", "Take"
Multi-instance Type
- Format: String
- Example Result: "None", "Parallel", "Sequential"
Cardinality (Multi-instance)
- Format: Expression or Integer
- Example Result: "${number}", "2"
Collection (Multi-instance)
- Format: Integer (representing a count derived from a collection)
- Example Result: "2"
Element Variable (Multi-instance)
- Format: String
- Example Result: "elementvar"
Completion Condition (Multi-instance)
- Format: Boolean Expression
- Example Result: "true", "${variable==True}", "${dataCount==0}", "${dataExists==\"true\"}"
Implementation Examples
Field Setup - Execution listeners: Start, End, Take - Multi-instance type: None, Parallel, Sequential
Execution Parameters - Cardinality (Multi-instance): ${number}, 2 - Collection (Multi-instance): 2 - Element Variable (Multi-instance): elementvar - Completion Condition (Multi-instance): true, ${variable==True}, ${dataCount==0}, ${dataExists=="true"}
Technical Notes
The 'Start' property indicates the moment a process is initiated, triggering an execution listener to perform specific actions at the beginning of the workflow. The 'End' property signifies process completion, allowing an execution listener to trigger actions at the workflow's conclusion. The 'Take' property denotes a flow transition between tasks or activities, enabling an execution listener to manage data transitions or conditional operations.
Multi-instance types control the creation of activity instances. 'None' creates a single instance. 'Parallel' creates instances concurrently, which is suitable for User tasks. 'Sequential' creates instances one after another, often used for Service tasks.
Cardinality defines the number of instances using an expression or an integer value. Collection determines instances based on the elements within a specified collection, with each element generating a new instance. When using a collection, an Element Variable makes each collection element accessible to its corresponding newly created instance. A Completion Condition is an expression that, when evaluated to
true, halts the creation of any further instances.