7.2

Table Of Contents
n
You can apply an approval policy to a blueprint. When approved, the blueprint catalog item and all its
components, including nested blueprints, are provisioned. You can also apply different approval
policies to different components. All the approval policies must be approved before the requested
blueprint is provisioned.
n
When you edit a published blueprint, you are not changing deployments that are already provisioned
by using that blueprint. At the time of provisioning, the resulting deployment reads current values from
the blueprint, including from its nested blueprints. The only changes you can pass on to provisioned
deployments are edits to software components, for example edits to update or uninstall scripts.
n
Settings you define in the outer blueprint override settings configured in nested blueprints with the
following exceptions:
n
You can change the name of a nested blueprint, but you cannot change the name of a machine
component, or any other component, inside a nested blueprint.
n
You cannot add or delete custom properties for a machine component in a nested blueprint.
However, you can edit those custom properties. You cannot add, edit, or delete property groups
for a machine component in a nested blueprint.
n
Changes you or another architect make to nested blueprint settings appear in the outer blueprints,
unless you have overridden those settings in the outer blueprint.
n
Limit the maximum lease time on the outer blueprint to the lowest maximum lease value of a
component blueprint.
While the lease time specified on a nested blueprint and on the outer blueprint can be set to any
value, the maximum lease time on the outer blueprint should be limited to the lowest maximum lease
value of a nested blueprint. This allows the application architect to design a composite blueprint that
has uniform and variable lease values, but is within the constraints identified by the infrastructure
architect. If the maximum lease value defined on a nested blueprint is less than that defined on the
outer blueprint, the provisioning request fails.
n
When working in an outer blueprint, you can override the Machine Resources settings that are
configured for a machine component in a nested blueprint.
n
When working in an outer blueprint, you can drag a software component onto a machine component
within a nested blueprint.
n
If you open a blueprint in which a machine component a nested blueprint was removed or its ID was
changed, and the machine component was associated to components in the current blueprint, the
associated component are removed and the following or similar message appears:
A machine component in a nested blueprint that is referenced by components in the current blueprint
was removed or its machine component ID was changed. All components in the current blueprint that
were associated to the missing or changed machine component ID have been removed. Click Cancel
to keep the association history between the missing or changed machine component ID in the nested
blueprint and components in the current blueprint and correct the problem in the nested blueprint.
Configuring vRealize Automation
VMware, Inc. 482