Adhoc Sub Process Activity
The Adhoc Sub Process activity enables the creation of a task group designed to complete a specific part of a larger process. It provides flexibility in defining and executing sub-processes that are not strictly pre-defined in the main workflow.
| Field | Description | Requirement |
|---|---|---|
| Completion condition | An expression that, when evaluated to true, halts the creation of new instances for the adhoc sub-process. | Optional |
| Ordering | Specifies the execution order for instances within the adhoc sub-process. This attribute must be included if the Embedded Sub-Process is Ad Hoc. | Optional |
| Cancel remaining instances | Determines whether any remaining active instances of the adhoc sub-process should be canceled upon completion or termination. | Optional |
Action Types & Examples
Completion Condition
- Format: Boolean expression
- Example Result:
true
Ordering
- Format: String
- Example Result:
Parallel
Implementation Examples
Field Setup - Completion condition: ${variable==True} - Ordering: Parallel - Cancel remaining instances: true
Execution Parameters - Completion condition: ${dataCount==0} - Ordering: Sequential - Cancel remaining instances: false
Technical Notes
The
Completion conditionparameter accepts expressions that evaluate to a boolean value. When this condition becomestrue, the creation of new instances for the adhoc sub-process ceases. TheOrderingparameter is specifically relevant when the parent Embedded Sub-Process is configured as Ad Hoc, in which case its inclusion is mandatory to define the execution flow.