Orchestrations
Orchestration microflows are microflows that only route the logic to the execution of units but is never changing or creating values itself. It can be seen as the 'composition of units' and sub-orchestrations in order to reach a desired result. As a rule of thumb: a orchestration microflow itself is not resulting in a measurable output but leaves changing an object, executing a function or checking the correctness of data to the unit microflows.

1. Orchestration microflow pattern
- checking preconditions
- calling other orchestration microflows and/or orchestrate unit microflow execution
- calling the commit logic (optional)
2. Base Microflow types
- Orchestration (
ORC): microflows that contains the logic to choose the correct unit microflows to be executed and optionally commit changes by calling the commit microflow (CMT). - Committer (
CMT: microflow that evaluates if a commit is allowed by calling validation microflows (VALandVAL_ORC) and committing the objects - Validation orchestration: (
VAL_ORC): microflow that composes all validations that should be executed given a specific situation
3. Naming conventions
See section Naming conventions.
4. Call hierarchy of microflow typologies
Orchestration microflows can be called from any Touchpoint microflow typology and can call themselves.
ORC orchestration microflows are allowed to call:
- a microflow type that belongs to the same microflow type.
- the
CMTmicroflow type. - the
VAL_ORCmicroflow type. - the microflow typologies that belong to the Unit microflow typology.
The CMT microflows are allowed to call:
- a microflow type that belongs to the same microflow type.
VAL_ORCmicroflow type.- the common unit microflow types (
GET,VAL,FTNandRULE).
The VAL_ORC microflows are allowed to call:
- a microflow type that belongs to the same microflow type.
- a
VALmicroflow type.
See the Microflow call hierarchy overview for a schematic overview of which microflow typologies are allowed to call each other.