Transaction events

  • Release version: Australia
  • Updated May 7, 2026
  • 2 minutes to read
    • Summarize
    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 activate rule groups, integrations, and stage transitions, helping users efficiently manage quotes by triggering actions via interface buttons or API calls. They primarily facilitate moving quotes through different stages by automating standard and custom behaviors.

    Show full answer Show less

    Key Features

    • Header-level system events: Standard events that operate at the transaction (quote) level and are accessible through buttons on the quote interface:
      • Create Transaction: Initiates a new transaction.
      • Update Transaction: Enables editing of an existing transaction.
      • Copy Transaction: Clones a transaction along with its line items.
      • Upsert Lines: Automatically manages creation and updates of transaction lines after catalog browsing or product configuration, operating on all lines within the transaction.
      • Delete Transaction: Removes an existing transaction.
    • Transaction line-level system events: These events appear as buttons on the quote lines grid and act on individual or multiple lines:
      • Clone Line: Clones a top-level line and its children, applying header-level rules post-cloning.
      • Delete Lines: Deletes selected lines, with support for headless mode via line IDs.
      • Reconfigure: Allows reconfiguration of selected lines, also supporting headless mode.
    • Event APIs: Allow programmatic triggering of events secured via session cookies. It is important to avoid scenarios where both UI and API simultaneously act on the same transaction to prevent unpredictable outcomes.
    • Validation setting for custom events: The Validate configured items setting enables validation of product configurations before event actions execute. It respects a configurable validity period to prevent unnecessary revalidation of recently validated products, using system fields that track configuration status and validation timestamps.

    Practical Considerations for ServiceNow Customers

    • Use transaction and line-level events to automate and streamline quote management tasks such as creation, cloning, updating, deletion, and configuration.
    • Leverage the automatic Upsert Lines event to ensure transaction lines reflect the latest catalog selections and configurations without manual intervention.
    • Implement custom events with validation to maintain product configuration integrity before allowing quote progression.
    • Be cautious when combining UI-triggered events and API calls on the same record to avoid conflicts or erratic behavior.

    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 API calls on the quote layout and typically helpuserscan 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

    System events are standard behaviors provided by default. When Transaction Manager is embedded in Sales CRM, 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. For more information about UI effects, see Quote transaction layouts.
    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.

    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

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