Migrate Field Update logic from Workflow Rules and Process Builders to Price Rules, otherwise Field updates done with Workflow Rules and Process Builders may trigger re-calculations or may not consider fields injected if calculations depend on them.
Make sure to use the proper Calculator Evaluation Event and follow Best Practices when creating price rules and compatible formulas.
If more complex sequencing logic is necessary, there is also the option of creating a "Quote Calculator Plugin."
As of CPQ v28, Salesforce CPQ no longer develops new features for the Legacy Calculator. All pricing and calculation features released in CPQ v28 and subsequent versions are only available on the Advanced Calculator. Orgs wishing to take advantage of new features and improved response times in the Quote Line Editor must switch to using the Advanced Calculator.
The Legacy Calculator (if "Use Legacy Calculator" is TRUE in the Installed Package settings for Salesforce CPQ) runs calculations in Apex. Some organizations use Workflow Rules and Process Builders to update Quote Line fields on Quote Line creation with the Legacy Calculator. This was supported in some instances as the Quote Line record was created once saving from Product Selection/Configuration.
The Advanced Calculator runs in Javascript and calls out to Heroku to run calculations of Quote Line data. On the Advanced Calculator Quote Line Data exists "in memory" when added from Product Selection/Configuration until a "Save" or "Quick Save" happens in the Quote Line Editor, which then saves it to the database. As such, Workflow Rules and Process Builders will fire upon saving to the database which is after the full calculation sequence.
Best Practice with Field Updates from Workflow Rules and Process Builders on Quote Lines or Quote level fields in the "Calculating Fields" Field Set (instances where a re-calculation may be triggered) is to migrate the logic to Price Rules so they can be sequenced to run smoothly with the Advanced Calculator.
Also note that Formulas used in Price Rule's Conditions/Actions need to be reviewed to be compatible with the Advanced Calculator.
Consult this document for further Price Rule Considerations
Finally, if your organization is upgrading from a version that didn't have the Advanced Calculator to a version that does, create the following picklist values for "Calculator Evaluation Event" on the Price Rule object
As well as the following field on the Price Condition object's "Filter Type"
NOTE: The Legacy Calculator assumes the picklist value "Value" if Filter Type is null. Filter Type requires a value for Price Rules to fire on the Advanced Calculator.
000383083

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.