---
sourceDocument: Brazil Sales Customer Relationship Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/order-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Sales Customer Relationship Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Set up blueprints

# Set up blueprints {#ariaid-title1}

Release version: Brazil  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Set up blueprints

Blueprints in ServiceNow CPQ define and manage the entire configuration experience by acting as containers that bring together fields, rules, layouts, and configurable products.
They enable administrators to design, deploy, and manage configuration workflows across different environments.
A blueprint determines the user interface and the subset of fields and rules relevant for a specific configuration experience.
Show full answer Show less  

## Blueprint Components and Associations

* **Fields:** Blueprints associate with global fields including sets, product pickers, and system fields. System fields support Salesforce integration by automatically pulling data during initialization.
* **Rules:** Rules relate automatically to a blueprint if all referenced fields are associated. Rules can be active (applied during runtime) or inactive (stored but not applied).
* **Layouts:** Each layout is uniquely tied to one blueprint and supports its configuration experience. Multiple layouts can exist per blueprint, with the most recently modified layout used by default.
* **Configurable Products:** Configurable products link to one blueprint and launch the corresponding configuration experience, including through Salesforce integration. Multiple products can share the same blueprint.
* **Enrichments:** Enrichment scripts run outside the rules engine to handle tasks like initialization, validation, and pricing adjustments.

## Blueprint Definition Page

The blueprint definition page provides tabs to view and manage all associated elements (fields, rules, layouts, configurable products, deployments, and enrichments). It offers metadata details, search capabilities, and editing options for each element type.

## Deploying Blueprints

Blueprints must be deployed to be available to end users. Edits to blueprint components are not visible until deployment. Deployment can be initiated from the blueprint list or within a blueprint record. The deployment status is visible with icons indicating deployed, not deployed, or expiring soon.

Deployment behavior varies by environment type:

* **Production:** Blueprints remain deployed indefinitely regardless of user activity.
* **Test environments:** Blueprints auto un-deploy after 30 days of no user engagement but can be redeployed or reactivated by launching configuration.
* **Demo environments:** Blueprints auto un-deploy every weekend.

Deployment notifications indicate progress and completion status.

## Practical Benefits for ServiceNow Customers

* Blueprints enable modular, reusable configuration experiences tailored to specific products or workflows.
* They streamline administration by grouping related fields, rules, layouts, and products, simplifying configuration management.
* Integration with Salesforce allows seamless launching of configuration experiences through product records.
* Deployment controls ensure that configuration updates are tested and controlled before end-user exposure.  
Blueprints define the structure of a configuration experience in ServiceNow CPQ. They act as containers that bring together fields, rules, layouts, and configurable products, enabling administrators to design, deploy, and manage
complete configuration workflows across environments.
The blueprint defines the configuration experience. It acts as a container for all the parts necessary to be plugged in for the end- user interface. Because ServiceNow CPQ rules and fields are global, they can be used to facilitate any number of configuration experiences. The blueprint record allows the administrator to associate the subset of the fields and rules that are
relevant to the configuration experience it represents. Further, the blueprint defines layouts and configurable products.

Unlike fields and rules, layouts can only be associated with one blueprint. A layout is defined and built in the context of, and to explicitly support, one blueprint --- one configuration experience. However, a blueprint may have
multiple layouts.

For Salesforce-integrated organizations, the configurable product element determines the SFDC Product2 record that, when quoted in Salesforce, launches the configuration experience defined by a blueprint. Multiple configurable
products can launch the same blueprint. However, each configurable product can only be associated with one blueprint.

For a step-by-step guide to creating a blueprint, see [Create a blueprint](https://servicenow-prod.fluidtopics.net/YGRdC0WAReadpxrE76bfSQ "Create a blueprint to define the structure, behavior, and configuration experience for your product model.").

## The blueprint definition page {#blueprints_101__section_xxx_5zw_zgc}

The blueprint definition page holds all of the different elements that are associated with the blueprint. Each tab indicates the number of elements associated if relevant. Clicking each shows specific metadata and lets you search
by name or variable name, or edit each element in the blueprint.

## The Associated Fields tab {#blueprints_101__section_c1v_xzw_zgc}

This tab shows all of the fields that have been associated with the blueprint. The name, type, variable name, description, and last modified date of the fields are shown to the admin on this page, as well as the username of the
user that last modified the field. You can also drill down to specific field types associated to the blueprint, such as sets, product pickers, and system fields.


* Standard: Shows global fields associated with the blueprint.
* Sets: Shows the sets and set subfields associated with the blueprint. Once a set is associated, each subfield added is automatically associated with the blueprint.
* Product Pickers: Shows the product pickers and product picker subfields associated with the blueprint.
* System: Automatically associated with each blueprint. If integrated with Salesforce, these fields pull data automatically upon initialization without the need to specify it in an external connection.

{#blueprints_101__ul_skz_b1x_zgc}

To learn more about fields and how to associate them with blueprints, see [Configure fields](https://servicenow-prod.fluidtopics.net/EessbbI2ktejRqnHQ~1hVw "Learn about how fields in ServiceNow CPQ help structure data collection efficiently and about the various types of field. Associate fields with blueprints for consistent use across configurations, layouts, and rules.").

## The Related Rules tab {#blueprints_101__section_d1q_t1x_zgc}

This tab shows all of the rules that are related to the blueprint. Unlike fields, rules connect to a blueprint automatically as long as every field referenced by the rule is associated with the blueprint. The name, variable name,
description, action types, and last modified date of the rules are shown to the admin on this page, as well as the username of the user that last modified the rule.


Active: Shows what rules are currently set to active in their definition. When a rule is active, it is included as a valid rule during deployment and enacts its Actions when its Conditions are fulfilled during runtime.

Inactive: Shows what rules are currently set to inactive in their definition. They are still related to the blueprint and is included if the blueprint is exported, but they aren't valid when deployed and don't enact their actions
during runtime.

## Layout {#blueprints_101__section_wq1_w1x_zgc}

This tab hows all of the layouts that have been created for the blueprint. The most recently modified layout is the layout generated unless otherwise specified. The name, variable name, last modified date, and the username of the
user that last modified the layout are located on this page.


## The Configurable Product tab {#blueprints_101__section_rv4_z1x_zgc}

This tab shows the configurable products that are linked to the blueprint. Calling a runtime API with any of the associated configurable products with the blueprint, or configuring from the product through a third-party such as
Salesforce, immediately launches the blueprint. The name and product ID are present, and an admin can delete a product by clicking the Trash icon on the left.


## The Deployments tab {#blueprints_101__section_vzw_1bx_zgc}

This tab shows the fifty most recent deployments for the blueprint. The blueprint name, variable name, and last deployment date and time are visible here, along with the username of the user that last deployed the blueprint.


You can also see a list of the environment's most recent deployments in the Utilities menu on the Deployment page. See [Viewing blueprint deployments](https://servicenow-prod.fluidtopics.net/wgtCa8nDt5y~IThCVrzLkg "The Deployments page shows the fifty most recently deployed blueprints together with their timestamps and associated users.").

## The Enrichments tab {#blueprints_101__section_e3z_bbx_zgc}

This tab shows the enrichment scripts that have been created for the blueprint. These scripts run outside of the rules engine and enact their functions on their own areas, such as on initialization, BOM response, validation, or
picklist extension pricing. An admin can edit these scripts or delete them using the Trash icon on the far left. For more information about enrichment scripts, see [Using external connections with OAuth support](https://servicenow-prod.fluidtopics.net/XH_swCKZ1FBaHoD9Xmnrmw "External connections allow enrichments to retrieve data from third-party systems to enhance configurations. When security requires OAuth, you can set up an OAuth handshake using client credentials to authenticate and access external APIs. This approach ensures secure data exchange for tasks such as pricing updates or attribute population during configuration.").


## Deploying a blueprint {#blueprints_101__section_wlb_2bx_zgc}

ServiceNow CPQ configuration experiences are deployed (made available to application end users) at the blueprint level. Administrator edits to fields, rules, layouts, and configurable products are not visible to the end
user until deployed.

To deploy a blueprint, in the Blueprints list administration page, check the box to the left of the blueprint to deploy, and then select Deploy. (You can also select Deploy in the
blueprint itself.)


The blueprint administration list page shows the deployment status of each blueprint. Icon key:


![Deployed icon]() Deployed

![Not deployed icon]() Not deployed

![Expiring Soon icon]() Expiring Soon

In production sector environments provided to ServiceNow CPQ customers, once a blueprint is deployed, it remains deployed, no matter its end-user activity.

In test sector environments provided to ServiceNow CPQ partners, blueprints are automatically un-deployed after a period of thirty days with no end-user engagement. Redeploying the blueprint or launching a configuration of the blueprint resets the thirty-day
period after ServiceNow's database syncs each evening.

In demo sector environments, blueprints are automatically un-deployed every weekend.

After a blueprint is deployed, a notification alerts you to the status of the deployment process (either In Progress or Completed).


**Related concepts**   

* [Testing in non-production environments before migration](https://servicenow-prod.fluidtopics.net/2XqZX9Zh~5vcpW5AJ5PV_A "Test configurators in a non-production environment before migrating them to production. The configurators support revenue-critical processes, validate all changes outside production and promote them using controlled environment-to-environment migrations.")
* [ServiceNow CPQ fields, system fields, and partner fields](https://servicenow-prod.fluidtopics.net/HVtsYoocfzNKUKZ5buQi6w "Learn about the three types of fields in ServiceNow CPQ—ServiceNow CPQ, system fields, and partner fields. Understand how each type stores, retrieves, and displays data in configurations, and how they interact with Salesforce and partner systems for seamless data integration.")
* [Configure fields](https://servicenow-prod.fluidtopics.net/EessbbI2ktejRqnHQ~1hVw "Learn about how fields in ServiceNow CPQ help structure data collection efficiently and about the various types of field. Associate fields with blueprints for consistent use across configurations, layouts, and rules.")  
**Related tasks**   

* [Create a blueprint](https://servicenow-prod.fluidtopics.net/YGRdC0WAReadpxrE76bfSQ "Create a blueprint to define the structure, behavior, and configuration experience for your product model.")  
**Related reference**   

* [Boundaries and limits](https://servicenow-prod.fluidtopics.net/PqajQOwIfjq79cns~3BJ9w "View a list of boundaries and limits in ServiceNow CPQ.")

