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


---

# Layout elements

# Layout elements and hierarchy {#ariaid-title1}

Release version: Brazil  
Updated August 29, 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 Layout elements and hierarchy

Layouts in ServiceNow use a hierarchical structure consisting of pages, tabs, tiers (sections), column sets, and fields to organize configuration interfaces.
Understanding this hierarchy enables you to design effective and user-friendly layouts that suit your configuration needs, from simple forms to complex multi-page setups.
Show full answer Show less  

## Layout Structure and Element Definitions

* **Page:** The top-level container representing a distinct view navigable via tabs or buttons. Each page can hold multiple tabs and tiers.
* **Tab/Vertical Tab:** Secondary organizational elements within pages that let users switch between content groups without leaving the page. Tabs contain tiers and column sets.
* **Tier (Section):** Groups related fields and components. Tiers support different display types (e.g., accordion, expandable) and can be nested to create multi-level groupings.
* **Column Set:** Arranges fields, buttons, and images horizontally within tiers. Supports two modes:
  * **Responsive:** Default mode where fields wrap automatically, ideal for adaptable layouts.
  * **Defined Columns:** Fixed column structure for table-like layouts, allowing precise control over column widths and alignment.
* **Field:** Individual input or display elements (text inputs, dropdowns, checkboxes, etc.) tied to configuration attributes.
* **Button:** Action elements triggering events or navigation within the layout.
* **Heading:** Text labels or section titles used to organize and label content without interactive elements.

## Nesting Rules and Constraints

* A layout contains one or more pages.
* Pages contain tabs or tiers.
* Tabs contain tiers.
* Tiers contain column sets, nested tiers, or (Quote Experience only) a line item grid as a sole element.
* Column sets contain fields, buttons, or headings, stacked vertically if multiple column sets exist in the same tier.
* Line item grids must be the only element in their tier and cannot mix with column sets.

## Typical Layout Structures and Use Cases

* **Simple Layout:** Single tier with columns and fields for basic forms.
* **Multi-Section Layout:** Multiple tiers grouping related fields logically (e.g., General Info, Advanced Options).
* **Tabbed Layout:** Multiple tabs to reduce complexity and organize many options.
* **Complex Layout:** Multiple pages with nested tiers and defined column sets for multi-step configurations or product pickers.

## Choosing Between Responsive and Defined Column Sets

* **Responsive Column Sets:** Best for adaptable layouts that work well on various screen sizes, mobile-friendly forms, and minimal setup.
* **Defined Column Sets:** Suitable for fixed, table-like structures where precise column width and alignment control is needed, such as product grids or e-commerce interfaces.

## Layout Design Recommendations

* Group related fields into clearly labeled tiers to enhance logical organization.
* Use tabs to manage large numbers of fields and reduce cognitive load.
* Test layouts on different screen sizes to ensure usability, especially on mobile devices.
* Maintain consistent column alignment within tiers for visual clarity.
* Avoid overly deep nesting (more than 2--3 levels) to prevent confusion.  
Layouts use a hierarchical structure of organizational elements: pages, tabs, tiers (sections), column sets, and fields. Understanding how these elements nest and interact helps you design layouts.

## Layout hierarchy overview {#cpq-layout-elements__hierarchy-overview}

The layout element hierarchy from top to bottom is: Layout (root) → Pages (top-level sections) → Tabs or Tiers (organization within pages) → Column Sets (horizontal arrangement) → Fields and Buttons (data/actions)

Not all levels are required. For example, a simple layout may have only a page, a tier, a columnset, and fields. More complex layouts use multiple pages, tabs, and nested tiers to organize content.

## Element definitions {#cpq-layout-elements__element-definitions}

Page
:   The top-level organizational boundary within a layout. A page is a distinct view or section of the configuration interface. Users navigate between pages using page tabs or buttons. Each page can contain multiple tabs
    and tiers.

Tab and Vertical Tab
:   Secondary organization within a page. Tabs are displayed as a horizontal or vertical tab bar, allowing users to switch between different groups of content without leaving the page. Each tab can contain tiers and
    column sets.

Tier (Section)
:   A container element that groups related fields and components. Tiers can be configured with different representation types (for example, simple section, accordion, expandable container) to control how content is
    displayed and interacted with. Tiers can be nested within other tiers to create multi-level hierarchies.

Column Set
:   Arranges fields, buttons, and images horizontally within a tier. Column sets support two modes: Responsive (fields wrap automatically; default) and Defined Columns (fixed column structure, table-based layout).
    Multiple column sets in the same tier are stacked vertically. See [Defined column set reference](https://servicenow-prod.fluidtopics.net/FNDaiD_TVvEMDbz~0aFwPQ "Defined column sets organize fields in a fixed, table-based structure with explicit control over column count, width, alignment, and flow. Use them for structured layouts such as product pickers and e-commerce product grids.") for details on both modes.

Field
:   An individual data input or display element placed within a column set. Fields can be text inputs, dropdowns, radio buttons, checkboxes, or read-only text. Each field is associated with a configuration attribute or
    variable.

Button
:   An action element placed within a column set. Buttons trigger events or navigate users to other views (for example, a reconfigure button, a link to product picker, a validate button).

Heading
:   A text label or section title placed within a layout to organize and label content. Headings do not contain fields or interactive elements.

## Nesting rules and constraints {#cpq-layout-elements__nesting-rules}

The following rules govern how layout elements can be nested:

* Layout contains one or more Pages.
* Page contains one or more Tabs/Vertical Tabs or Tiers.
* Tab contains one or more Tiers.
* Tier can contain:
  * One or more Column Sets (most common), or
  * Nested Tiers, or
  * A Line Item Grid (Quote Experience only; must be the only element in the tier)
  {#cpq-layout-elements__ul_gqd_1fs_tkc}
* Column Set contains one or more Fields, Buttons, or Headings.
* Multiple Column Sets in the same Tier are arranged vertically (stacked).

{#cpq-layout-elements__ul_fqd_1fs_tkc}  
Important:  
A Line Item Grid (Quote Experience layouts only) must be the only element in its tier and cannot coexist with column sets or other elements in the same tier.

## Example layout structures {#cpq-layout-elements__example-layouts}

Simple Layout (No Pages or Tabs):

* Layout → Tier (Heading) → Column Set → Fields
* Use case: Basic configuration form with a single section.

{#cpq-layout-elements__ul_hqd_1fs_tkc}

Multi-Section Layout (Multiple Tiers):

* Layout → Tier 1 (General Info) → Column Set → Fields ↓ Tier 2 (Advanced Options) → Column Set → Fields ↓ Tier 3 (Summary) → Column Set → Fields
* Use case: Configuration with distinct logical groups (General, Advanced, Summary).

{#cpq-layout-elements__ul_iqd_1fs_tkc}

Tabbed Layout (Horizontal Organization):

* Layout → Tab: "Basic" → Tier → Column Set → Fields ↓ Tab: "Advanced" → Tier → Column Set → Fields
* Use case: Configuration with many options; tabs reduce cognitive load.

{#cpq-layout-elements__ul_jqd_1fs_tkc}

Complex Layout (Nested Tiers + Defined Columns):

* Layout → Page: "Config" → Tier (Accordion) → Tier (nested) → Defined Column Set (3 columns) → Fields ↓ Page: "Summary" → Tier → Responsive Column Set → Fields
* Use case: Multi-step configuration with product picker (defined columns) and summary view.
{#cpq-layout-elements__ul_kqd_1fs_tkc}

## Choosing between responsive and defined column sets {#cpq-layout-elements__column-set-choice}

Most layouts use responsive column sets, which are the default. Choose defined columns when:

* You need a fixed, table-based structure (for example, product grid, comparison table).
* You want to control column widths and alignment explicitly.
* You are designing an e-commerce or product picker interface.

{#cpq-layout-elements__ul_lqd_1fs_tkc}

Use responsive column sets when:

* You want the layout to adapt to various screen sizes (especially mobile).
* You are building standard forms or data entry interfaces.
* You want minimal configuration effort.

{#cpq-layout-elements__ul_mqd_1fs_tkc}

For a detailed comparison, see [Defined column set reference](https://servicenow-prod.fluidtopics.net/FNDaiD_TVvEMDbz~0aFwPQ "Defined column sets organize fields in a fixed, table-based structure with explicit control over column count, width, alignment, and flow. Use them for structured layouts such as product pickers and e-commerce product grids.").

## Layout design tips {#cpq-layout-elements__layout-design-tips}

* Organize logically: Group related fields into tiers with meaningful labels.
* Use tabs for many options: If a single tier contains too many fields, consider splitting them into tabs.
* Test responsive behavior: Resize your browser and test on mobile to ensure layouts are usable on small screens.
* Consistent alignment: Use consistent column structures within a tier to maintain visual coherence.
* Avoid deep nesting: While nesting tiers is allowed, avoid nesting more than 2--3 levels deep, as it can become confusing.
{#cpq-layout-elements__ul_nqd_1fs_tkc}
**Related concepts**   

* [Set up layouts](https://servicenow-prod.fluidtopics.net/LYjp9BqJPJlNdbxg12S2WA "Layouts in ServiceNow CPQ define the structure and appearance of the configuration interface. They organize fields into pages, tabs, and sections, shaping how users interact with configurations and view shopping cart details.")
* [Quote transaction layouts](https://servicenow-prod.fluidtopics.net/aqpxQxk6u2bSWbku7FolJQ "Layouts define the quote user interface in ServiceNow Quote Experience, controlling which fields, events, and UI effects are visible and how the quote is organized for users in ServiceNow CPQ.")  
**Related reference**   

* [Defined column set reference](https://servicenow-prod.fluidtopics.net/FNDaiD_TVvEMDbz~0aFwPQ "Defined column sets organize fields in a fixed, table-based structure with explicit control over column count, width, alignment, and flow. Use them for structured layouts such as product pickers and e-commerce product grids.")

