MENU
A Revenue Cloud Consultant is writing a constraint rule in Constraint Modeling Language (CML) to prevent customers from selecting a red laptop case if the selected laptop model is Executive Pro. The consultant anticipates that this color restriction might apply to other products in the future and wants to make the rule easier to maintain and reusable across multiple rules.
Which approach should the consultant take?
Exact Extracts from Salesforce CPQ Advanced Configurator (Constraint Modeling Language Guide):
''Global constants enable administrators to define reusable values that can be referenced across multiple CML rules.''
''Using global constants ensures consistent logic and simplifies maintenance when constraints need to be updated.''
''Avoid hard-coded literals or repetitive local variables in multiple rules, as this increases maintenance complexity.''
Step-by-Step Reasoning:
Requirement: Create a reusable restriction for color ''red'' across several product rules.
Best Practice: Define global constant, e.g., const BlockedColor = 'Red'.
Why C is Correct:
Global constants promote reusability and reduce redundancy.
Changing one constant updates all dependent rules automatically.
Why Others Are Incorrect:
A: Local variables are limited to each rule; no reuse.
B: Hardcoding values breaks scalability and maintainability.
Salesforce CPQ Advanced Configurator Developer Guide --- Constraint Modeling Language (CML) and Global Constants
Salesforce CPQ Implementation Guide --- Best Practices for Constraint Rules and Reusability