Loading

Migration to the Place Sales Transaction API

Fecha de publicación: Apr 7, 2026
Descripción

Overview

In 254 API updates, the transition from "double persistence" to "single persistence" has led to performance improvements in transaction management. In the PlaceQuote and PlaceOrder APIs, the transaction management process previously involved a sequence of four steps; Config, Persist, Price, Persist. This process required two distinct persistence operations, contributing to longer response times.

With the introduction of the PlaceSalesTransaction (PST) API in version 254, persistence is now executed only once, now following a sequence of three steps: Config, Price, Persist. This shift from "double persist" to "single persist" has resulted in a 30% average improvement in API response times.

Key Changes and Impact

  • Quote and Order Creation in Version 252 vs. 254:

    • In version 252, quotes and orders were created using the PlaceQuote API or PlaceOrder API.
    • With the release of version 254, quotes and orders created through the Revenue Cloud experience layer are now handled via the PlaceSalesTransaction API, consolidating the API management process.
  • Performance Gains: The primary benefit of the transition is the reduction in persistence operations from two to one. This change not only boosts the overall system performance but also enhances API response times for end users, improving their experience with faster transactions.

Considerations for Existing Customers

  • Apex Logic Dependency: Customers who have custom Apex logic relying on the first persistence event may experience changes in price calculation results, particularly if the logic is designed to be price-impacting. This may require adjustments to ensure that the revised API behavior aligns with existing business processes.

  • Formula Fields and Context Attributes: For customers utilizing formula fields that are mapped to context attributes through sObject, price-impacting calculations may be impacted as a result of the change in persistence behavior. It is important to assess the potential impact on price calculations and make necessary adjustments.

Solución

Workaround

  • For pricing logic that can be managed through configuration, it is recommended to migrate the logic from apex to pricing procedures or migrate configuration rules to the pricing procedure. This approach allows for continued flexibility and pricing automation while aligning with the updated API processes.
  • If the pricing logic involves Salesforce triggers to populate or modify additional or existing data, it is important to review the usage patterns and explore the possibility of refactoring these triggers into pricing procedures for long-term support and performance.
  • If the logic cannot be migrated, a case can be opened with support.
Número del artículo de conocimiento

004333169

 
Cargando
Salesforce Help | Article