7.4
Table Of Contents
- Custom Properties Reference
- Contents
- Custom Properties Reference
- Custom Properties and the Property Dictionary
- Using Custom Properties
- Custom Properties Grouped by Function
- Custom Properties for Deployments
- Custom Properties for Naming and Analyzing Deployments
- Custom Properties for OpenStack Endpoints
- Custom Properties for Clone Blueprints
- Custom Properties for Linked Clone Blueprints
- Custom Properties for FlexClone Blueprints
- Custom Properties for Basic Workflow Blueprints
- Custom Properties for Linux Kickstart Blueprints
- Custom Properties for SCCM Blueprints
- Custom Properties for WIM Blueprints
- Custom Properties for vCloud Air and vCloud Director Blueprints
- Custom Properties for Networking and Security
- Custom Properties and Property Groups for Containers
- Custom Properties for PXE Provisioning
- Custom Properties for OVF Import
- Custom Properties for vRealize Automation Guest Agent
- Custom Properties for BMC BladeLogic Configuration Manager Integration
- Custom Properties for HP Server Automation Integration
- Custom Properties Grouped by Name
- Custom Properties Underscore (_)
- Custom Properties A
- Custom Properties B
- Custom Properties C
- Custom Properties E
- Custom Properties H
- Custom Properties I
- Custom Properties L
- Custom Properties M
- Custom Properties N
- Custom Properties O
- Custom Properties P
- Custom Properties R
- Custom Properties S
- Custom Properties V
- Custom Properties X
- Using the Property Dictionary
- Using Property Definitions
- Using Property Groups
- Defining Component Profile Settings
Limitations
If you create a property definition where Data type equals String, Display as equals Dropdown, and
you use a vRealize Orchestrator action that returns properties that populate the drop-down list, the list is
in random order. You cannot specify the order.
Create and Test Custom Property Deļ¬nitions
You create a custom properties definition 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 definitions, 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 Configuring vRealize
Automation.
n
Verity that the blueprint is entitled to you so that you can test the custom properties in the blueprint.
See Configuring vRealize Automation.
n
Log in to vRealize Automation as a tenant administrator or fabric administrator.
Procedure
1 Create Custom Property Definitions
You create custom property definitions 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.
Custom Properties Reference
VMware, Inc. 101