7.3
Table Of Contents
- Life Cycle Extensibility
- Contents
- Life Cycle Extensibility
- Machine Extensibility Overview
- Extending Machine Lifecycles By Using vRealize Orchestrator
- Configuring Workflow Subscriptions to Extend vRealize Automation
- Event Topics Provided With vRealize Automation
- Workflow Subscriptions and Event Broker Terminology
- Blockable and Replyable Event Topics
- Best Practices for Creating vRealize Orchestrator Workflows for Workflow Subscriptions
- Workflow Subscription Settings
- Working with Provisioning and Life Cycle Workflow Subscriptions
- Configuring vRealize Orchestrator Workflows for Provisioning and Life Cycle Workflows
- Workflow Subscription Life Cycle State Definitions
- Configuring the Timeout Values for States and Events
- Configuring the Error Behavior for States and Events
- Scenario: Take a Post-Provisioning Snapshot of a Virtual Machine
- Working with Approval Workflow Subscriptions
- Troubleshooting Workflow Subscriptions
- Troubleshooting vRealize Orchestrator Workflows That Do Not Start
- Troubleshooting Provisioning Requests That Take Too Much Time
- Troubleshooting a vRealize Orchestrator Workflow That Does Not Run for an Approval Request
- Troubleshooting a Rejected Approval Request That Should Be Approved
- Troubleshooting a Rejected Approval Request
- Extending Machine Life Cycles By Using vRealize Automation Designer
- Extending Machine Life Cycles By Using vRealize Automation Designer Checklist
- Installing and Configuring vRealize Automation Designer
- Customizing IaaS Workflows By Using vRealize Automation Designer
- Workflows and Distributed Execution Management
- CloudUtil Command Reference
- vRealize Automation Workflow Activity Reference
- Index
vRealize Automation Designer provides a customizable workow for each of these states.
Table 1‑18. Customizable State Change Workflows
Master Workflow State Customizable Workflow Name
BuildingMachine WFStubBuildingMachine
Disposing WFStubMachineDisposing
Expired WFStubMachineExpired
MachineProvisioned WFStubMachineProvisioned
RegisterMachine WFStubMachineRegistered
UnprovisionMachine WFStubUnprovisionMachine
Configuring a State Change Workflow Overview
You can customize a state change workow by using vRealize Automation Designer. A blueprint author can
then enable it for specic blueprints.
The following is a high-level overview of the steps required to enable state change workows:
1 A workow developer customizes one of the state change workow templates by using vRealize
Automation Designer. See “Customize an IaaS Workow,” on page 52.
Any IaaS workow can call a vRealize Orchestrator workow. For more information, see “Using
vRealize Orchestrator Workow Activities,” on page 53.
2 A tenant administrator or business group manager congures a blueprint to call the customized
workow for machines provisioned from that blueprint. See “Congure a Blueprint to Call a State
Change Workow,” on page 57.
Menu Operation Workflows
A menu operation workow is executed when a user selects an option from the Actions menu in the service
catalog or the machine menu in the Infrastructure tab.
For example, you can create a custom workow that enables a user to create a support ticket related to a
machine by selecting Raise Support Issue from the machine menu.
vRealize Automation Designer provides templates for customizing menu operation workows.
In addition to the workow denition, a menu operation workow depends on an operation conguration
le, which denes the aspects of the custom menu option such as the display text, which roles have access to
it, and the machine states for which the operation is available.
N An XaaS architect can dene custom actions for any catalog item by using the XaaS. Creating custom
actions for IaaS machines other than those provisioned by using vSphere or vCloud Director requires
vRealize Automation 6.1 or later.
Chapter 1 Life Cycle Extensibility
VMware, Inc. 51