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

# Solution configuration setup {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 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 configuration setup

Solution configuration in ServiceNow CPQ enables administrators to manage multiple blueprints within a single configuration environment.
This feature, currently off by default, requires activation through ServiceNow CPQ Support.
It introduces configurable product actions---specialized product actions linked to blueprints and capable of passing data between configurations via field mapping.
This setup enhances modularity and reusability across configurations.
Show full answer Show less  

## Key Features

* **Configurable Product Actions:** These actions define blueprints and allow data exchange between configurations through field mappings. Advanced configurable product actions require predefined product IDs and blueprint fields outside scripts.
* **Blueprint Management:** Each blueprint can be deployed independently, facilitating granular updates and reducing conflicts by allowing different teams to work on separate logical components.
* **Blueprint Reusability:** Blueprints can be reused across multiple solutions or independently, minimizing duplication and maintenance overhead.
* **End User Experience:** Users can seamlessly navigate multiple configurations without restarting ServiceNow CPQ. Features include cloning valid child configuration nodes, adding blank nodes, and removing nodes within the navigation sidebar.
* **Solution Navigation:** When multiple configurable products are added, a navigation sidebar appears to manage and switch between configurations. The root configurable product initializes the solution.
* **Bill of Materials (BOM):** The solution hides the default product list and provides a "View Full Solution" button showing the entire BOM at the solution root. Individual product tiers show only relevant child configurations.
* **Node Cloning:** Enables duplication of valid configuration nodes, including field values, for efficient creation of new nodes. Cloned nodes are independent of the originals, ensuring changes remain isolated.
* **Layout Management:** Each solution component uses layouts defined in its blueprint, while the root layout controls headers, styles, buttons, and product list display. The navigation sidebar activates with additional configurable products.
* **Field Mapping:** Supports data passing between fields of the same type during child configuration creation or field changes, limited to a single mapping level and excluding sets and product pickers.

## Key Outcomes

* **For Administrators:** Enables modular deployment and collaboration by segmenting configurations into reusable blueprints, improving maintainability and reducing duplication.
* **For End Users:** Provides a streamlined experience navigating complex configurations without restarting the application, with capabilities to clone and manage configuration nodes efficiently.
* **Error Handling:** Common issues include missing or undeployed blueprints, incorrect blueprint associations, and field mapping errors, which are important to monitor for smooth configuration management.
* **Flexibility:** Supports large configurations through sets and product pickers, and allows multiple independent configurations for enhanced downstream system compatibility.  
Solution configuration lets ServiceNow CPQ admins manage multiple blueprints in a single configuration. Configurable product actions include a blueprint definition and can pass data between configurations via defined fields.
Solution configuration is an environment level feature that is off by default. To have it enabled in an environment, log a case with ServiceNow CPQ Support.

Configurable product actions are a new 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.

## Benefits {#solution-configuration-setup__section_yb1_24t_fhc}

* For administrators:
  * Independent deployment: Each blueprint can be deployed independently, which allows for finer granularity when making changes or updates to a blueprint.
  * Separation of concerns: Administrators can segment out logical components from a configuration and allow different groups to work on blueprints without conflicting.
  * Blueprint reusability: Blueprints can be reused both as part of a solution, multiple solutions, or as an independently configurable product. This leads to less duplication when a blueprint is needed for multiple contexts and less overhead for maintenance.
  {#solution-configuration-setup__ul_hfn_g4t_fhc}
* For end users:
  * End users can seamlessly work through multiple configurations without needing to re-launch ServiceNow CPQ each time.
  * You can clone the child configuration if it is a set-based configuration. The original node in a set must be in the valid state. Cloned nodes are independent of the original edits to a cloned node do not affect the source node.
  * You can also add a blank node or remove node from the navigation sidebar.
  {#solution-configuration-setup__ul_ekj_fy3_43c}
{#solution-configuration-setup__ul_zzc_f4t_fhc}

## The end user experience {#solution-configuration-setup__section_mzq_m4t_fhc}

* Launching a solution: Users launch the configurable product that they want to start from, just as they do normally. Whichever configurable product is launched becomes the root product for the solution.
* Adding configurable products: When any of the defined rules that have a configurable product action are triggered, a new child configuration is created if a valid configurable product with a deployed blueprint is found.
* When additional configurable products are added to the configuration, solution navigation becomes available and shows a list of the current configurable products, including the root configurable product.
* Changing the condition of a configurable product action rule to false removes the configuration and configurable product, just as in a normal product action. This also removes changes to fields, products, nested children, or other items.
* Viewing the bill of materials: When a configuration becomes a solution, the default product list component is hidden and replaced by the View Full Solution button in all configurations. In a solution, View Full Solution displays the entire solution BOM. Additional product lists added as tiers reflect only the currently selected configurable product and any of the child configurations below it.
{#solution-configuration-setup__ul_zcw_n4t_fhc}

## Potential errors with configurable product actions {#solution-configuration-setup__section_irs_5mt_fhc}

Errors related to configurable product actions may include the following:

* The configurable product is not found
* The configurable product does not have a blueprint associated with it
* The configurable product does not have a deployed blueprint
* The blueprint does not exist
* The blueprint is not deployed
* The blueprint has changed
{#solution-configuration-setup__ul_uyd_2pp_5hc}

## Field mapping {#solution-configuration-setup__section_rvd_ynt_fhc}

Field mapping defines which fields have data passed to or from them. Field mapping happens on creation of a child configuration or when a mapped source field is changed. Fields are only mapped a single level, to continue the mapping
define the mapped fields on each blueprint. Fields can only be mapped to the same type of field: text to text, number to number, and so on.

Entire sets and product pickers cannot be mapped.

## Node cloning for solution configurations {#solution-configuration-setup__section_c1g_p4q_43c}

Node cloning lets you duplicate an existing, valid solution configuration node to use as the starting point for a new node. When you clone a node, both the fields and their values are copied --- so you don't have to re-enter
configuration data for each new node from scratch.

Cloned nodes are fully independent of the original. Changes you make to a cloned node don't affect the source node, and changes to the source node don't affect the clone.

Cloning is available from the solution configuration in a set using the navigation sidebar. A node must be in a valid state before you can clone it --- this prevents incomplete configurations from being duplicated. When you clone a node
that has a dependent set, a corresponding child node is created as part of the cloning operation.

## Layout {#solution-configuration-setup__section_h5r_znt_fhc}

Each solution component displays its own layout from the layouts associated with the current blueprint.

When in a solution, the header, background style, buttons and product list display comes from the solution root layout that is defined in the root blueprint.

The solution navigation sidebar automatically appears when additional configurable products are added during a configuration.

## Bill of materials (BOM) {#solution-configuration-setup__section_qyx_c4t_fhc}

The bill of materials shows the items from the currently viewed configuration and any child configurations below. The entire solution BOM can be viewed at the solution root.

The BOM hierarchy is still defined via the parent product and the unique identifier fields in product actions. It is independent of the solution hierarchy, and one does not necessarily reflect the other. A child configuration may add
top level items to the bill of materials.

## Other options {#solution-configuration-setup__section_myv_j4t_fhc}

* Sets make it easy to handle large numbers of rows with potentially different configurations. They support cloning rows, while set repeater layout options provide visual similarity.
* Product pickers work well with lightly configurable products and can be customized with additional fields and bulk actions.
* Depending on the downstream system, making multiple independent configurations may provide more flexibility than a single solution configuration.
{#solution-configuration-setup__ul_d4t_k4t_fhc}
**Related concepts**   

* [Node cloning for solution configuration](https://servicenow-prod.fluidtopics.net/vebnRKmcwX8fjr5NFdK1uw "Node cloning lets you duplicate an existing solution configuration node in a set, producing an independent copy that you can modify without affecting the source.")

