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
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
serviceId : STRING, // Identifier of the service which initiated the approval
externalClassId : STRING // Identifier of the class to which the source object
belongs
}
}
Property names and property values can be the custom properties or system properties that you congure in
the approval policy level. These properties are congured in the approval policy to allow the approver to
change the values during an approval process. For example, if CPU is included, the approver can decrease
the number of CPUs in the approval request form.
The reply event data payload is the information that it returned to vRealize Automation by the workow.
The contents of the reply payload determines whether the request is approved or rejected.
{
approved : BOOLEAN,
// Property values
fieldValues : Properties
}
The approved parameter in the reply event payload is either true, for approved, or false, for rejected
requests. The property values are the custom or system properties that were modied by the
vRealize Orchestrator workow and returned to vRealize Automation and included in the approval process.
As a best practice, you should congure the vRealize Orchestrator workow with an output parameter for
businessJustification. You can use this parameter to pass comments provided by the approver in the
outside system to the vRealize Automation approval process. These comments can be for approvals or
rejections.
Creating a vRealize Orchestrator Workflow Based on the Approval Schema
The custom approval workow that you create must have an input parameter, with any useful name, that is
congured with the type Properties. The approval event data payload is put into this parameter when the
workow subscription is triggered to run.
The output parameters of the workow that are sent back to vRealize Automation are approved : Boolean
and fieldValues : Properties. The returned approved : Boolean parameter determines if the approval
level is approved or rejected. The fieldValues : Properties parameter contains the values that were
modied in the external system.
Life Cycle Extensibility
38 VMware, Inc.