Product Rules in Salesforce CPQ are used to enforce logic during product configuration.

Salesforce CPQ Product Rules are configuration logic tools used to manage product selection
and validation within a quote. They ensure that the correct products are included in a quote.

Types of Product Rules

1. Validation Rules: When the conditions are not met, an error message is displayed, and
the users can’t continue until the situation is fixed. So, they act as a hard stop.
2. Selection Rules: can add, remove, show, hide, enable, or disable or perform some
combination of these actions on product options within a bundle or they can add a
product to a quote. This rule can be a great way to leverage Guided Selling to guide your
reps to the appropriate or most desired options by automatically selecting the right
products.
3. Filter Rules: Filter Rules are used in bundles to pull in product options from the product
catalog using a filter rule. This is often referred to as creating a dynamic bundle.
4. Alert Rules: •Alert Rules are a soft stop as compared to the Validation Rules’ hard stop.
They also display a message, but it’s more as a suggestion because the user can
proceed without meeting the specified business requirements.

Basic Steps to Create Product Rules:

1. Set up a product rule.

2. Set up error condition(s).
3. Set up action(s).
4. Set up a configuration rule.

What are the key components of a Product Rule in Salesforce CPQ?

The key components of a Product Rule in Salesforce CPQ include:
Product Rule: The main logic container that defines the rule’s type, conditions, and actions.
Error Conditions: Conditions that trigger the rule based on specific criteria, such as product
attributes or configuration attributes.
Product Actions: Actions that are taken when the rule is triggered, such as adding, removing,
showing, or hiding products.
Configuration Rule: Links the Product Rule to specific products or bundles, specifying where
and when the rule should apply.
To Create a Product Rule.

A. Product Rule Name- use a meaningful name that would make sense for you or anyone
reading it.

B. Active checkbox - check it to indicate that the rule is active.

C. Type- there are 4 types of rules: Alert, validation, Selection and Filter.

D. Conditions Met - there are 3 options here:

● All: Choose this option if all conditions must be met in order to trigger this rule (AND).
● Any: Choose this option if a single condition must be met in order to trigger this rule
(OR).
● Custom: This is a combination of AND/OR.

E. Scope - indicates whether the rule applies to:

● the entire quote (visible on Quote Line Editor) or
● a specific product (visible during configuration).
F. Evaluation Event - The Evaluation Event is to control when and how the Product Rule is
applied.:
● Load: The Product Rule is evaluated when the product configuration page is loaded..
● Edit: The Product Rule is evaluated whenever the user makes changes
(add/remove/modify) in the product configuration...
● Save: The Product Rule is evaluated when the user attempts to save the configuration
or quote..
● Always: The Product Rule is continuously evaluated during the product configuration
process.

G. Message - enter the message that will appear to users when an Alert Rule or a Validation
Rule is triggered.

H. Evaluation Order: In our Org have 100 active Product Rules are there, it will define Order of
Product Rules.

The scope has 2 options

1. Product and
2. Quote.

If we Select Scope is Product, the Product rule will fire on the QLE Configurations Products
Page.

Once we add the Product and click on Apply rules and click on Save, the product rule will
fire.

If we Select Scope is Quote, the Product rule will fire on QLE Quote Edit Page.

This Edit Quote Page, Product Rule will fire.

How do you set up a Validation Rule for a Product Bundle in Salesforce CPQ?
To set up a Validation Rule for a Product Bundle:
- Define a Product Rule with the type "Validation."
- Specify the conditions under Error Conditions, such as ensuring a warranty does
not exceed the number of products.
- Define the message that will be displayed when the condition is not met.
- Link the Product Rule to the specific bundle using a Configuration Rule to ensure the
rule applies within the bundle context.

What is the function of the “Scope” field in a product rule?

The “Scope” field in a product rule determines where the rule is applied within the Salesforce
CPQ process.
It can be set to either “Product” or “Quote”:
•Product Scope: The rule applies during the product configuration process, affecting the
selection of products and options within a bundle.
•Quote Scope: The rule applies at the Quote Line Editor stage, impacting the overall quote,
such as pricing and discount applications.
Example: For Dell, a rule with a “Product” scope might ensure that only compatible hardware
components are selected when configuring a server bundle. A “Quote” scope rule might ensure
that discounts are applied only to certain product lines or customer types.

How do Error Conditions work within a Product Rule, and what is their function in this
scenario?

Error Conditions within a Product Rule define the specific criteria that trigger the rule’s actions,
such as displaying an error message.

In this scenario, the Error Condition checks if the Summary Variable for Product B’s total
quantity is less than the Summary Variable for Product A’s total quantity. If this condition is met,
the rule fires, and the system prevents the user from saving the configuration until the condition
is resolved.

Q Can Product Rules and Option Constraints be used together, and if so, how?
Yes, Product Rules and Option Constraints can be used together in Salesforce CPQ to create a
more comprehensive configuration experience. For example, Option Constraints can handle
straightforward dependencies and exclusions with real-time feedback, while Product Rules can
manage more complex scenarios like dynamic product selection, validations, and conditional
actions.

How do actions function within product rules?

Actions within product rules specify the changes that Salesforce CPQ should make when a
rule is triggered. These can include adding, removing, enabling, disabling, or filtering
products within a quote or bundle configuration.
Example:
For a desktop bundle, an action could automatically add a specific model of Dell monitor when
a corresponding desktop computer is selected, ensuring that customers receive a complete
system setup.

What is the purpose of Selection Rules in Salesforce CPQ, and how do they enhance
user experience?
Selection Rules automatically manage product options within a configuration. They can add,
remove, show, hide, enable, or disable product options based on specified criteria.
This automation streamlines the configuration process, ensures users select compatible
products and reduces the likelihood of errors.
For instance, if a user selects a specific carrier, the rule can automatically add relevant service
plans while removing incompatible ones.

Example: Selection Rule: If the Country is the USA, I want to disable the Intel I9 Product
Option.

Create an Error Condition.

In my Error Condition I need to check with my Configuration attribute, right? In that
Configuration Attribute we created Country and define some country values.

Save the Error Condition.

Now create an Action

Now create a Configuration Rule in Product Rule.

In this Configuration Rule we can select the Product to applied this Selection Product Rule.
What considerations should be taken into account when setting the Option Selection
Method to ‘Dynamic’?
When setting the Option Selection Method to ‘Dynamic,’ it’s important to set up a Salesforce
CPQ Filter Product Rule.
This rule pre-filters the list of products available for selection, streamlining the process for users
by only showing relevant options.

How is a Configuration Rule related to a Product Rule?

A Configuration Rule links a Product Rule to specific product bundles or configurations,

ensuring that the rule is applied in the appropriate context. This association allows for targeted
rule application within certain products or scenarios.
They may be used in Lookup Queries or Error Conditions to dynamically adjust the rule’s logic
based on user input or other factors.

What are configuration attributes and how are they used in product rules?
Configuration attributes are fields that sales reps can set during the product configuration
process. They can be used in error conditions to determine whether a product rule should
trigger, often based on selections or inputs made by the sales rep.
Example: A configuration attribute might be “Operating System Preference,” where the choice
between Windows and Linux triggers different sets of compatible software options and
warranties.

We have another option to apply the changes immediately without clicking the
Apply Rule button.

Go to Country Configuration Attribute -> check on the Apply Immediately field

46. Why should we use product rule validation of Salesforce CPQ when
validation rule in Salesforce is already present?
Product Rule Validation in Salesforce CPQ and traditional Salesforce Validation Rules serve
different purposes and are used in different contexts.

Product Rule Validation:

Is specifically designed for use within the Salesforce CPQ (Configure, Price, Quote)
environment. It allows for validation of complex product configurations, ensuring that
sales reps configure products correctly within the context of a quote or order.

For example, it can prevent incompatible product combinations or ensure required

components are included in a bundle.
It can provide immediate feedback during the product configuration process, as it is integrated
into the CPQ workflow. This is particularly useful for complex product setups where certain
configurations are not allowed or require additional products to function correctly.

Salesforce Validation Rules:

 Are more general and can be applied to any Salesforce object. The are triggered when a
record is saved.