A blueprint is a complete specification for a service. With service blueprints, you can publish predefined and custom vRealize Orchestrator workflows as catalog items for requesting.

Blueprints for requesting run workflows with no provisioning and provide no options for managing a provisioned item. You cannot perform post-provisioning operations on this type of provisioned resource. For example, you can create a service blueprint for adding a Puppet Master.

Log in to the vRealize Automation console as a service architect.


Select Advanced Services > Service Blueprints.


Click Add (Add a service blueprint).


Navigate through the vRealize Orchestrator workflow library and select a workflow.

You can see the name and description of the selected workflow, and the input and output parameters as they are defined in vRealize Orchestrator.

For example, you can select the Puppet workflow.


Click Next.


Enter a name and, optionally, a description.

The Name and Description text boxes are prepopulated with the name and description of the workflow as they are defined in vRealize Orchestrator.


(Optional) If you do not want to prompt consumers to enter a description and reason for requesting this resource action, select the Hide catalog request information page check box.


(Optional) Add the version number of the workflow if you have existing iterations of the workflow.


Click Next.


Accept the default service blueprint.

By default, the service blueprint form is mapped to the vRealize Orchestrator workflow presentation.


Click Next.


Accept the default No provisioning output parameter.

The service blueprint does not add new items on the Items tab.


Click Add.

The new service blueprint appears on the Service blueprints page.