A Configuration Rule is a feature that operates within a Product Rule. This feature allows you to establish conditions that will automatically select (add), deselect (remove), enable, disable, enable & add, or disable & remove options in a bundle. When used within a Product Rule of the Selection Type, Configuration Rules will save some clicks and provide immediate feedback to the sales user when the “Apply Immediately” field is selected on product options and configuration attributes.
The conditions are able to use summary variables, formulas or plain values.
Configuration Selection Rules are established by setting the Type field of a Product Rule to Selection, then creating Product Actions and Configuration Rules as needed:
Product Action Standard Fields:
|Rule||Name of the product rule the product action is related to.|
|Type||Declare the behavior of this action|
|Product||Select the product that this action should manipulate within configuration when the conditions are met|
|Required||Select this field for product selection rules.|
When the parent Product Rule Type is set to Selection, the following field values will become available for the Type picklist field on the Product Action page:
|Add||Within configuration, this will select the specified product.|
|Remove||Within configuration, this will deselect the specified product.|
|Enable||Within configuration, if a product is disabled (check box is not selectable), this will enable the checkbox so it is selectable by the user.|
|Disable||Within configuration, this disables a product so it is no longer selectable.|
|Enable and Add||Within configuration, this will enable a product and auto select it.|
|Disable and Remove||Within configuration, this will deselect a product and disable it from being selected.|
|Show||Within configuration, this will display products that are originally hidden.|
|Hide||Within configuration, this will prevent products from displaying.|
|Show and Add||Within configuration, this will display the product and auto-select it.|
|Remove and Hide||Within configuration, this will deselect a product and hide it from the view.|
Configuration Rule Fields
|Active||Indicates whether this rule should be used in evaluating configurations|
|Product||Select the configured Product you want this rule to validate|
|Product Rule||Select the Product Rule that contains the logic to validate your product configurations. Your configuration rule will have a lookup relation with this Product Rule.|
|Product Feature||For Dynamic Bundles, select the Product Feature you where the filter rule should run|
|Ascending Nested Condition Level||Include ancestor options to the specified level when evaluating this rule's conditions in the configurator. For more information on this and the two fields below, please review Selection Rules in Nested Bundles.|
|Descending Nested Condition Level||Include descendant options to the specified level when evaluating this rule's conditions in the configurator.|
|Descending Nested Action Level||Allow descendant options up to the specified level to be targeted by this rule's actions when executing in the configurator.|
|Rule Evaluation Event||Specify when this rule should be evaluated.|
|Rule Type||Type of Product Rule referenced by this Configuration Rule|
Configuration Rules contain a Product field that can be associated with a specific Bundle. This way you can use a single Product Rule across multiple bundles.
No setup is required.
Click New Product Action and fill out the Information fields.
Next, fill out the Filter Information fields. The fields you select here will function as follows when the associated Product Rule Type is set to Selection.
Example 1 - Selection Rule that displays an originally-hidden product
A user can only sell reporting software training once a reporting software license is selected. You have a bundle for 'Software Options,' but you don't want 'Reporting Software Training' to be displayed until 'Reporting Software License' is selected. You can use a summary variable to count 'Software Reporting License' and use that variable in the Error Condition.
Note: Make sure Apply Immediately is checked on the Reporting Software License product option.
|Product Rule Name||Show Reporting Software Training|
Tested Variable: Reporting License Count
Operator: greater or equals
Filter Type: Value
Filter Value: 1
Product: Reporting Software Training
Product: Software Options
Example 2 - Product Configuration Rule
Your business sells storage systems and you want to build product validation rules for storage bundles to ensure that users do not create bundles with invalid option configurations. If your storage system comes with chassis that have a limited number of drive bays and your users want to add hard drive options for those bays, you could create a product configuration rule that prevents users from making 5 hard drives available as options for a chassis with only 3 drive bays.
To set this up, you would first create a custom field on the Products object to contain the number of drive bays in the chassis. Then, create a Summary Variable to total the number of drive bays and the number of hard drives. Next, create a product rule that has an error condition to compare these two summary variables. Finally, create a configuration rule to associate this rule with the chassis product.
Example 3 - Testing of Quote Line Group fields
As of Salesforce CPQ Winter 17, users may select Quote Line Group as the Error Condition's Tested Object. Users can then test against Quote Line Group field values within the Quote Line Editor.
For example, a computer design business has a quote containing two Quote Line Groups - one for their "Green" monitor package and one for their "Blue" monitor package. These package types are controlled by a custom Color field added to the Quote Line Group object. Users who buy either package can add a Monitor bundle; one Product Option this package is a Monitor Stand. The business wants a Product Rule that automatically adds a Support Stand for every monitor added to the Blue package.
This Configuration Selection Rule should be created as follows:
|Field / Related List||Values|
|Product Rule Name||Add Stand to Blue package Monitor Bundles|
Tested Object: Quote Line Group
Tested Field: SBQQ__Color__c
Filter Type: Value
Filter Value: Blue
Product: Monitor Stand
When this rule is active, sales reps can add a Monitor bundle to the Blue quote line group and Salesforce CPQ will automatically add a Monitor Stand to that bundle. Likewise, Salesforce CPQ will not add Monitor Stands to any Monitor packages in the Green quote line group.
As of Winter '16, SteelBrick allows admins to use logical ANDs and ORs to build product configuration rules, which provides more control over which conditions apply to the rule. For example, a rule with 3 conditions could fire based off 1 AND (2 OR 3) logic.
Note: When Activating and Inactivating product rules for testing or debugging, make sure to activate/inactivate both the configuration rule and product rule.
As of SteelBrick CPQ Spring '16, Selection Rules can be applied to Nested Bundles within a Parent Bundle. Review Selection Rules in Nested Bundles for a comprehensive walkthrough.