7.1

Table Of Contents
XaaS architects add custom resources related to the supported endpoints and provided workows, and then
create XaaS blueprints and actions based on those resources. Tenant administrators and business group
managers can add the XaaS blueprints and actions to the service catalog. The XaaS blueprint can also be
used in the blueprint designer.
When the service catalog user requests an item, vRealize Automation runs a vRealize Orchestrator
workow to provision the custom resource.
Figure 42. Create and Request Custom Resource Actions to Modify a Custom Resource
Map vRealize
Orchestrator
object types
and workflows
to vRealize
Automation
Active
Directory
vCenter
Server
SOAP
HTTP-
REST
Request a resource action
Modify the custom resource
Resource Action
vRealize Automation
Catalog
Orchestrator Workflow
Engine and Library
XaaS
Run a
vRealize
Orchestrator
Workflow
Custom Resource
Expose new
object and
actions in
vRealize
Automation
Custom post-provisioning
action
XaaS architects can also add vRealize Orchestrator workows as resource actions to extend
vRealize Automation capabilities. After the service catalog users provision a custom resource, they can run
post-provisioning action. This way, the consumers run a vRealize Orchestrator workow and modify the
provisioned custom resource.
When a service catalog user requests an XaaS blueprint or resource action as a catalog item, the XaaS service
runs the corresponding vRealize Orchestrator workow passing the following data as global parameters to
the workow:
Table 441. XaaS Global Parameters
Parameter Description
__asd_tenantRef
The tenant of the user requesting the workow.
__asd_subtenantRef
The business group of the user requesting the workow.
__asd_catalogRequestId
The request id from the catalog for this workow run.
__asd_requestedFor
The target user of the request. If the request is on behalf of
a user, then this is the user on behalf of whom the
workow is requested, otherwise it is the user requesting
the workow.
__asd_requestedBy
The user requesting the workow.
If an XaaS blueprint or resource action uses a vRealize Orchestrator workow that contains a User
Interaction schema element, when a consumer requests the service, the workow suspends its run and waits
for the user to provide the required data. To answer to a waiting user interaction, the user must navigate to
Inbox > Manual User Action.
Chapter 4 Providing On-Demand Services to Users
VMware, Inc. 307