7.0

Assign a State Change Workflow to a Blueprint and Its Virtual
Machines
You configure custom vRealize Orchestrator workflows to run at specific stages in the master machine
workflow by associating your custom workflow with a state change workflow stub and assigning the
workflows to a blueprint.
Note The workflow stubs are being 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 Chapter 3 Configuring Workflow Subscriptions to
Extend vRealize Automation.
Prerequisites
Use the workflow template provided in the Extensibility subdirectory of the vRealize Automation plugin
library to create a custom workflow to run during the machine lifecycle.
Procedure
1 From the drop-down menu in the Orchestrator client, select Run or Design.
2 Click the Workflows view.
3 Select Library > vRealize Automation > Infrastructure > Extensibility.
4 Right-click the Assign a state change workflow to a blueprint and its virtual machines workflow
and select Start workflow.
5 Choose the lifecycle stage at which to run the workflow by selecting a stub from the vCAC workflow
stub to enable drop-down menu.
6 Select an IaaS host.
7 Click Next.
8 Select the blueprint to which you want to assign the workflow.
9 Choose whether or not to apply these workflows to existing machines provisioned by using this
blueprint.
10 Select the workflow you want to run during the machine lifecycle.
11 Configure which workflow input values are added as custom properties to the machine.
a Add vCO workflow inputs as blueprint properties.
b Add last vCO workflow run input values as blueprint properties.
12 Click Submit.
Life Cycle Extensibility
VMware, Inc. 18