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


---

# Using the sidebar

# Using the sidebar {#ariaid-title1}

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

Use the sidebar element to display persistent information---such as visualizations, product details, or alternate shopping carts---across tiers in a configuration. Define its position and content in the layout CSV to enhance
visibility and user experience throughout the configuration process.
In a layout, the sidebar element can be used to show persistent information to the end user across multiple tiers.


Hinweis:  
Currently, you cannot implement this feature using the CPQ layout editor. You must create the sidebar element in the layout CSV and then import the CSV file.

## Setup {#layout_sidebar__section_vbw_ytg_phc}

When setting up the sidebar, you must define the sidebar element as a child of the entire layout. The cells to fill in are below together with an example of the sidebar section of the CSV file.

* Type: sidebar
* Path: /layout/sidebar
* Value: `{"location":"right"}` or `{"location":"left"}`

{#layout_sidebar__ul_ysd_x2z_chc} {#layout_sidebar__table_wbw_ytg_phc__entry__6}

| type | path | label | variablename | component display type | value |
|-|-|-|-|-|-|
| sidebar | /layout/sidebar |   |   |   | `{"location":"right"}` |
| tierdef | /layout/sidebar/tiers |   |   | BasicContainer |   |
| tier | /layout/sidebar/tiers | Tier | tier |   |   |
[Tabelle : 1. Sidebar element]

{#layout_sidebar__table_wbw_ytg_phc}

The location property determines whether the sidebar appears to the user on the left or right of the screen. This is where the sidebar exists during configuration, and unlike the shopping cart's similar
property, it cannot be on the bottom of the configurator, nor can it be moved during configuration.

The child of the sidebar can only be a tierdef object. If you add a tier or a columnset element as a child, the layout fails. After a tierdef is defined in the CSV, you
can then add the necessary tiers, columnsets, and fields as children as in any other tier.

Only one sidebar can exist on a layout. Adding another will result in their being combined into the same tier upon deployment.

## Use case: 3D visualizer {#layout_sidebar___3d_visualizer}

The sidebar can host the 3D visualization tools an organization uses during configuration. As shown in the example above, any changes to fields that are tied to updating the visualization are shown to end users no matter the tier
they are currently on.

## Use case: product information {#layout_sidebar__product_information}


The sidebar can host anything from the product or quote using the system or partner fields that you would like to make available to the end user throughout the configuration process.

[Example CSV file](https://drive.google.com/file/d/1lXUD_rRKlUub7Airg21tvHQfBuH3AYZD/view?usp=sharing)

## Use case: shopping cart {#layout_sidebar__shopping_cart}


To show a product list other than the shopping cart to the end user, you can host it in the sidebar. This could be helpful if you need to list a separate manufacturing BOM type while only showing sales BOM types in the shopping
cart.

[Example CSV](https://drive.google.com/file/d/1uB6SjfiHTjff-cI54zdffaEf6bUzSuNy/view?usp=sharing)