Loading
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
            Multiple Rating Procedures per Product or Multiple Specs at Any Level for getRatedProducts

            You are here:

            1. Salesforce Help
            2. Docs
            3. Digital Insurance

            Multiple Rating Procedures per Product or Multiple Specs at Any Level for getRatedProducts

            Format InsProductService:getRatedProducts userInputs for products that use multiple rating procedures in the product hierarchy or multiple child specs in any level of the hierarchy.

            Note
            Note Products configured before Winter '23 release 240.22 can have multiple child specs in a given level of the hierarchy, no grandchild specs, and only one rating procedure at the root level. For these products, use the same userInputs format as you did in earlier releases. See One Rating Procedure per Product for getRatedProducts. Products configured with multiple rating procedures must use userInputs described here. The userInputs from releases earlier than Winter '23 don't support products configured with multiple rating procedures.

            For example, a commercial product that uses unique rating procedures for Location, Building, and Infrastructure has multiple rating procedures in the product hierarchy.

            Diagram of a product structure with rating procedures at two insured item levels

            A Home Insurance product with more than one piece of art and jewelry insured at a given property has multiple child specs in a single level of the product hierarchy.

            Diagram of a product structure with two insured item specs at the lowest level of the hierarchy
            Note
            Note To rate products that use a single rating procedure per root product, you format input JSON differently. To prevent errors, run the service with only one type of userInputs format at a time. See One Rating Procedure per Product for getRatedProducts.

            InsProductService: getRatedProducts looks for a userInputs key in the input JSON. Products with ratings at the insured item level have one userInputs for each insured item instance, and one separate userInputs for the root instance and its coverages.

            In the unique userInputs with insured item-level details:

            • For the insured items related directly to the root product, set parentInstanceKey to the product code of the root product.
            • For lower-level insured items, set parentInstanceKey to the instanceKey value of the parent. For example, at a Location called 1 Market Street, there's a Building called Building 100. The parentInstanceKey value in userInputs for Building 100 is 1 Market Street ('parentInstanceKey' => '1 Market Street').
            • Set instanceKey to the instanceKey value of the insured item. For example, the instanceKey value in userInputs for "Building 100" is "Building 100" ('BUILDING.instanceKey' => 'Building 100').
            • Include the insured item instance's coverages.

            In the separate single userInputs with root-level details:

            • Set instanceKey to the root product's product code.
            • Include root-level coverages.
            • Set parentInstanceKey to an empty string.

            For example, a Traveler Insurance product (TRAVEL_ROOT) covers a TRAVELER (Insured Party), LUGGAGE (Insured Item), and VALUABLES (Insured Item). The root product has accident coverage (TRAVEL_ACCIDENT), and the child products each have their own coverage (TRAVELER_HEALTH, LUGGAGE_LOSS and VALUABLES_THEFT).

            Diagram of a product structure with coverages at the root level and at multiple insured item levels

            Sample Input JSON

            This is an example for the product hierarchy with one instance for each insured item spec or insured party spec.

            {
    "userInputs": [
        {
"TRAVEL_ROOT.instanceKey": "TRAVEL_ROOT",
"parentInstanceKey": "",
"TRAVEL_ACCIDENT.FaceAmount": 3000
        },
        {     
"TRAVELER.instanceKey": "John Smith",
"parentInstanceKey": "TRAVEL_ROOT",
"TRAVELER.persName": "John Smith",
"TRAVELER.persIncome": 100000,
"TRAVELER_HEALTH.CoInsurance": 0.2
        },
        {
"LUGGAGE.instanceKey": "Suitcase",
"parentInstanceKey": "John Smith",
"LUGGAGE.valuableName": "Suitcase",
"LUGGAGE.valuableValue": 400,
"LUGGAGE_LOSS.ded_limit_Limit": 400
        },
        {
		
"VALUABLES.instanceKey": "iPad",
"parentInstanceKey": "John Smith",
"VALUABLES.valuableName": "iPad",
"VALUABLES.valuableValue": 600,
"VALUABLES_THEFT.ded_limit_Limit": 400
        },
        {
"VALUABLES.instanceKey": "iPhone",
"parentInstanceKey": "John Smith",
"VALUABLES.valuableName": "iPhone",
"VALUABLES.valuableValue": 800,
"VALUABLES_THEFT.ded_limit_Limit": 400
        }
    ]
}

            The first JSON node represents userInputs for the root product. It specifies the instanceKey TRAVEL_ROOT and the root-level TRAVEL_ACCIDENT coverage.

            The second JSON node represents userInputs for the child instance 'John Smith'. It specifies the instanceKey 'John Smith', the parentInstanceKey TRAVEL_ROOT, and the child-level TRAVELER_HEALTH coverage.

            The third JSON node represents userInputs for the child instance 'Suitcase'. It specifies the instanceKey 'Suitcase', the parentInstanceKey 'John Smith', and the child-level LUGGAGE_LOSS coverage.

            The fourth JSON node represents userInputs for child instance 'iPad'. It specifies the instanceKey 'iPad', the parentInstanceKey 'John Smith', and the child-level VALUABLES_THEFT coverage.

            The fifth JSON node represents userInputs for child instance 'iPhone'. It specifies the instanceKey 'iPhone', the parentInstanceKey 'John Smith', and the child-level VALUABLES_THEFT coverage.

            Keep in mind that:

            1. For each JSON node above, %ProductCode%.instanceKey and parentInstanceKey are both required.
            2. If there are multiple instances of one insured item spec or insured party spec, such as the ‘iPad’ and ‘iPhone’ above, there should be multiple JSON nodes included in the userInputs, each with different instanceKeys.
             
            Loading
            Salesforce Help | Article