Every blueprint that you create and publish displays a form when your users request the blueprint in the catalog. You can use the default form or you can customize blueprint request forms when you create or edit a blueprint. You customize a form when the information provided or required on the default form is not what you want to present to your users.

Customizing Request Forms

You access the custom request form designer from the blueprint data grid or from the blueprint canvas.

Custom Form Menu on the Design Tab

Custom Request Form Designer

You use the form designer to create your custom form.

Custom Form Design Canvas with Callouts

To create a custom form:

  1. Drag elements (1 and 2) onto the design canvas (3).
  2. Configure each element using the properties pane (4).
  3. Activate the form (5).

Unless a property is configured prohibit overwriting, the blueprint elements list includes custom properties. If the overridable option on the property is set to no, the field is not eligible for customization.

Validation and Constraints

The custom form designer supports data validation by adding constraints to a field or by using an external validation source. For constraints options that are applied as you create a form, see Custom Form Designer Field Properties.

When you add validation and dependencies in forms, the requesting user must supply or the system must validate the fields or the dependent fields might not appear on the form.

For example, if you have fields on the first tab that subsequent fields are dependent on, the depend fields might not appear on the succeeding tabs until the dependent value is provided on the preceding tabs.

Custom Request Form Actions

You use the action menu items to populate forms and share forms with other systems.

Custom Form Design Canvas Action Menu
Table 1. Custom Request Form Action Menu Items
Action Menu Item Description
Generate Form Adds all the fields associated with each blueprint component to the form designer. Each component is added to a tab. If you use this menu item after you created or modified a form, the generated form overwrites your current form.

If you use this menu item, you can hide or remove fields that you do not want to present to your users in the catalog. If you do not generate the form, you can still add and configure the text boxes that you want your users to see.

Import Form Imports a custom form JSON or YAML file.
Export Form Exports your current custom form as a JSON file.

Export the file when you want to use part of it that matches a component that you use in another blueprint.

Export form as YAML Exports your current custom form as YAML.

Export the file as YAML when you want to move a custom from one vRealize Automation instance to another. For example, from your test environment to your production environment. If you prefer to edit the form as YAML, you can export the form, edit it, and then import it back into the blueprint.

Import CSS Imports a CSS file that enhances the catalog request form.

The file might be similar to the following example. This example changes the font size and makes the text bold. The field referenced is the Deploy Machine with Active Directory User Account text field that appears in the image located in the Custom Request Form Designer section above.

#<field-ID> .grid-item {
     font-size: 16px;
     font-weight: bold;
     width: 600px;

In this example, <field-ID> is the ID for the field in the canvas. To locate the value, select the field in the canvas. The value is located in the right pane, below the name. In the image above, the value is text_d947bc97.

To import the file. Save it as <filename>.css.

Export CSS Exports your imported CSS.
Remove CSS Discards your custom CSS.

The discarded CSS is not recoverable.

Download format schema Downloads a JSON file that contains the structure and description of the controls and states used in a custom form.

You can use this schema to create a form or to modify an existing form. You can import the modified JSON file as the custom form.