Now that we have seen an overview of workflows, we will dive deeper into the components used to make workflows useful for end-users from the perspective of building a custom workflow.
One thing to keep in mind is that any user building workflows should approach operations from a mindset of achieving idempotence, meaning that we can apply the same configuration via executing a workflow within ICO, and we should achieve the same result every time this configuration is applied.
Let's dig into these categories of the inner workings of Intersight Cloud Orchestrator:
- Data Models & Data Types
- Device mapping
- User input
- Variables
- Failure/terminal action
- Executors