When designing a complex business process it may become too large to manage as one monolithic process definition. A sub-flow activity allows another process definition to enacted as part of another process. To enact a process as a subflow, the subflow activity must identify the process that will be enacted by name. As with the other process enactment mechanisms, the latest released version of the process is the one that will be enacted.
Subflows can be enacted synchronously. This means that the branch of the parent workflow containing the subflow activity that started the subflow process waits for that subflow process to finish before continuing. Alternatively, a subflow may be enacted asynchronously. This means that once the subflow activity starts the subflow process, the branch containing that subflow activity continues immediately with the outcome of the subflow process having no effect on the parent process.
The metadata associated with subflow activities is described in the Subflow chapter of the Cúram Workflow Reference Guide.