You can extend the workflow presentation and functionality by adding new predefined fields to the default generated forms of resource actions and XaaS blueprints.

If an input parameter is defined in the vRealize Orchestrator workflow, in vRealize Automation it appears on the default generated form. If you do not want to use the default generated fields in the form, you can delete them and drag and drop new fields from the palette. You can replace default generated fields without breaking the workflow mappings if you use the same ID as the field you are replacing.

You can also add new fields, other than the ones that were generated based on the vRealize Orchestrator workflow inputs, so that you can extend the workflow presentation and functionality in the following cases:

  • Add constraints to the existing fields
    For example, you can create a new drop-down menu and name it dd. You can also create predefined options of Gold, Silver, Bronze, and Custom. If there is a predefined field, such as CPU, you can add the following constraints to this field:
    • If dd equals Gold, then CPU is 2000 MHz
    • If dd equals Silver, then CPU is 1000 MHz
    • If dd equals Bronze then CPU is 500 MHz
    • If dd equals Custom, the CPU field is editable, and the consumer can specify a custom value
  • Add external value definitions to fields

    You can add an external value definition to a field 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 workflow to change the firewall settings of a virtual machine. On the resource action request page, you want to provide the user with the ability to change the open port settings, but you also want to restrict the options to ports that are open. You can add an external value definition to a dual list field 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.

  • Add new fields that are handled in the vRealize Orchestrator workflow as global parameters

    For instance, the workflow provides an integration with a third-party system and the workflow developer defined input parameters to be handled in the general case, but has also provided a way for passing custom fields. For example, in a scripting box, all global parameters that start with my3rdparty are handled. Then, if the XaaS architect wants to pass specific values for consumers to provide, the XaaS architect can add a new field named my3rdparty_CPU.

Table 1. New Fields in the Resource Action or XaaS Blueprint Form
Field Description
Text field Single-line text box
Text area Multi-line text box
Link Field in which consumers enter a URL. You can use http, https, ftp, mailto, or /. Do not use file://.
Email Field in which consumers enter an email address
Password field Field in which consumers enter a password
Integer field Text box in which consumers entre an integer

You can make this field a slider with a minimum and maximum value, as well as an increment.

Decimal field Text box in which consumers enter a decimal

You can make this field a slider with a minimum and maximum value, as well as an increment.

Date & time Text boxes in which consumers specify a date (by selecting a date from a calendar menu) and can also select the time (by using up and down arrows)
Dual List A list builder in which consumers move a predefined set of values between two lists, the first list contains all unselected options and the second list contains the user's choices.
Check box Check box
Yes/No Drop-down menu for selecting Yes or No
Drop-down Drop-down menu
List List
Check box list Check box list
Radio button group Group of radio buttons
Search Search text box that auto completes the query and where consumers select an object
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.