An Overview of Product Rules

by Community Manager on ‎07-21-2015 05:47 PM - edited on ‎04-25-2017 03:57 PM by Community Manager

OVERVIEW

Product Rules evaluate a Quote's Products against user-made conditions and then display a message in the Quote Line Editor if conditions aren't met.


Product rules contain a condition to meet, an error message (to display if the condition is not meet), and a filter. Users create Error Conditions to determine if a certain set of products is valid in a given scenario. The Error Conditions will use Summary Variables to make these decisions.

 

Product rules have 4 varieties:

  • Validation Rules check the quote line items and verify that there are no invalid products. Set the Scope of your product rule to "Quote" when building a quote product rule.
  • Configuration Rules check the product and its components to prevent invalid product options from being selected on a product bundle. Set the Scope of your product rule to "Product" to build a product configuration rule. Make sure you select the product bundle in the Configuration Rules related list.
  • Filter Rules are used with Dynamic Product Bundles to allow you to pre-filter the products that are available for your sales reps to add dynamically to a bundle. 
  • Alert Rules can be used as guidance or informational messages to your sales reps during configuration or pricing.  Unlike a validation rule, they allow reps to continue on and save their configurations and quotes without performing a corrective action.  

The major difference between Validation and Selection rules is that Selection rules can be used for specific products whereas Validation Rules can be used for fields on specific objects. 

 

KEY CONCEPTS AND DEFINITIONS

Common Product Rule Types Description
Dependency Product A is required with Product B
Complex Dependency Product A is required with multiple products
Exclusion Product A cannot be sold with Product B
Quantity-Based Constraints Quantity of Product A cannot be higher/lower than quantity of Product B
Prior Purchase Constraints Cannot purchase Product A without having previously purchased Product B

 

DETAILS

Product Rule Fields 

Fields

Description

Product Rule Name Name of the Product Rule.  It is best to enter a meaningful name here to make it easier to distinguish between any other rules you may have.
Conditions Met

Choose how to apply the Error Conditions:

  • All: All conditions must evaluate to "True" for the rule to fire. 
  • Any: Only one condition must evaluate to "True" for the rule to fire. 
  • Custom: Use with Advanced Conditions field to determine how conditions are evaluated.  For example, this enables a rule with 3 conditions to be handled in the following fashion: 1 AND (2 OR 3).  
Scope

Choose where the rule will be applied:

  • Product: Rule will be used within a product bundle. 
  • Quote: Rule will fire in the Quote Line Editor.
Evaluation Event Choose an Evaluation Event:
  1. Load: The rule will be evaluated when the configuration page loads.
  2. Edit: The rule will be evaluated when and a user selects or deselects an option on the configuration page. This event also provides real-time processing if the selected or deselected option, or configuration attribute, is flagged as 'Apply Immediately'.
  3. Save: The rule will be evaluated when the user clicks Save on the configuration page.
  4. Always: The rule is evaluated on page load, after changes are made, and upon save. Use this option when creating Real-Time Product Rules.
Type Choose Selection for Selection, Remove, and Hiding Rules.
Active Activate Rule before testing
Message An Error Message is required for 'Validation' type rules. This message will inform the user of any errors in their current configuration.
Evaluation Order This field is used to determine the order in which the product rules fire.
Advanced Conditon

Used to apply logic to the created conditions.

 

Error Condition fields

Field

Description

Index Assign a unique number to this Condition to reference it in the Advanced Condition field.
Rule Name of the product rule the error condition is related to. This is a lookup field and is pre-populated to the current rule by default. 
Tested Object

If you are evaluating a field on an object, select that object here.  You can choose from Quote, Quote Line, Quote Line Group, Product Option, Configuration Attribute, or Upgraded Asset. 

 

Note: Quote Line Group is available as a Tested Object value of Salesforce CPQ Winter 27. Review 

Validation Rules and Configuration Rules for sample Use Cases where Error Conditions test against Quote Line Groups.

Tested Field Select the field being evaluated if applicable.  This is a dependent picklist and will be populated with available fields related to the Tested object. 
Tested Variable If evaluating a summary variable and not a field, enter or lookup the summary variable in this field.
Operator Choose operator for condition.  You may need to add picklist values to the menu for the following:  not equals, less than, less or equals, greater than, greater or equals, starts with, ends with, and contains.  
Filter Type

Choose:

  • Value: to evaluate against a specified value. 
  • Variable: to evaluation against a Summary Variable. 
Filter Value Enter value you are comparing against.
Filter Variable Enter or lookup to the summary variable you are comparing against.

 

USE CASE: REAL-TIME RULE PROCESSING

Admins can configure Product Rules to automatically disable/enable or select/deselect product options based on other option selections and configuration attributes. This means the sales user will receive immediate feedback about valid and invalid options instead of receiving it only when they save the configuration.

 

This feature is useful for setting up a guided configuration: You can create configuration attributes in the form of questions; based on the response from the user, the system can automatically create the appropriate configuration, perhaps by auto-selecting multiple options in one step. 

 

To create a Product Rule that will function in real-time:

  1. Select a Product Bundle.
  2. Select a Product Option.
  3. Select Apply Immediately.
  4. Select System, if it is not already checked. This will remove the ability for the user to manually select the option. It is selected by either another option or a configuration attribute.
  5. Click the Product Rules tab.
  6. Click New.
  7. Enter the following fields with these values:
    1. Type: Selection
    2. Scope: Product
    3. Evaluation Event: Always. Note: you can select any value for Evaluation Event, it is not restricted to Always.
  8. Create a Product Action.

For instance, admins could create a Product Rule that adds a Product to a bundle based on where the quoted equipment is being shipped.

 

Tip: Wondering why a Rule isn't working? Check your Option Constraints. Remember, Option Constraints override Product Rules!

Note: Administrators can comma-separate values in the Target Field when using the "equals" operator, in order to check for multiple values with 1 Error Condition when creating a Product Rule. Do NOT include a space after each comma because the Search will be performed on a value that includes the space and therefore fail.

Caution: The "Object" in Error Conditions should not be specified when testing a Summary Variable, or it will not work.