You are here:
View Orchestration Dependencies in the Automation App
Orchestrations rely on flows to run steps and evaluate complex conditions. To understand the relationships between an orchestration and its referenced flows, view the Usage tab of the Orchestration Version page in the Automation app.
- Determine Flow Usage in an Orchestration Version
Orchestration versions use flows to run interactive and background steps. Orchestration version stages and steps can use flows to evaluate complex criteria. Those criteria can determine when a background, interactive step, or MuleSoft step starts and when to mark a stage or interactive step as completed. View the flows that an orchestration version uses to understand the relationships between an orchestration version and the flows it references. - Add the Automation Usage Component to the Orchestration Record Version Page
The Automation app shows the flows that an orchestration version uses. If you customized the Default Orchestration Version Record page, add the Automation Usage component to your page and save it as your org default.
Did this article solve your issue?
Let us know so we can improve!
