---
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


---

# Solution configurations

# Solution configurations {#ariaid-title1}

Release version: Brazil  
Updated March 26, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 Solution configurations

Solution configurations in ServiceNow CPQ allow you to link multiple blueprints, enabling buyers to complete related product configurations within a single, connected session.
This approach is ideal for complex products composed of separate, independently configurable components (e.g., hardware and software).
Each blueprint can be managed and updated independently, while also being reused across multiple solutions.
A configuration becomes a solution when it includes at least one child configuration linked to a parent blueprint, creating a unified configuration session with a consolidated bill of materials (BOM).
Show full answer Show less  
Note that solution configuration is an environment-level feature that is disabled by default and must be enabled through ServiceNow Support.

## Key Features

* **Solution root:** The top-level configurable product that initiates the configuration session.
* **Solution hierarchy:** Parent-child relationships between blueprints in the session, supporting up to four levels in depth.
* **Configurable product actions:** Specialized product actions that link blueprints by triggering child configurations and allow field data to be mapped between configurations.
* **Solution BOM:** An aggregated bill of materials consolidating all products configured across the entire solution session.
* **Field mapping:** Enables passing data values from parent to child blueprints during configuration creation or updates.

## Benefits for ServiceNow CPQ Administrators

* **Independent deployment:** Blueprints can be updated and deployed separately, enabling fine-grained control.
* **Separation of concerns:** Different teams can work on distinct blueprints without conflict.
* **Blueprint reusability:** Blueprints can be reused across multiple solutions or configured independently, reducing duplication and maintenance efforts.

## Benefits for End Users

* Seamless navigation through multiple linked configurations without relaunching the CPQ interface.
* Ability to clone valid child configurations fully independently within set-based solutions.
* Flexibility to add or remove nodes from the solution navigation sidebar as needed.

## When to Use Solution Configurations

Choose solution configurations to manage complex, multi-component products where each component is managed as a separate blueprint but requires a cohesive buyer experience. For simpler configuration needs, alternatives such as Sets (for large row configurations), Product Pickers (for lightly configurable products), or multiple independent configurations (when outputs must remain unlinked) may be more appropriate.  
Solution configurations let you link multiple blueprints together so buyers complete related product configurations in a single, connected session.

A solution configuration combines two or more blueprints into a coordinated configuration session. When a buyer reaches a product that requires additional configurable components, each component opens in its own child configuration ---
linked to the parent through configurable product actions. The result is a unified session with a consolidated bill of materials (BOM).

Solution configurations suit complex products that span multiple independent blueprints, such as a platform product that includes separately configurable hardware and software components. Each blueprint can be deployed and updated
independently, and the same blueprint can participate in multiple solutions.

A configuration becomes a solution when at least one child configuration is added. The product that a buyer starts from is the solution root. From the root, any number of child configurations --- and child-of-child configurations --- can
be created based on rules defined in the admin.  
Note:  
Solution configuration is an environment-level feature that is off by default. Contact Support to enable it for your environment by using the [ServiceNow Support portal](https://support.servicenow.com). For step-by-step instructions, see [Create a case on Now Support for CPQ Customers](https://support.servicenow.com/kb?sys_kb_id=d67d3e71475d7a90f64de825126d4326&id=kb_article_view).

## What is solution configuration {#solution-configurations__section_what_is_solution_config}

Configurable product actions are a specialized type of product action that can be added to rules. They are similar to standard product actions, but have a blueprint defined and can include field mapping to pass data between
configurations. Advanced configurable product actions require that the product ID and the blueprint fields are defined outside of the script.

Solution configuration enables you to create interconnected blueprint hierarchies where:

* A solution root is the topmost configurable product that is launched by the end user.
* A parent (source) blueprint includes a rule with a configurable product action for another blueprint.
* A child (target) blueprint is used to create a child configuration when a configurable product action is triggered.
* A solution BOM is the aggregated bill of materials that rolls up across all configurations in the solution.

## Benefits of solution configuration {#solution-configurations__section_benefits}

Solution configuration provides distinct advantages for both ServiceNow CPQ administrators and end users.

For administrators
:
    * Independent deployment: Each blueprint can be deployed independently, allowing for finer granularity when making changes or updates to a blueprint.
    * Separation of concerns: Segment logical components from a configuration and allow different teams to work on blueprints without conflicting.
    * Blueprint reusability: Blueprints can be reused as part of a solution, multiple solutions, or as independently configurable products, reducing duplication and maintenance overhead.
    {#solution-configurations__ul_admin_benefits}

For end users
:
    * End users can seamlessly work through multiple configurations without needing to relaunch ServiceNow CPQ each time.
    * Users can clone valid child configurations in set-based solutions, with cloned nodes being fully independent of the original.
    * Users can add blank nodes or remove nodes from the solution navigation sidebar as needed.
    {#solution-configurations__ul_enduser_benefits}

## Key concepts {#solution-configurations__key-concepts}

* Solution root: the top-level configurable product a buyer launches. All other configurations in the session are descendants of the root.
* Solution hierarchy: the parent-child relationship between configurable products in a session. The hierarchy is independent of the BOM hierarchy and supports a maximum depth of four levels, including the root.
* Solution BOM: the consolidated bill of materials that rolls up all products added across every configuration in the session.
* Field mapping: a mechanism for passing field values from a parent blueprint to a child blueprint when a child configuration is created or when a mapped source field changes.

## When to use solution configurations {#solution-configurations__when-to-use}

Solution configurations work well when you need to manage complex products as separate, independently deployable blueprints while keeping the buyer experience connected. For simpler scenarios, consider these alternatives:

* Sets: use when managing large numbers of rows that may have different configurations within the same blueprint.
* Product Pickers: use for lightly configurable products that do not require a separate blueprint.
* Multiple independent configurations: use when downstream systems require separate, unlinked configuration outputs.
**Related tasks**   

* [Enable solution configuration](https://servicenow-prod.fluidtopics.net/BDLQ_qMXZaZFEYT9bhKpLw "Enable solution configuration for an environment to let admins link multiple blueprints into connected configuration sessions.")  
**Related reference**   

* [Solution configuration terminology](https://servicenow-prod.fluidtopics.net/2CBGpTJpB3UsQ4GnRxd~1A "Terms used in solution configurations and their definitions.")
* [Solution configuration limits](https://servicenow-prod.fluidtopics.net/nbj6PfmJBDA_n0UGWXbv5w "Structural limits that apply to solution configurations, including hierarchy depth, total configuration count, and field mapping constraints.")
* [Field mapping supported field types](https://servicenow-prod.fluidtopics.net/4kKI4lQyJAkivj9xKDkONA "Field types that are supported as source and target fields in solution configuration field mappings.")

