7.1

4 As a machine requestor, specify required values as prompted.
You can also populate the property value in a drop-down menu by using vRealize Orchestrator script
actions. Using vRealize Orchestrator script actions also enables you to populate a drop-down menu value
based on the values specied for another property.
You can use the vra content list --type property-definition vRealize CloudClient command to list all
property denitions in the current vRealize Automation instance tenant. You can also use the vra content
list --type property-group vRealize CloudClient command to list all property groups. You can add some
or all of the property denitions and property groups to a package and export the package to a zip le. You
can then import the package into another vRealize Automation instance tenant. For more information about
vRealize CloudClient and its uses, see the VMware Developer Center at
hps://developercenter.vmware.com/tool/cloudclient.
Create and Test Custom Property Definitions
You create a custom properties denition that determines how the custom property appears in
vRealize Automation. You can add the custom property to a blueprint so that you can verify that the
property displays the check box, drop-down menu, or other control type as expected.
To create and test the custom property denitions, you need a blueprint that is already entitled to you or to a
test user account to which you have access. This test blueprint allows you to create the custom property, add
it to a blueprint, and then verify that the custom property has the expected appearance. After you validate
the custom property, you can add it to your production blueprints as needed.
Prerequisites
n
Verify that you have a blueprint to which you are adding the action. See Conguring vRealize Automation.
n
Verity that the blueprint is entitled to you so that you can test the custom properties in the blueprint.
See Conguring vRealize Automation.
n
Log in to the vRealize Automation console as a tenant administrator or fabric administrator.
Procedure
1 Create Custom Property Denitions on page 87
You create custom property denitions that determine how the custom property appears in
vRealize Automation. You can validate the custom property in a test blueprint before adding it to your
production blueprints.
2 Add a Custom Property to a Blueprint on page 95
You can add custom properties to many parts of vRealize Automation, including approval policies,
business groups, endpoints, and reservation policies. However, only the machine blueprints support
the display options that you congure as property denitions. Adding a custom property to a
blueprint as a simple way to verify that the custom property appears in the user interface as you
designed it in the property denition.
3 Verify the Custom Property in the Catalog Request Form on page 97
As creator of the custom property denitions that run vRealize Orchestrator actions, you test your
custom properties to ensure that the correct values appear in the request form.
Custom Properties Reference
86 VMware, Inc.