7.3

Table 3‑61. New Fields in the Resource Action or XaaS Blueprint Form (Continued)
Field Description
Tree Tree that consumers use to browse and select available objects
Map Map table that consumers use to define key-value pairs for properties
You can also use the Section header form field to split form pages in sections with separate headings
and the Text form field to add read-only informational texts.
Constraints and Values in the Form Designer
When you edit an element of the blueprint or resource action form, you can apply various constraints and
values to the element.
Constraints
The constraints that you can apply to an element vary depending on the type of element you are editing
or adding to the form. Some constraint values might be configured in the vRealize Orchestrator workflow.
Those values do not appear on the Constraints tab because they are often dependent on conditions that
are evaluated when the workflow runs. Any constraint values that you configure for the blueprint form
overrides any constraints included in the vRealize Orchestrator workflow.
For each constraint you apply to an element, you can select one of the following options to define the
constraint:
Not set Gets the property from the vRealize Orchestrator workflow presentation.
Constant Sets the element you are editing to required or optional.
Field Binds the element to another element from the form. For example, you can
set the element to be required only when another element, such as a check
box, is selected.
Conditional Applies a condition. Use the conditions to create various clauses and
expressions and apply them to the state or constraints of the element.
External Select a vRealize Orchestrator script action that defines the value.
Table 3‑62. Constraints in the Forms Designer
Constraint Description
Required Indicates whether the element is required.
Read only Indicates whether the field is read-only.
Value Sets a value for the element.
Configuring vRealize Automation
VMware, Inc. 471