7.4

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
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
configure in the approval policy level. These properties are configured 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.
Life Cycle Extensibility
VMware, Inc. 42