7.4

Using External Validation in the Custom Forms Designer
You can customize a request form to ensure that users provide valid values at request time by adding
constraints to fields or using an external validation source.
Some field properties, such as minimum, maximum, regular expressions, match fields, or not empty, can
be configured with constraints to ensure valid values. See Custom Form Designer Field Properties.
External validation checks for valid values from an external source using vRealize Orchestrator actions .
Some examples where you might use external validation includes:
n
The valid values are defined in an external source. For example, vRealize Orchestrator.
n
The validation must affect several fields. For example, a vRealize Orchestrator action collects the disk
size and storage pool capacity, and validates the provided size values based on available space.
How do you order multiple external validations in one blueprint? The validations are processed in the
order that the appear on the External Validation canvas. If you have two validations that validate the same
field, the second validation results will overwrite the first. To reorder the validations, you can click and
drag the cards on the canvas.
Example: vRealize Orchestrator User Example
In this use case, you want the catalog user to provide only a new user name. To do this example, you
have a vRealize Orchestrator action that checks whether the user name provided in the form exists in
your Active Directory database. If the name does exist, an error message appears on the request form.
This use case is applied to the Create a Custom Request Form with Active Directory Options example.
1 In vRealize Orchestrator, configure an action, checkIfUsernameExists, with a script similar to the
following example.
Configuring vRealize Automation
VMware, Inc. 542