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.
Quote and Order Creation in Version 252 vs. 254:
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.
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.
004333169

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.