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
Core Concept Examples
Annotation Examples
Constraint Modeling Language (CML) Best Practices
Business-Centric Constraint Modeling Language (CML) Guidelines
Debugging Constraint Modeling Language (CML)
About the Apex Debugging Log File
Use the Apex Debugging Log File
Model Structure
Transaction Management
Advanced Approvals
Dynamic Revenue Orchestrator
Usage Management
Billing
Revenue Management Associated Objects
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Debugging Constraint Modeling Language (CML)

To debug constraint models and troubleshoot performance issues, enable debug logging in Apex and set the debug log level to FINE.

For more information on debug logging in Salesforce, see these topics in Salesforce Help:

Use the Apex log to get information about configurator engine performance when running a constraint model, including performance degradation or unexpected behavior. To improve performance, modify the constraint model based on information in the log.

For tips on writing trouble-free CML, see Constraint Modeling Language (CML) Best Practices.