---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Form configuration with blueprints

# Form configuration with blueprints {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Blueprints control what the user sees on the catalog order form. You can configure the
form to show or hide fields, populate fields with default values, and otherwise create a unique
form for the user based on criteria.
Note:  
* Starting with Orlando, Cloud Provisioning blueprints are available on instances upgraded from a previous release but you cannot create new blueprints. Resource profiles and custom-created blueprints will no longer be supported starting with the Australia release.
* Use Cloud Provisioning cloud templates to create catalog items in place of blueprints. Cloud Provisioning [cloud templates](https://www.servicenow.com/docs/gIdpgEQRixhZ92fK3LyyiA "Create a cloud template and associate the template with a catalog item. Once you've created a template, you can reuse the template to create additional catalog items for the services you want to provision.") allow you to ingest Azure ARM, AWS CFT, Google Deployment Manager (GDM) and Terraform specification syntax in cloud catalog items to run your cloud deployment orchestration.
{#blueprint-form-configuration__ul_qrq_hlc_hlb}

You can also change the values in form fields using policies. See [Create a cloud policy](https://www.servicenow.com/docs/0sIkTZnZ6Ejj2VWKacaJ4w "A cloud policy can override a property value set by a user, create an approval task, reserve an IP address, pre-populate or hide form fields, execute custom scripts, call the Cloud API, or start or abort workflows. A cloud policy gives you system-wide control over approvals, resource operations, blueprint operations, or catalog item settings.") and [Create a policy action script](https://www.servicenow.com/docs/HJokDoCw~8BcEZtW_W13Zw "Use policy action scripts to get, update, or set values in cloud requests.") for examples.

## Components of blueprint form configuration {#blueprint-form-configuration__section_qn2_zlx_q2b}

Blueprints use these components to control how the system uses catalog form fields:

* Catalog variables define the basic structure of each field on catalog order forms.
* Rules specify an action that the system takes on a field when a condition is met.
* Scripts query the system for information that you need to show the catalog requester, populate form fields, and process the data that users submit.
* UI groups to put related fields together in a tab. Users can progress through tabs to fill out all the form fields.
{#blueprint-form-configuration__ul_a3x_bmx_q2b}

## Start here {#blueprint-form-configuration__section_olt_wvp_q2b}

These tasks show you the basics of form configuration with blueprints:

* [Add fields to a cloud catalog item order form](https://www.servicenow.com/docs/nhTjVtHSYqxHD17euFDJDg "You can add fields to a cloud catalog form if you want the user to enter additional information beyond what a default blueprint provides.")
* [Control visibility default values for Cloud catalog items](https://www.servicenow.com/docs/i7aS8tDCu2WR_C9qZcwfCw "Through blueprints, you can control how form fields appear to users in the cloud catalog. For example, you can control where the fields appear to users on the catalog item form, and whether they are read only or mandatory.")
* [Create a variable set for Cloud Provisioning and Governance](https://www.servicenow.com/docs/ZKnExyFJo7FB0HKL04dcAA "Reduce the number of steps required to create and manage multiple catalog items and order guides by creating variable sets. With variable sets, you don't have to create variables individually for each catalog item.")
{#blueprint-form-configuration__ul_jcf_2wp_q2b}

## Examples {#blueprint-form-configuration__section_yjp_mxj_t2b}

These examples guide you through form configuration based on a specific goal: [Cloud catalog form configuration examples](https://www.servicenow.com/docs/Kcygn9wjLvI~pxzV~7UKWw "Several examples are provided to help you understand how to manipulate Cloud catalog order forms. These example cover blueprint rules, blueprint variables, and blueprint form UI groups.").
* **[Add fields to a cloud catalog item order form](https://www.servicenow.com/docs/nhTjVtHSYqxHD17euFDJDg)**   
  You can add fields to a cloud catalog form if you want the user to enter additional information beyond what a default blueprint provides.
* **[Control visibility default values for Cloud catalog items](https://www.servicenow.com/docs/i7aS8tDCu2WR_C9qZcwfCw)**   
  Through blueprints, you can control how form fields appear to users in the cloud catalog. For example, you can control where the fields appear to users on the catalog item form, and whether they are read only or mandatory.
* **[Cloud catalog form configuration examples](https://www.servicenow.com/docs/Kcygn9wjLvI~pxzV~7UKWw)**   
  Several examples are provided to help you understand how to manipulate Cloud catalog order forms. These example cover blueprint rules, blueprint variables, and blueprint form UI groups.

**Related tasks**   

* [Build a Cloud Provisioning blueprint](https://www.servicenow.com/docs/EFg~MX6L_NVB5~4R31bKpg "Use the blueprint designer to create custom blueprints for the Cloud Provisioning and Governance application. Blueprints are deprecated in the Orlando release.")