7.3

Table Of Contents
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 congure in
the approval policy level. These properties are congured 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 workow.
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 modied by the
vRealize Orchestrator workow and returned to vRealize Automation and included in the approval process.
As a best practice, you should congure the vRealize Orchestrator workow 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 workow that you create must have an input parameter, with any useful name, that is
congured with the type Properties. The approval event data payload is put into this parameter when the
workow subscription is triggered to run.
The output parameters of the workow 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
modied in the external system.
Life Cycle Extensibility
38 VMware, Inc.