Ask Search:
Kristin GormanKristin Gorman 

Suggest products based on field from Account?

Trying to build an intricate setup that is stumping me.  Kind of along the lines of "guided selling."

We have a custom field on the account we created called "Account Tier.".  The account is assigned a tier number from 1-5.  We want to use this field to drive a *suggested* product selection in the QLE.

I have a bundle product setup (SP-CW-CONFIG), with three options.  
Gold product - suggested if tier 1 on account
Silver product - suggested if tier 2 or 3 on account
Bronze product - suggest it tier 4 or 5 on account

Here's a product rule I created that doesn't seem to be doing anything:

User-added image

The idea is that after selecting the bundle product from the product selection screen, you are opened to a configurator page, and based on the account tier, it will automatically check the product you are suggested to sell.  However, we want to enable users to uncheck that one and select one of the other options as needed.  Is this even possible?  Thank you in advance for any insights or pointers!
Best Answer chosen by Kristin Gorman
Christopher HickmanChristopher Hickman
Looks like you have the correct design in mind - the account-level field needs a quote-level twin to drive the functionality you seek. And your rule is basically correct, though your "message" field does nothing as that is only relevant to validation/alert-type rules. You can't reference quote directly inside a bundle, however - you will need to create a configuration attribute which inherits a default value, see this document for this; https://help.salesforce.com/articleView?id=cpq_config_attribute_guidelines.htm&type=5

The one other piece is the "suggestion" - I don't think "Enable & Add" is correct, because you don't want any of the values to be disabled, so you should just use "Add". The problem is, there is no explict "fire this rule one time only" setting, so I would recommend creating another configuration attribute, call it something like "override default selection", be sure to set it to "apply immediately", and add an error condition to your rule which evaluates that this checkbox should be false to fire the selection logic. You will also need 2 more rules for your other selection scenario, but you may want to consider creating a lookup table rule instead, which will also give you the framework to add additional selection logic at a later time without creating additional rules to do it. See here for info on that: https://help.salesforce.com/articleView?id=cpq_lq_product_rules.htm&type=5

All Answers

Christopher HickmanChristopher Hickman
Looks like you have the correct design in mind - the account-level field needs a quote-level twin to drive the functionality you seek. And your rule is basically correct, though your "message" field does nothing as that is only relevant to validation/alert-type rules. You can't reference quote directly inside a bundle, however - you will need to create a configuration attribute which inherits a default value, see this document for this; https://help.salesforce.com/articleView?id=cpq_config_attribute_guidelines.htm&type=5

The one other piece is the "suggestion" - I don't think "Enable & Add" is correct, because you don't want any of the values to be disabled, so you should just use "Add". The problem is, there is no explict "fire this rule one time only" setting, so I would recommend creating another configuration attribute, call it something like "override default selection", be sure to set it to "apply immediately", and add an error condition to your rule which evaluates that this checkbox should be false to fire the selection logic. You will also need 2 more rules for your other selection scenario, but you may want to consider creating a lookup table rule instead, which will also give you the framework to add additional selection logic at a later time without creating additional rules to do it. See here for info on that: https://help.salesforce.com/articleView?id=cpq_lq_product_rules.htm&type=5
This was selected as the best answer
Kristin GormanKristin Gorman
Thank you very much Christopher!  This led us in the right direction.  We discovered there were 2 fields we did not haev displayed on the configuration attribute as well.  After utilizing those, we seem to have a successful process.  Appreciate your quick response!