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


---

# Fields

# Quote transaction fields {#ariaid-title1}

Release version: Brazil  
Updated May 7, 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 Quote transaction fields

ServiceNow Quote Experience enables administrators to create and manage fields at two levels---transaction (header) and transaction line---to capture all necessary quote data within ServiceNow CPQ.
Transaction-level fields capture deal-wide information, while transaction line-level fields handle product and pricing details.
The level at which a field is created determines its availability in rules that operate at the corresponding level.
Show full answer Show less  

## Field Levels

* **Transaction level (header):** Fields outside the quote lines grid for overall deal data such as account info, total pricing, and discounts.
* **Transaction line level:** Fields within the quote lines grid, shown as columns or in the Line Details UI, for product-specific data.

## Field Types and Key Attributes

Supported field types at both levels include Text, Number, Boolean, Picklist, and Date/Time. Each field type comes with configurable attributes to ensure data quality and usability:

* **Text:** Free-form text with configurable minimum and maximum length constraints.
* **Number:** Numeric values supporting Integer, Decimal, and Currency types with value range validations.
* **Boolean:** True/false values shown as checkboxes or toggles, customizable labels, and default states.
* **Picklist:** Single or multi-select lists with customizable options, ordering, default selections, and comparison modes (Text or Number) for sorting and processing.
* **Date/Time:** Stores UTC date and time with default values and constraints to enforce business rules such as valid quote periods.

All fields include standard attributes like display name, unique system identifier, default value, requirement toggle, and access control settings (editable, read-only, or hidden) to manage user permissions effectively.

## System-Provided and Custom Fields

ServiceNow Quote Experience offers predefined system fields at both transaction and transaction line levels, covering pricing, opportunity, product, and order information for streamlined transaction processing.

Administrators can also add custom fields via the administration interface, associating them automatically with blueprints and enabling integration with platform capabilities such as Approvals, PDF generation, and Order Creation. Custom fields must sync through ServiceNow CPQ Microservices to the platform.

## Practical Benefits for ServiceNow Customers

* Create comprehensive, rule-aware fields tailored to your quoting process at both deal and product levels.
* Enforce data quality and business logic through configurable constraints, validations, and access controls.
* Leverage system fields for common transaction data while extending functionality with custom fields when needed.
* Ensure consistent and accurate quote data capture that integrates with other platform capabilities and workflows.  
ServiceNow Quote Experience supports five field types at two levels ---transaction (header) and transaction line ---enabling administrators to capture all required quote data in ServiceNow CPQ.

Fields in ServiceNow Quote Experience store data on a quote. Administrators create fields at the transaction level for deal-level data and at the transaction line level for product and pricing data. The level at which a field is
created affects its availability in rules, which also operate at transaction or transaction line level.

## Field levels {#quote-tm-fields__field-levels}

{#quote-tm-fields__table_mwg_ldp_hjc__entry__2}

| Field level | Description |
|-|-|
| Transaction level (header) | Transaction-level fields sit outside the quote lines grid. They capture information about the deal as a whole, such as account, addresses, list price total, total discount, and net total. |
| Transaction line level | Transaction line-level fields sit in the quote lines grid. They can appear as column fields or as fields in the Line Details UI Effect. |
[Table 1. Field levels]

{#quote-tm-fields__table_mwg_ldp_hjc}

## Field types {#quote-tm-fields__field-types}

ServiceNow Quote Experience supports the following field types at both levels.

Every field, regardless of type, includes these standard attributes and settings:

* Field name --- Display label that appears in the user interface
* Variable name --- Unique system identifier for the field, locked after creation (select a descriptive name that does not require changes later)
* Default value --- Value that automatically populates when a new transaction is created
* Required --- Toggle that enforces validation so users must provide a value before proceeding
* Access Control --- Settings that determine user permissions:
  * Editable --- Users can view and modify the field
  * Read-only --- Users can view but cannot modify the field
  * No Access --- Field is hidden from users
  {#quote-tm-fields__ul_wmb_13c_vjc}

{#quote-tm-fields__ul_vmb_13c_vjc}

For details on configuring access control rules for different user groups, see [ServiceNow Quote Experience: Access Control](https://servicenow-prod.fluidtopics.net/VTRQJsdYSG7pJNhC_nUBgQ "ServiceNow Quote Experience controls access at two levels: record access, which determines who can view or modify a quote, and field access, which controls the fields a user sees within a quote. Record access can be managed by your CRM or natively within ServiceNow Quote Experience.").
{#quote-tm-fields__table_nwg_ldp_hjc__entry__2}

| Field type | Description |
|-|-|
| Text | Stores free-form text input, such as names, descriptions, or open-ended responses. Text fields support configurable length constraints---administrators can set a minimum character length to ensure users enter sufficient detail and a maximum character length to prevent long entries. |
| Number | Stores numeric values for quantities, amounts, or calculations. Number fields support three distinct types: Integer (whole numbers only), Decimal (numbers with decimal places), and Currency (numbers formatted as currency). Supports configurable minimum and maximum value constraints to validate that users enter data within acceptable ranges. |
| Boolean | Stores a true or false value, typically displayed as a check box or toggle switch. You can customize the labels for each state---for example, "Yes/No," "Enabled/Disabled," or "Active/Inactive"---to match your business terminology. You can set a default checked state so the field comes pre-checked or unchecked when a transaction is created. |
| Picklist | Stores a single selected value or multiple selected values from a defined list of options, depending on the configuration mode selected. When defining picklist options, you control the order in which they appear. You assign a label (the user-facing name) and value (the system identifier). You can designate a default selection, provide an optional description, and include an optional image URL to visually represent the option. Picklist fields support a comparison type setting---select Text to compare options as text strings or Number to compare them numerically. This setting affects how the system processes and sorts picklist selections. |
| Date/Time | Stores both date and time values in UTC format (YYYY-MM-DDTHH:MM:SSZ) to ensure consistency across time zones. You can set a default date/time value that pre-fills when a transaction is created. The Not Before and Not After constraints restrict the date/time range users can select. These constraints enforce business rules such as "quotes cannot be created for dates in the past" or "expiration dates must be within 30 days." For detailed guidance on date and time field configuration and best practices, see [Date and time field fields](https://servicenow-prod.fluidtopics.net/MIxx4GTRKi_8bo_5CBiN3w "Reference for how date and time fields behave in ServiceNow CPQ ServiceNow Quote Experience rules and scripts, including comparison operators, null handling, and supported aggregate functions."). |
[Table 2. Field types]

{#quote-tm-fields__table_nwg_ldp_hjc}

## System-provided fields {#quote-tm-fields__system-provided-fields}

ServiceNow Quote Experience provides a set of system-provided fields at both levels that are commonly used in transaction processing.

Transaction-level system fields cover the following categories: pricing information, opportunity information, transaction information, and account information. For a complete list, see [Transaction-level system fields](https://servicenow-prod.fluidtopics.net/9wbXYZ7VNlWrnd~Xh1mHGg "Reference for the system-provided fields at the transaction (header) level in Quote Experience, including variable names, descriptions, who can modify each field, and default values.").

Transaction line-level system fields cover the following categories: pricing information, transaction line information, configuration information, product information, and order information. For a complete list, see [Transaction line-level system fields](https://servicenow-prod.fluidtopics.net/Seex3n5T432D7CxXMWuQ6w "Reference for the system-provided fields at the transaction line level in ServiceNow CPQ ServiceNow Quote Experience, including variable names, descriptions, who can modify each field, and default values.").

## Custom fields {#quote-tm-fields__custom-fields}

Custom fields can be added to a blueprint through the ServiceNow Quote Experience administration interface. Fields created through the interface are automatically associated with the blueprint.

Custom transaction fields can be created for platform capabilities such as Approvals, PDF Document Generation, or Order Creation. The field must sync from the ServiceNow CPQ Microservices to the Platform. For more information, see [Configure transaction-to-quote field mapping](https://servicenow-prod.fluidtopics.net/DjlsvCH1gy0rJqK2Vf5TIw "When you use Sales CRM capabilities such as opportunity management, advanced approvals, or PDF document generation, ServiceNow CPQ Microservices sync data to the ServiceNow platform. This sync is set up automatically, but custom transaction fields require you to configure the data mapping.").
**Related tasks**   

* [Create a transaction field](https://servicenow-prod.fluidtopics.net/S_5PvHHNqoojLZp~mGILFg "Create a custom field in ServiceNow Quote Experience to capture additional data at the transaction (header) level or the transaction line level in ServiceNow CPQ.")  
**Related reference**   

* [Transaction-level system fields](https://servicenow-prod.fluidtopics.net/9wbXYZ7VNlWrnd~Xh1mHGg "Reference for the system-provided fields at the transaction (header) level in Quote Experience, including variable names, descriptions, who can modify each field, and default values.")
* [Transaction line-level system fields](https://servicenow-prod.fluidtopics.net/Seex3n5T432D7CxXMWuQ6w "Reference for the system-provided fields at the transaction line level in ServiceNow CPQ ServiceNow Quote Experience, including variable names, descriptions, who can modify each field, and default values.")
* [Date and time field fields](https://servicenow-prod.fluidtopics.net/MIxx4GTRKi_8bo_5CBiN3w "Reference for how date and time fields behave in ServiceNow CPQ ServiceNow Quote Experience rules and scripts, including comparison operators, null handling, and supported aggregate functions.")

