Return to main navigation Page
CPQ Cloud allows Price Books to be used in configuration rules as a variable in rule conditions and actions.
For Example: You can use a recommendation rule to force set a Price Book or constrain a Price Book. Constrained Price Books are removed from the Price Book list unless they are currently selected, in which case they will appear marked.
You could also use a Price Book as a rule condition for a hiding rule and hide particular attribute(s) when a certain Price Book is selected.
When a Price Book is used as the action attribute in a constraint rule, it will be removed from the Price Book list unless it is currently selected.
In the example below, a constraint rule is running that says when Boy Scouts is selected, the Price Book should be set to Scouting. Notice that the current Price Book, Sports Teams, is marked with an asterisk (*) and encased in red.
When the user clicks on the Price Book list to select a new Price Book, the only one available is Scouting.
When a Price Book is used as a rule condition in a hiding rule, it can hide attribute(s) based on which Price Book is selected. In the example below, you'll notice that in the first image, you can see the Side Items attribute displaying.
However, when the Price Book is changed to Sports Teams, you'll notice that the attribute has been hidden from view.
When a Price Book is used as the action attribute in a recommendation rule, it will be forced set for the user, meaning they will not be able to change it. In the example below, a recommendation rule is running that says when Girl Scouts is selected as the Group, then the Price Book should be set to Scouting. Notice that it is read only.
Price Books are available for use as rule inputs, whether as a rule condition or as an action attribute. They can also be used in BML scripts. The following steps explain how to use a Price Book as a rule input.
Selecting a Price Book as a Rule Input
Select the appropriate value(s) for the Price Book.