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
The approval workflow subscription receives messages from the approval service and compares the
messages to the configured criteria for approval subscriptions. When it finds a message that matches the
criteria, the selected vRealize Orchestrator workflow starts to run. The published event data is passed to
the workflow as input and processed in the method specified in the workflow. The results of the workflow
are returned to vRealize Automation and the request is processed. If approved, the next approval level is
evaluated. If rejected, the request is rejected. If the approval service does not receive a reply within 24
hours, the default timeout for the approval service, the request is processed as rejected.
Configuring vRealize Orchestrator Workflows for Approval Event
Topics
You must configure your custom vRealize Orchestrator workflow to support the approval message and to
reply with correctly formatted information that vRealize Automation can process.
Approval Event Topic Schema
The pre-approval and post-approval event message schema includes the field names and values, the
information included in the request, and information about the source of the request.
The following is the structure of the event data payload.
{
fieldNames : Properties, // Property names
fieldValues : Properties, // Property values
// Information about the request
requestInfo : {
requestRef : STRING, // Identifier for the source request
itemName : STRING, // Name of the requested item
itemDescription : STRING, // Description of the requested item
reason : STRING, // Justification provided by the user specifying why the
request is required
description : STRING, // Description entered by the user specifying the purpose of
the request
approvalLevel:ExternalReference,// Approval level ID. This is a searchable field
approvalLevelName : STRING, // Approval level name
createDate : DATE_TIME, // Time the approval request is created
requestedFor : STRING, // Principal id of the user for whom the source request is
initiated
subtenantId : STRING, // Business group id
requestedBy : STRING // Principal id of the user who actually submits the request
},
// Information about the source of the request
sourceInfo : {
externalInstanceId : STRING, // Identifier of the source object, as defined by the intiator
service
Life Cycle Extensibility
VMware, Inc. 47