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


---

# Transaction Manager

# Transaction Manager {#ariaid-title1}

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

Set up, govern, and troubleshoot Transaction Manager so sales teams can capture non-configuration commercial data---such as contacts, addresses, quotes, discounts, and presentation options---alongside CPQ configuration outcomes.  
As a transaction administrator, you can

* Access stages, associated fields, related rules, rule groups, events, layouts, views, and personas.
* Decide the sales workflow stages you need and what must be true to enter each stage (entry criteria).
* Identify transaction-level (header) fields and transaction-line fields you'll capture.
* Enable these optional pilots:
  * Transaction Converse for natural-language line-item operations
  * Cosmo SmartPredict for in-context predictive recommendations
  {#transaction-manager__ul_hyb_1nv_5gc}
{#transaction-manager__ul_udp_dnv_5gc}

## How Transaction Manager is organized {#transaction-manager__section_h13_knv_5gc}

In Admin, choose the transaction context in the top navigation. The left menu exposes Transaction Manager admin areas (stages, associated fields, related rules, rule groups, events, layouts, views, and personas). The main work area
changes based on the entity you're editing.  
Core building blocks and relationships include:

* Stages that structure the sales process. Each stage may have entry criteria and can invoke rule groups and events. A transaction is in one stage at a time.
* Fields that store data. Use transaction-level (header) fields for deal metadata and line-level fields for the grid of items and pricing.
* Rules that evaluate conditions and perform actions such as hiding, messages, including or excluding picklist values, and setting or clearing values. Use rule groups to bundle rules and attach them to stages and events.
* Events such as buttons and API triggers that can run rule groups and drive stage transitions.
* Layouts and UI effects that define the buyside experience.
* Views and personas that tailor the layouts and fields that appear for a particular audience or stage.  
  Hinweis:  
  Favor many simple, non-scripted rules; the rules engine can evaluate tens of thousands quickly and automatically optimizes their order. To keep the UI responsive, avoid scripting where you can.
{#transaction-manager__ul_pwq_jnv_5gc}
**Zugehörige Konzepte**   

* [Installing the Salesforce Transaction Manager Integration Package extension](https://servicenow-prod.fluidtopics.net/ng2ZdQis_4~tpCvq8LDJ2g "To use Transaction Manager with Salesforce, you must first follow these steps to install and configure the Salesforce Transaction Manager Integration Package Extension.")