The field properties in Service Broker determine how the fields looks and what default values are presented to the user. You can also use the properties to define rules that ensure that the users provide a valid entry when they request the item in the catalog.
You configure each field individually. Select the field and edit the field properties.
For many of the properties, you can select from various value source options. Not all source options are available for all field types or properties.
- Constant. The value does not change. Depending on the property, the value might be a string, an integer, a regular expression, or selected from a limited list, for example, Yes or No. For example, you can provide 1 as a default value integer, select No for the Read-only property, or provide the regular expression to validate a field entry.
- Conditional value. The value is based on one or more conditions. The conditions are processed in the order listed. If more than one condition is true, the last condition that is true determines the behavior of the field for that property. For example, you can create a condition that determines if a field is visible based on the value in another field.
- External source. The value is based on the results of a vRealize Orchestrator action. For example, calculate cost based on a scripted vRealize Orchestrator action. For an example, see Using vRealize Orchestrator actions in the custom form designer in Service Broker
- Bind field. The value is the same as the field to which it is bound. The available fields are limited to the same field type. For example, you bind default value for an authentication needed check box field to another check box field. When one target field check box is selected in the request form, the check box on the current field is selected.
- Computed value. The value is determined based on how the operator processes the selected fields and values. Text fields use the concatenate operator. Integer fields use the selected add, subtract, multiply or divide operations. For example, you can configure an integer field to convert megabytes to gigabytes using the multiply operation.
You use the appearance properties to determine whether the field appears on the form and what label and custom help you want to provide to your catalog users.
|Label and type||
Provide a label and select a display type. The available display types depend on the element. Some some elements support multiple text types and others only support integers. Possible values:
Drop-down and data grid fields include a Placeholder setting. The entered value appears as an internal label or instructions in the drop-down menu, or as a general label or instructions in the data grid.
|Visibility||Show or hide a field on the request form.
If the visibility for a field is set to No, the field constraints, like regular expressions and required fields, are disregarded.
|Read-only|| Prevent users from changing the field values.
|Rows per page||For data grid elements only.
Enter the number of rows.
|Custom help|| Provide information about the field to your users. This information appears in signpost help for the field.
You can use simple text or HTML, including href links. For example,
You use the values properties to provide any default values.
|Columns||For the data grid element only.
Provide the label, ID, and value type for each column in your table.
The default value for the data grid must include the header data that matches the defined columns. For example, if you have user_name ID for one column and user_role ID for another, then the first row is user_name,user_role.
For configuration examples, see Using the data grid element in the Service Broker custom form designer.
|Default value||Populates the field with a default value based on the value source.
Possible value sources depend on the field.
|Value option||Populates a drop-down, multi-select, radio group, or value picker fields.
|Step||For integer or decimal fields, define the incremental or decremental values.
For example, if the default value is 1 and you set the step value to 3, then the allowed values are 4, 7, 10, and so on.
You use the constraint properties to ensure that the requesting user provides valid values in the request form.
|Required||The requesting user must provide a value for this field.
|Regular expression||Provide a regular expression that validates the value and a message that appears when the validation fails.
|Minimum value||Specify a minimum numeric value. For example, a password must have at least 8 characters.
Provide an error message. For example, The password must be at least 8 characters.
|Maximum value||Maximum numeric value. For example, a field is limited to 50 characters.
Provide an error message. For example, This description cannot exceed 50 characters.
|Match field||This field value must match the selected field value.
For example, a password confirmation field must match the password field.