7.1
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
2 Create the root element customOperations.
<customOperations xmlns="http://www.dynamicops.com/schemas/2009/OperationConfig/">
</customOperations>
The element must specify the XML namespace
http://www.dynamicops.com/schemas/2009/OperationConfig/.
3 For each operation you want to define, add an operation element within customOperations.
<operation name="WFMachineMenu1" displayName="Execute Machine Menu task">
</operation>
The operation element takes the following attributes:
Attribute Description
name The name of the workflow that this operation executes.
displayName A descriptive label for the option in the machine menu.
4 Specify the roles to grant access to the menu operation.
a Add the authorizedTasks element.
<operation name="WFMachineMenu1" displayName="Execute Machine Menu task">
<authorizedTasks>
</authorizedTasks>
</operation>
b For each role that you want to grant access to the operation, add a task element, for example:
<authorizedTasks>
<task>VRM User Custom Event</task>
<task>VRM Support Custom Event</task>
<task>Group Administrator Custom Event</task>
<task>Enterprise Administrator Custom Event</task>
<task>VRM Administrator Custom Event</task>
</authorizedTasks>
The valid contents of the task element are as follows:
Element content Description
VRM User Custom Event Grants access to the operation for all users.
VRM Support Custom Event Grants access to the operation for support users.
Group Administrator Custom Event Grants access to the operation for business group managers.
Enterprise Administrator Custom
Event
Grants access to the operation for fabric administrators.
VRM Administrator Custom Event Grants access to the operation for IaaS administrators only.
Life Cycle Extensibility
VMware, Inc. 73