7.4

Table Of Contents
The following list shows the order of precedence for custom properties. Property value specified in a
source that appears later in the list override values for the same property specified in sources that appear
earlier in the list.
Note If a conflict exists between a vRealize Automation-supplied custom property name and a user-
defined property name, the vRealize Automation-supplied custom property name takes precedence.
1 Property group
2 Blueprint
3 Business group
4 Compute resource
5 Reservations
6 Endpoint
7 Runtime
Property group, blueprint, and business group custom properties are assigned at request time, while
other compute resource, reservation, and endpoint properties are assigned during provisioning.
This order is further clarified as follows:
1 Custom properties and groups at the overall blueprint level
2 Custom properties and groups at the component level
3 Custom properties for the business group
4 Custom properties for the compute resource
5 Custom properties for the reservation
6 Custom properties for the endpoint
7 Custom properties at the nested blueprint request level
8 Custom properties at the component request level
In most situations, a runtime property takes precedence over other properties. A runtime property meets
the following conditions:
n
The property option to prompt the user is selected, which specifies that the user must supply a value
for the property when they request machine provisioning.
n
A business group manager is requesting machine provisioning and the property appears in the
custom properties list on the machine request confirmation page.
Custom Properties Reference
VMware, Inc. 9