Price Rule - Configurator vs Calculator - on Evaluation Scope - Answers - Salesforce Trailblazer Community
Trailblazer Community
Ask Search:
Ricardo Furlan de AzevedoRicardo Furlan de Azevedo 

Price Rule - Configurator vs Calculator - on Evaluation Scope

Hello,

When configuring a Price Rule I can´t find an explanation when it is necessary to use Configurator or Calculator, on Evaluation Scope.
What´s the difference between both?

Thanks in advance!
Best Answer chosen by Ricardo Furlan de Azevedo
Deep SinghDeep Singh
Hi Ricardo,

Configurator Evaluation Events
1. A price rule’s configurator evaluation event determines when Salesforce CPQ applies the price rule to its target. You can change the evaluation event based on when you want sales reps to see the price rule’s results.

2. The price rule’s configurator evaluation event has three values.
None: Salesforce CPQ applies the price rule after the user clicks Save and then leaves the configurator.
Save: Salesforce CPQ applies the price rule after the user clicks Save in the configurator.
Edit: Salesforce CPQ applies the price rule immediately after the user navigates out of a changing field that the price rule is covering when the Apply Immediately field in the product option is active.

3. for example - Refer to this example (https://help.salesforce.com/articleView?id=cpq_config_pr_examples.htm&type=5) Your company sells an enterprise server management bundle for $6,000 each. However, you want to reduce its price to $5,000 when one of its product options, and admin training license, reaches a quantity of 2.   

Calculator Evaluation Events
1. If a price rule has a calculator evaluation event of On Initialization, Salesforce CPQ runs the rule before calculating the rule’s formula fields. If your On Initialization rule contains a formula field that requires a specific value, you might run into an error. Price conditions and actions load related records and evaluate formula fields following After Calculate rules and plugin methods. Any Block Price, Discount Tier, or Term Discount relationship in formula contains an incorrect record. You can still reference Block Price, Discount Tier, and Term Discount in a formula field, but don’t reference those relationships in the formula itself.

2. Salesforce CPQ doesn’t support On Initialization, Before Calculate, or On Calculate formulas that reference the Prorate Multiplier field or any unit price other than the List Price field. The values of those fields aren’t accurate until after the rule event’s completion.

3. Salesforce CPQ doesn’t support On Initialization, Before Calculate, or On Calculate formulas that reference total price fields other than component totals and package totals. Noncomponent and non-package totals get their values following calculation, so a price rule can’t reference them during the first calculation sequence.

Thanks!