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.

After calculated for a field, the minimum and maximum bindings are only recalculated when a blueprint is requested.

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 1. 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.

Visible

Indicates whether the consumer can see the element.

If you apply a visibility constraint on a display group in the vRealize Orchestrator workflow, the constraint is ignored in the XaaS Submitted Request Details form and the fields that you want hidden appear in the form.

To hide fields that you do not want to appear in the Submitted Request Details form, and they are not required for the requesting user, remove the fields from the Submitted Request Details form on the Blueprints Form tab in the XaaS blueprint designer. To locate this tab, see Add a New XaaS Blueprint Form.

Minimum length

Sets a minimum number of characters of the string input element.

Maximum length

Sets a maximum allowed number of characters of the string input element.

Minimum value

Sets a minimum value of the number input element.

Maximum value

Sets a maximum value of the number input element.

Increment

Sets an increment for an element such as a Decimal or Integer field. For example, when you want an Integer field to be rendered as a Slider, you can use the value of the step.

Minimum count

Sets a minimum count of items of the element that can be selected.

For example, when you add or edit a Check box list you can set the minimum number of check boxes that the consumer must select to proceed.

Maximum count

Sets a maximum count of items of the element that can be selected.

For example, when you add or edit a Check box list you can set the maximum number of check boxes that the consumer must select to proceed.

Values

You can apply values to some of the elements and define what the consumers see for some of the fields. The options available depend on the type of element you are editing or adding to the form.

Table 2. Values in the Form Designer

Value

Description

Not set

Get the value of the element you are editing from the vRealize Orchestrator workflow presentation.

Predefined values

Select values from a list of related objects from the vRealize Orchestrator inventory.

Value

Define a static custom value with labels.

External Values

Select a vRealize Orchestrator script action that defines your value with information not directly exposed by the workflow.