Hi everyone, and welcome back to bundles in Salesforce CPQ, part of Revenue Cloud. This time we’re going to be taking on level two. We will be talking about configuration rules as well as option constraints. As you might recall, in our previous video, we made a bundle and that is for a backpack with 10 different potions.
You can only choose three potions right now with our Salesforce CPQ set up. It’s allowing you to choose up to three under each feature, but it’s not smart enough to know if I only want three across all the features.
So what we’ve done here under the related area of the parent product is that we have a configuration rule. This configuration rule, if I click into it, we can see that it’s associated with the parent product, that’s the canvas backpack, and it’s linking us to a product rule that is called three potions per backpack limit. Salesforce Revenue Cloud Consulting can sometimes be about setting limits.
So this is just a junction object that connects the product with the product rule. In here for this product rule, that’s where the brains actually live, this product rule is going to say, If the conditions are met, and those conditions are located under related, take a look at the product, so the scope is the product level, and upon trying to save, that’s the evaluation event, you’re going to get a message that says, you can only add three potions for this backpack.
This is a validation, so it’s making sure that you cannot proceed unless this is, uh, is cleared, if you will. So, you must have less than three. three or fewer potions in order for this message to not stop you. Other types of product rules are alerts, so you can just let somebody know, like a friendly reminder, but this one is going to be more forceful and actually stop you from proceeding.
I gave this an evaluation order of 10 because we like to number things by 10s for easy rearranging. Let’s take a look at Related. So, over here, we have this error condition and then we’re associating it with the configuration role, so it’s connected with the canvas backpack. This error condition, it’s going to say, when should this validation pop up?
It’s going to pop up if the total number of options have a value that is greater than three. So if there are more than three options, then we’re going to error. Some people at this point like to use a formula field, and then they’ll connect it to a field. But I went ahead and made a summary variable.
Summary variables in Salesforce CPQ are sometimes a little bit intimidating if you’ve never used them, but once you get used to it, they’re quite easy, and they’re super helpful. So this summary variable is total options. We’re looking at the product options. We’re going to sum up the quantity of those product options and that’s it.
We’re just going to look at how many product options are there, add up the sum of all of those, and we’re done. So let’s go ahead and navigate back to our rule. And from this rule, we’re going to go back to our product. This configuration rule is not active. So let’s go ahead and test it while it’s not active, and then we’ll test it again once we activate it. Revenue Cloud has a ton of options for product configuration as you’re noticing.
Now I’ll just pull this up on the screen so that we can see right now our rule is not active. So if we go to quotes today, and we try to edit our lines. We are going to click on add products, we’ll choose our canvas backpack bundle, and from here I can choose, let’s say I’ll choose a couple of each of these. And now if I hit save, nothing’s actually going to stop me because I didn’t exceed three of any one feature. So I have five potions here, but my backpack can only hold three. We need to make a change in Salesforce Revenue Cloud to get things working.
So now let’s go ahead and activate our rule. Now this is active. I will go ahead and delete this backpack bundle. And let’s try this again. If I click on my canvas backpack and I select that, now let me try to add more than three. And I’ll click on save. I get a pop up that says, You can only add three potions for this backpack. Salesforce CPQ has used our rule to limit the number of potions.
That’s the exact message from our rule that we just created over here. If we were to look at our rule, this is our message. So you can see this is working. It’s really important to not just test the use case where you’re expecting this to fail, but also to test the use case where you want this to be successful.
So now I’ve got three. And I’m going to hit save and I should not get that error. Fixing errors can sometimes be a big part of Salesforce Revenue Cloud Consulting. Alright, we have this functioning exactly the way that we want. The next step is to make sure that if I choose a special potion, I have to select the other potion. We’re going to do that with an option constraint in our next video.
If you’ve enjoyed this tutorial, please like and subscribe and if you’d like to learn more about this or any other Salesforce CPQ, Revenue Cloud, or Salesforce Revenue Cloud Consulting items – you can work with us. Thank you so much!
Note: The information in this blog post is still applicable to Salesforce CPQ; however, as of Q1 2025, Salesforce CPQ has been officially deemed End of Sale and Salesforce’s new lifecycle management product has been rebranded to Revenue Cloud (previously named RLM). To view the timeline of CPQ and Revenue Cloud history, click here.
If you’d like to know more regarding the differences between Salesforce CPQ and Salesforce’s new offering, Revenue Cloud (RLM), please click here.
