7.1

Table 4‑43. XaaS Object Types and Associated Forms
Object Type Default Form Additional Forms
Custom resource Resource details form based on the
aributes of the vRealize Orchestrator
plug-in inventory type (read-only).
n
None
XaaS blueprint Request submission form based on the
presentation of the selected workow.
n
Catalog item details (read-only)
n
Submied request details (read-only)
Resource action Action submission form based on the
presentation of the selected workow.
n
Submied action details (read-only)
You can modify the default forms and design new forms. You can drag elds to add and reorder them on
the form. You can place constraints on the values of certain elds, specify default values, or provide
instructional text for the end user who is completing the form.
Because of their dierent purposes, the operations you can perform to design read-only forms are limited
compared to the operations for designing submission forms.
Fields in the Form Designer
You can extend the workow presentation and functionality by adding new predened elds to the default
generated forms of resource actions and XaaS blueprints.
If an input parameter is dened in the vRealize Orchestrator workow, in vRealize Automation it appears
on the default generated form. If you do not want to use the default generated elds in the form, you can
delete them and drag and drop new elds from the palee. You can replace default generated elds without
breaking the workow mappings if you use the same ID as the eld you are replacing.
You can also add new elds, other than the ones that were generated based on the vRealize Orchestrator
workow inputs, so that you can extend the workow presentation and functionality in the following cases:
n
Add constraints to the existing elds
For example, you can create a new drop-down menu and name it dd. You can also create predened
options of Gold, Silver, Bronze, and Custom. If there is a predened eld, such as CPU, you can add the
following constraints to this eld:
n
If dd equals Gold, then CPU is 2000 MHz
n
If dd equals Silver, then CPU is 1000 MHz
n
If dd equals Bronze then CPU is 500 MHz
n
If dd equals Custom, the CPU eld is editable, and the consumer can specify a custom value
n
Add external value denitions to elds
You can add an external value denition to a eld so that you can run vRealize Orchestrator script
actions and supply additional information to consumers on the forms you design. For instance, you
might want to create a workow to change the rewall seings of a virtual machine. On the resource
action request page, you want to provide the user with the ability to change the open port seings, but
you also want to restrict the options to ports that are open. You can add an external value denition to a
dual list eld and select a custom vRealize Orchestrator script action that queries for open ports. When
the request form loads, the script actions runs, and the open ports are presented as options to the user.
n
Add new elds that are handled in the vRealize Orchestrator workow as global parameters
For instance, the workow provides an integration with a third-party system and the workow
developer dened input parameters to be handled in the general case, but has also provided a way for
passing custom elds. For example, in a scripting box, all global parameters that start with my3rdparty
are handled. Then, if the XaaS architect wants to pass specic values for consumers to provide, the XaaS
architect can add a new eld named my3rdparty_CPU.
Chapter 4 Providing On-Demand Services to Users
VMware, Inc. 319