Adding a Subworkflow to Conductor

Sub workflows are a "workflow in a task." That's right, you can just call another workflow right inside your workflow. Updates to that workflow will be automatically propagated into your workflow,.

Other reasons to use a sub workflow:
1. readability
2. Do/WHILE loops cannot be nested, but a Sub workflow (with a loop) can be nested inside a DO/WHILE.
3. Dynamic Forks only permit one task - but a sub workflow is just one task.

Other tasks you can add to your Conductor Workflow: