Loading
Feature degradation | Gmail Email delivery failureRead More
Insurance
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Set Up Constraint Rules Engine

            You are here:

            1. Salesforce Help
            2. Docs
            3. Digital Insurance

            Set Up Constraint Rules Engine

            Set up the Constraint Rules Engine rule engine by creating the ConstraintEngineNodeStatus custom field on Quote Line Item object, updating the InsuranceContext context definition to map the field, and adjusting your procedure plan definition so that Insurance quotes use Constraint Rules Engine.

            Required Editions

            Available in: Lightning Experience
            Available in: Developer, Enterprise, and Unlimited Editions of Revenue Cloud where Product Configurator is enabled
            Permission Set
            Permission Set Name Description
            Product Configuration Constraints Designer Create and manage constraint types and rules in Configurator with Constraint Rules Engine.

            Create the ConstraintEngineNodeStatus Custom Field

            Before your rule designers can create advanced configuration rules and sales reps can use them, you must create the ConstraintEngineNodeStatus custom field on the Quote Line Item object. Constraint Rules Engine uses the fields to store data for internal processing.

            1. From the object management settings for Quote Line Item, go to Fields & Relationships.
            2. Click New.
            3. Select Text Area (Long), and then click Next.
            4. Enter Constraint Engine Node Status as the field label.
            5. Enter 5000 as the length.
            6. Enter ConstraintEngineNodeStatus as the field name.
            7. Click Next.
            8. For the profiles whose users use Constraint Rules Engine, make sure that the Read-Only option is deselected.
              Note
              Note For Customer Community and Partner Community users to run constraints, give these profiles also access to this field. Select the Visible option and deselect the Read-Only option for the profiles.
            9. Click Next.
            10. Deselect the page layouts, and save your changes.

            Update the InsuranceContext Context Definition

            After you create the ConstraintEngineNodeStatus field, update your extended InsuranceContext context definition ​​to use the field. If you don’t have the extended context definition, extend InsuranceContext before you add the attribute.

            Note
            Note Make sure to use the extended InsuranceContext context definition that is configured for your default pricing procedure.
            1. From Setup, in the Quick Find box, enter Context Service, and then select Context Definitions.
            2. Edit your extended InsuranceContext context definition.
            3. Select the SalesTransactionItem node under SalesTransaction.
            4. Add the ConstraintEngineNodeStatus attribute to the InsuranceItem node with INPUTOUTPUT as the type and STRING as the data type.
            5. Click Next.
            6. Select the SalesTransactionItem node under SalesTransaction.
            7. Add a new tag ConstraintEngineNodeStatus__c for ConstraintEngineNodeStatus__c.
            8. Save your changes.
            9. Adjust the InsuranceContext context definition mapping to include the custom field.
              1. Select the Map Data tab and then edit QuoteEntitiesMapping.
            10. In the Map Data tab, make these updates.
              1. Edit QuoteEntitiesMapping and then map the ConstraintEngineNodeStatus attribute under SalesTransactionItem to the ConstraintEngineNodeStatus__c field on the QuoteLineItem object.
              2. In QuoteEntitiesMapping, review the context mappings and make sure that the TransactionType attribute on the SalesTransaction node is mapped to the TransactionType field on the Quote object.
            11. Save your changes and activate your context definition.

            Update Procedure Plan Definition

            Define rule-based criteria for the Advanced Configurator transaction processing type in your existing procedure plan definition for insurance.

            Make sure you've already set up a procedure plan definition with:

            • Process Type: Insurance
            • Primary Object: Transaction Processing Type
            • At least one Pricing Procedure section
            • Rule-based resolution
            1. From Setup, in the Quick Find box, find and select Procedure Plan Definitions.
            2. Open the procedure plan definition you've configured for Insurance.
            3. In the Procedure Plan Sections area, locate the pricing procedure section.
            4. Confirm that the Resolution Type is set to Rule-Based.
            5. Add a new condition to support the Advanced Configurator transaction processing type:Advanced Configurator Pricing Procedure
              resource operator output value
              Label Equals Advanced Configurator
              In the condition, specify the DeveloperName of the Advanced Configurator TPT.
            6. Save and activate your procedure plan definition.

            Enable Constraint Rules Engine

            Enable rule designers to create advanced configuration rules and constraints, and help sales reps run the rules for transactions (quotes).

            1. From Setup, in the Quick find box, enter Revenue Settings, and then select Revenue Settings.
            2. Turn on Set Up Configuration Rules and Constraints with Constraint Rules Engine.
              When you enable Constraint Rules Engine, AdvancedConfigurator is the default engine for transaction types in your org.
             
            Loading
            Salesforce Help | Article