---
sourceDocument: Australia Sales and Order Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/order-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Sales and Order Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Blueprints, fields, rules, layouts, and BOMs

# Blueprints, fields, rules, layouts, and BOMs {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Learn how the core building blocks of ServiceNow CPQ---blueprints, fields, rules, layouts, and bills of material (BOMs)---work together to power configuration and transaction experiences.

## Blueprints {#blueprints-fields-rules-layouts-and-boms__section_bsn_znv_5gc}

Blueprints define the configuration model for a product or offering. They include all the attributes, rules, and user experiences required to guide users through selection and configuration.

* Each blueprint represents a distinct configurator.
* Blueprints connect directly to transaction workflows through Transaction Manager.
* A blueprint includes fields, rules, layouts, and optional BOM definitions.
{#blueprints-fields-rules-layouts-and-boms__ul_a43_14v_5gc}

## Fields {#blueprints-fields-rules-layouts-and-boms__section_rjh_c4v_5gc}

Fields are attributes that capture data during configuration and transaction workflows.

* Transaction-level fields capture header data such as customer details, dates, or totals.
* Line-level fields appear in the transaction grid for products, pricing, and discounts.
* Field types include text, number, Boolean, picklist, and date/time.
* Some fields are system-provided. You can also create custom fields for your sales process.
{#blueprints-fields-rules-layouts-and-boms__ul_v5y_c4v_5gc}

## Rules {#blueprints-fields-rules-layouts-and-boms__section_el2_24v_5gc}

Rules automate logic and calculations. Each rule includes:

* Conditions that define when the rule should run.
* Actions that define what happens when conditions are met (set values, hide fields, filter picklist options, display messages).
* Rules that can run at transaction level or line level.

{#blueprints-fields-rules-layouts-and-boms__ul_mjb_34v_5gc}

You can group rules into rule groups and assign them to stages or events.

## Layouts {#blueprints-fields-rules-layouts-and-boms__section_ist_j4v_5gc}

Layouts define the user interface for the buyside experience. Layouts let you streamline the UI for different audiences while maintaining consistent logic. They specify:

* How transaction and line-level fields appear on the page
* Which fields or sections are visible for each stage or persona
* UI effects, such as messages or highlights triggered by rules
{#blueprints-fields-rules-layouts-and-boms__ul_fqp_l4v_5gc}

## BOMs {#blueprints-fields-rules-layouts-and-boms__section_l2x_lxx_5gc}

Bills of material (BOMs) translate configured data into structured outputs that integrate with downstream systems.

* Sales BOMs: Line items that pass into Salesforce for quoting.
* Manufacturing or custom BOMs: Detailed component structures exported to ERP or fulfillment systems.
* BOMs ensure that attribute-based configuration outputs map correctly into orderable and manufacturable items.
{#blueprints-fields-rules-layouts-and-boms__ul_wph_nxx_5gc}

## How components interact {#blueprints-fields-rules-layouts-and-boms__section_pnr_rxx_5gc}

* Blueprints bring together fields, rules, layouts, and BOM definitions into a complete model.
* Fields collect the data users provide.
* Rules validate input, enforce logic, and calculate outputs.
* Layouts deliver the tailored UI experience to users.
* BOMs package the result into line items for quoting and manufacturing.