--- sourceDocument: Australia Sales Customer Relationship Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/order-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia Sales Customer Relationship Management ft:clusterId : - omgmt bundleId : - omgmt workflow : - Customer and Industry --- # Events # Transaction events {#ariaid-title1} Release version: Australia 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 Transaction events Transaction events in ServiceNow Quote Experience enable automation and control over quote processing within ServiceNow CPQ. These events, triggered by buttons or API calls, facilitate transitioning quotes through stages, executing rule groups, invoking integrations, and managing quote lines and transactions. They improve user efficiency by automating common actions like creating, updating, cloning, and deleting transactions or lines, as well as repricing quotes. Show full answer Show less ## Key Features * **Header-level system events:** Standard transaction-level actions such as Create Transaction, Update Transaction, Copy Transaction, Upsert Lines (for adding or modifying lines), Reprice (for recalculating pricing), and Delete Transaction. * **Transaction line-level system events:** Actions on individual quote lines such as Clone Line, Delete Lines, and Reconfigure, accessible via buttons on the quote lines grid. * **Repricing events:** When pricing is enabled, manual repricing can be triggered by a button, while automatic repricing is attached by default to events like Upsert Lines. Repricing behavior can be customized per quote stage to optimize pricing logic. * **Event APIs:** Allow authorized API-based event triggers, but caution is advised to avoid simultaneous triggering from both UI and API on the same transaction to prevent unpredictable behavior. * **Validation setting:** Custom header events can include a Validate configured items option that checks product configurations before event actions execute, respecting a configurable validity period to avoid redundant validations. * **Custom events:** Customers can create custom transaction events to support specific business processes, enabling tailored rule groupings, integrations, and stage transitions. ## Practical Implications for ServiceNow Customers By leveraging transaction events, customers can streamline quote management workflows, automate pricing recalculations, and enforce business logic consistently across quotes. The ability to customize events and validation settings provides flexibility to align the quoting process with organizational needs. Understanding the interaction between events, pricing, and stages helps optimize performance and user experience. Customers should carefully design event API usage to avoid conflicts and ensure reliable quote processing. Events trigger rule groups, integrations, and stage transitions on a quote. ServiceNow Quote Experience provides system events and supports custom events in ServiceNow CPQ. Events are activated by buttons on the quote layout or by API calls, and typically help users transition quotes from one stage to another. When an event fires, it can run rule groupings, call integrations, and trigger stage transitions. ## Header-level system events {#quote-tm-events__system-events} System events are standard behaviors provided by default. When the ServiceNow Quote Experience is embedded in ServiceNow CPQ, the user sees buttons on the quote interface corresponding to transaction-level events. Transaction-level system events: Create Transaction : Triggered to create a new transaction. Update Transaction : Allows editing an updating a transaction. Copy Transaction : Clones a transaction and its line items. Upsert Lines : Manages the creation and update of transaction lines after the user browses the catalog to add new lines or reconfigures an existing line. Upsert Lines runs automatically after the user finishes selecting products from the catalog, configuring products, or reconfiguring a line. Although it works on lines, it operates at the transaction level on all lines. When pricing is enabled, this event ships with the Reprice action attached so that adding or reconfiguring a product automatically reprices the quote. For more information about UI effects, see [Quote transaction layouts](https://www.servicenow.com/docs/Lw416qa_lBBm7jF66xiaKA "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."). Reprice : Recalculates pricing for the quote by assembling the pricing context from the header and line values and calling the pricing service. The response is mapped back onto the quote and line pricing fields. Available when pricing is enabled for the deployment. The Reprice action can be attached to a button on the quote layout for manual repricing and to system events, such as Upsert Lines, for automatic repricing. Delete Transaction : Triggered to delete an existing transaction. Transaction line-level system events are represented as buttons on the quote lines grid: Clone Line : Clones a line and its children. Only top-level lines in the transaction can be cloned. Header-level rules also apply after cloning. Delete Lines : Deletes one or more selected lines from the transaction. Line IDs can also be passed in headless mode. Reconfigure : Re-configure one or more selected lines from the transaction. Line IDs can also be passed in headless mode. ## Repricing events {#quote-tm-events__pricing-events} When Pricing is enabled, the Reprice action drives both manual and automatic repricing. To enable Pricing, see [Set up an external connection in ServiceNow CPQ](https://www.servicenow.com/docs/5nbs~~fJgMfz3Rdq4pajaQ "Set up an external connection in ServiceNow CPQ by copying the client ID and client secret of the CPQ.ai Auth record.") * Manual reprice --- Attach the Reprice action to a button on the quote layout so users can recalculate pricing on demand. * Automatic reprice --- Default special-event triggers, such as upsertLines when a configuration is added, ship with the Reprice action attached, so pricing runs without the user selecting Reprice. You can disable these default triggers per event if you don't want automatic repricing for a given event. * Stage-aware behavior --- The effective repricing behavior can differ by stage without per-event configuration. For example, auto-pricing can be aggressive in an early stage such as Draft and suppressed in a later stage such as Order Submitted. Configure stage-specific behavior on the stage. For more information, see [Quote transaction stages](https://www.servicenow.com/docs/i2KkEP3U_1DGDFl_2xD4kA "Stages represent phases in the quoting process. Each stage can have entry criteria, rule group associations, and stage-specific layout behavior in ServiceNow CPQ."). {#quote-tm-events__ul_reprice_events} ## Event APIs {#quote-tm-events__event-apis} Event APIs are authorized via session cookie only. Warning: Avoid building a scenario in which the user initiates an event that fires an event API on the same transaction. Because both the quote interface and the APIs act on the same record simultaneously, such an implementation can result in unpredictable behavior. ## Event setting: Validate configured items {#quote-tm-events__event-settings-validate} The Validate configured items setting on custom header events validates product configurations in the transaction when the event executes. Validation occurs before event actions, which execute regardless of the validation outcome. The setting includes a validity period that excludes products validated within a specified time frame. For example, if the validity period is 15 days and a product was validated 7 days ago, that product is not revalidated. If a product was validated 20 days ago, it is revalidated. Two line-level system fields support this function: txn.line.configuration.status (Boolean) and txn.line.configuration.validatedAt (date). * **[Create an event](https://www.servicenow.com/docs/H7XgAkouCR9ZgYPqMziDiw)** Create a custom event in ServiceNow Quote Experience to trigger rule groupings, integrations, and stage transitions based on business-specific requirements in ServiceNow CPQ. **Related tasks** * [Create an event](https://www.servicenow.com/docs/H7XgAkouCR9ZgYPqMziDiw "Create a custom event in ServiceNow Quote Experience to trigger rule groupings, integrations, and stage transitions based on business-specific requirements in ServiceNow CPQ.")