7.1

3 Enter the options.
Option Description
Name
Consult the conguration details. Some of the custom properties require
specic names or formats. Where you can, use a standard naming
convention for the new property name such as
my_grouping_prefix.my_property_name.
Label
The label is populated based on the name. You can change the label to
provide a more readable name.
Visibility
The action custom properties are only available in the current tenant. To
make them available in another tenant, you must congure them when
you are logged in to that tenant.
Description
Describe the intent of the property denition and any other helpful
information about the property.
Display order
The number that you enter controls where the property name appears on
the request form. The following ordering rules apply:
n
The display order applies only to properties that are congured with
Prompt User or Show in Request Form seings.
n
All properties with a display order appear before properties with no
order index.
n
Properties with a display order are sorted from lowest to highest
value. You can use negative numbers.
n
All properties are ordered alphabetically, with all display order
properties appearing before non-display order properties.
n
If two properties have the same display order value, they are sorted
alphabetically.
4 Consult the conguration details to determine what you must provide for the values.
The following values are provided in the conguration details:
n
Data type
n
Display as
n
Values
n
Action folder
n
Script action
n
Input parameters
5 Click OK.
The custom property denition is added to the list and it is available to add to a blueprint.
What to do next
Add the custom property to a blueprint. Whether you add it as a machine or as a network property depends
on the property. See “Add a Custom Property to a Blueprint,” on page 95.
Bind Custom Properties to Create a Parent-Child Relationship
To create a parent-child relationship between custom properties, you bind the parent to the child. When you
add the parent and child custom properties to a blueprint, the requesting user selects a value for the parent
property. The selected parent value determines the possible values for the child property.
n
The parent custom property denition can be a static list or an external value that is determined by an
vRealize Orchestrator action. It provides possible input parameters to a child property denition.
n
The child custom property denition must call a vRealize Orchestrator action. In the child custom
property, you bind the parent custom property so that it provides an input parameter value.
Chapter 4 Using the Property Dictionary
VMware, Inc. 91