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
2 Add a Custom Property to a Blueprint
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 configure as property definitions. 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 definition.
3 Verify the Custom Property in the Catalog Request Form
As creator of the custom property definitions that run vRealize Orchestrator actions, you test your
custom properties to ensure that the correct values appear in the request form.
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.
n
Create a Property Definition
You can create property definitions to allow for additional levels of vRealize Automation
customization. When you create a property definition, you specify a data type for the property, for
example a string or a boolean type.
n
Create a Custom Property That Validates Against a Regular Expression
You create custom property definition that evaluates a regular expression when you want service
catalog users to provide validated data on the catalog request form.
n
Create a vRealize Orchestrator Action Custom Property Definition
You create a custom property definition that includes a vRealize Orchestrator action so that you can
add the custom property to a blueprint. The action runs when the service catalog user is configuring
the custom property in the request form. The action retrieves the data that is displayed in the form.
n
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.
Create a Property Definition
You can create property definitions to allow for additional levels of vRealize Automation customization.
When you create a property definition, you specify a data type for the property, for example a string or a
boolean type.
To avoid potential conflict with supplied vRealize Automation custom properties, use a naming format of
my_prefix.my_property_name1. For example, use a standard and meaningful prefix such as company or
feature name, followed by a dot (.), followed by a brief but descriptive name. Properties that you create
that do not follow this recommendation may conflict with vRealize Automation-supplied custom properties.
In that event, the vRealize Automation custom properties take precedence over properties that you
create.
Custom Properties Reference
VMware, Inc. 102