Revenue Management Developer Guide

Get Started with Revenue Management Developer Resources
Revenue Management Settings
Revenue Management Deployment
Product Catalog Management
Salesforce Pricing
Rate Management
Product Configurator
Product Configurator Standard Objects
Product Configurator Business APIs
Product Configurator Standard Invocable Actions
Product Configurator Metadata API Types
Constraint Modeling Language
Modeling a Generator Set
Core Concepts
Global Properties and Settings
Variables
Types
Relationships
Constraints
Logical Constraints
Table Constraints
Proxy Variables with Constraints on Types and Relationships
Message Rule
Preference Rule
Require Rule
Require Rule vs Constraint
Setdefault Rule
Exclude Rule
Action Rule
Hide or Disable Rule
Recommendation Rule
Set Product Selling Model in a Constraint
Core Concept Examples
Annotation Examples
Constraint Modeling Language (CML) Best Practices
Business-Centric Constraint Modeling Language (CML) Guidelines
Debugging Constraint Modeling Language (CML)
Model Structure
Transaction Management
Advanced Approvals
Dynamic Revenue Orchestrator
Usage Management
Billing
Revenue Management Associated Objects
PDF

Preference Rule

The preference rule encourages the constraint solver to satisfy the condition, but doesn't enforce it if the condition can't be met.

The system tries to satisfy the condition in a preference rule, but if for some reason it can't, the system delivers a failure message to the user with Info severity.

If a preference rule auto-adds a product that has one or more Product Selling Model Options (PSMOs), set one PSMO on the product to Default. The system uses the default PSMO to determine which pricebook entry to use for the auto-added product. For more information, see Manage Product Selling Model in Revenue Cloud in Salesforce Help.

Note

The preference rule has this syntax.

1preference(logic expression, string literal | string variable, argument, .., argument);
2preference(logic expression, string literal | string variable);
3preference(logic expression);

A preference rule can include an optional explanation message for failure. The message is of Info severity, meaning it does not block the user from continuing with the action.

In this example, the preference rule encourages the user to mention the dBMax value as 90 and the requiredKW value as 500.

1type GeneratorSet {
2   int requiredKW = [101..10000];
3   int dBMax = [0..140];
4   preference(dBMax == 90, "90 preferred for dbMax");
5   preference(requiredKW == 500,"50 preferred for requiredKW");
6}