You use a single workflow in vRealize Orchestrator to inject your custom logic into the IaaS workflow stubs and assign your customized life cycles to machine blueprints.


The workflow stubs are replaced by the event broker workflow subscriptions. They are still available, supported, and they can be used, but expect them to be removed in a future version of vRealize Automation. To ensure future product compatibility, you should use the workflow subscriptions to run custom workflows based on state changes. See Configuring Workflow Subscriptions to Extend vRealize Automation.

You must design your custom vRealize Orchestrator workflows to accept string inputs. If your custom workflow expects a complex data type, create a wrapper workflow that looks up this complex value and translates it to a string. For an example wrapping workflow, see the sample Workflow template, provided in Library > vRealize Automation > Infrastructure > Extensibility.