Loading
Agentforce is temporarily unavailable. Please try again later or visit Help topics below. For additional support, please contact your local support number for assistance. Thank you!
Prepare for Email to Become the Default Login ExperienceRead More
The online Trailblazer Community becomes read-only Oct 30, 2026Read More
Important Advisory: iOS Update Impacting CG Mobile ApplicationRead More
Ongoing maintenance for Salesforce HelpRead More
Insurance
Understand Impact on Existing Quotes

Understand Impact on Existing Quotes

Before you enable Constraint Rules Engine, review how it affects quotes created before and after enablement.

Required Editions

Available in: Lightning Experience
Available in: Developer, Enterprise, and Unlimited Editions of Revenue Cloud where Product Configurator is enabled

When you enable Constraint Rules Engine (CRE) in Revenue Settings, Product Configurator begins using CRE to process configuration rules on new quotes. Quotes created before CRE was enabled don’t run CRE rules unless you migrate those rules to CML.

Best Practices

  • Because Constraint Rules Engine is in beta, validate the features with your product model in a sandbox before enabling in production.
  • After testing, migrate existing dynamic rules to CML and then enable Constraint Rules Engine for production use.

What to expect after enabling Constraint Rules Engine with dynamic rules

  • If Advanced Configurator is set as the default engine, all new quotes automatically use a Transaction Processing Type (TPT) with Advanced Configurator as the default rule engine. These quotes will use the constraint engine for rule processing.
  • If TPT with Standard Configurator is created and Standard Configurator is set as the default engine, both existing quotes and new quotes use Business Rules Engine for rule processing.
 
Loading
Salesforce Help | Article