7.4
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
In addition to the workflow definition, a menu operation workflow depends on an operation configuration
file, which defines 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.
Note An XaaS architect can define 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.
Configuring a Menu Operation Workflow Overview
You can customize a menu operation workflow by using vRealize Automation Designer and the CloudUtil
command-line utility. A blueprint author can then enable it for specific blueprints.
The following is a high-level overview of the steps required to enable menu operation workflows:
1 A workflow developer customizes one of the menu operation workflow templates by using vRealize
Automation Designer. See Customize an IaaS Workflow.
Any IaaS workflow can call a vRealize Orchestrator workflow. For more information, see Using
vRealize Orchestrator Workflow Activities.
2 A workflow developer configures the menu operation in the Model Manager. See Configure a Menu
Operation.
3 A workflow developer registers the new menu operation with the service catalog. See Register New
Menu Operations with the Service Catalog.
4 A tenant administrator or business group manager configures a blueprint to enable the menu
operation for machines provisioned from that blueprint. See Configure a Blueprint to Enable a Menu
Operation Workflow.
If the menu operation is intended to be used in the service catalog, it must also be entitled to users. For
more information, see Tenant Administration.
Customize an IaaS Workflow
vRealize Automation Designer enables you to edit the customizable workflows and update workflows in
the Model Manager.
Prerequisites
Launch the vRealize Automation Designer.
Procedure
1 Click Load.
2 Select the workflow that you want to customize.
Option Description
WFMachineMenuN Customizable menu operation workflow
WFStubBuildingMachine Customizable state change workflow that executes before a machine enters the
BuildingMachine state
Life Cycle Extensibility
VMware, Inc. 59