7.4

Figure 3‑7. Controlling the Build Order by Mapping Dependencies
If you are designing blueprints to be scalable, it is a best practice to create single layer blueprints that do
not reuse other blueprints. Normally, update processes during scale operations are triggered by implicit
dependencies such as dependencies you create when you bind a software property to a machine
property. However, implicit dependencies in a nested blueprint do not always trigger update processes. If
you need to use nested blueprints in a scalable blueprint, you can manually draw dependencies between
components in your nested blueprint to create explicit dependencies that always trigger an update.
Customizing Blueprint Request Forms
Every blueprint that you create and publish displays a form when your users request the blueprint in the
catalog. You can use the default form or you can customize blueprint request forms when you create or
edit a blueprint. You customize a form when the information provided or required on the default form is not
what you want to present to your users.
Customizing Request Forms
You access the custom request form designer from the blueprint data grid or from the blueprint canvas.
Custom Request Form Designer
You use the form designer to create your custom form.
Configuring vRealize Automation
VMware, Inc. 521