Advanced Rules Framework

Advanced Rules Framework allows you to design sophisticated natural language criteria along with customizable interfaces to ensure the right products are available to eligible customers at the right price in the right configuration. Advanced Rules determine which products and under what circumstances they apply using Entity Filters, and they are built using Rule Builder. You can use Advanced Rules to create rules that depend on context, product attributes, and multiple criteria.

Salesforce provides the following rule types: Compatibility, Pricing, and Availability & Eligibility rules.

• Compatibility rules: Use product relationships to ensure products ordered in Industries Cart are compatible based on conditions in order line items and related objects. They are also known as Configuration or Validation rules.

• Pricing rules change standard pricing and operate on order line items in Industries Cart.

• Availability & Eligibility rules are legacy rules that display or hide products in Industries Cart's product list based on conditions in opportunity, quote or order header data or data in related objects such as Accounts or Assets. (Except in certain circumstances, these rules have been replaced by context rules.)

Advanced Rules Framework works in tandem with Context Rules Framework. To understand which type of rule to use in each situation, see Context Rules or Advanced Rules: What Type to Use?

Salesforce provides a configure, price, quote (CPQ) rules framework. Rules are associations of entity filters and actions. Entity filters evaluate objects for specific conditions. Rules execute actions on qualified objects.

You can create and implement reusable rules using the Rule Builder. Each rule is built using natural language. The natural language and visual Rule Builder enables designing new offers and managing promotions through availability, eligibility, compatibility, and pricing rules. Rules use filters to identify a set of items, and then apply one or more action steps to each remaining item. You can choose from existing filters and actions, or you can create new ones.

Note

• The chaining of Advanced Rule execution and validations are not supported. Within a single API transaction, the result of one rule does not affect the execution of the other.
• To ensure all validation issues are addressed, you must make an additional runCartValidation API call.

For example, if an Auto-Add rule adds a product, it will not automatically trigger validation for a Recommends or Requires rule.

• About Build Rules and Entity Filters
  Before building a Rule, you must create all of the associated Entity Filters, Rule Filters, and Rule Actions. Also, you must create all of the Rule Action procedures.
• Rules for Industries CPQ
  Salesforce provides an Industries Configure, Price, Quote (CPQ) rules framework. Rules are associations of entity filters and actions. Entity filters evaluate objects for specific conditions. Rules execute actions on qualified objects.
• Product Relationships
  Products can be related to one another. For example, a product may require, exclude, or recommend another product. You can define relationships between products using Product Relationship objects. Product Relationship objects are then used in compatibility rules to ensure that the correct combination of products is ordered. For example, if a customer orders Product A, the interface may recommend Product B.
• Setting Up an Availability or Eligibility Rule to Exclude Declined Products
  This topic provides an example of how to configure an availability or eligibility rule where all products that have been declined as part of the account offers within the last 12 months are excluded from the product list. Eligibility and availability rules must be created against the Header object (Opportunity, Quote , Order). This example is based on the Opportunity object.
• Setting Up an Attribute Configuration Rule to Modify Attributes Across Line Items
  This topic provides an example of how to define a configuration rule in which a parent line item modifies the attributes of a child line item.