Users must also have read access to all fields referenced in rule conditions or actions.
3. Create a Rule Library
A Rule Library is essential for managing rules.
When creating the library, select “Configurator” as the Usage Type.
Make sure the Rule Library version is Activated.
4. Link Rule Library to a Context Definition
Associate your Rule Library with a Context Definition that maps to relevant Salesforce objects (e.g., Quote Line Item, Product).
Ensure correct attribute mappings and avoid cloning Context Definitions when you can extend them (recommended for easier upgrades).
5. Set Up the Advanced Configurator (If Applicable)
If you’re using the Advanced Configurator, additional setup is required:
Create a custom field: ConstraintEngineNodeStatus (Text Area (Long), length 5000) on Quote Line Item, Order Product, and Asset Action Source objects.
Map this field in the Context Definition to the ConstraintEngineNodeStatus tag.
If using assets in rules, ensure an Asset Context Definition is configured.
6. Product Setup for Configuration
Ensure products are properly structured for rule evaluation:
For bundles:
Add mandatory groups and child components.
Root product must have “Configure During Sale” = Allowed.
With these prerequisites in place, your org will be ready to support dynamic configuration experiences using rules — helping your sales teams offer tailored product bundles, validate configurations, and drive accurate quoting.