Loading
The online Trailblazer Community becomes read-only Oct 30, 2026Read More
Important Advisory: iOS Update Impacting CG Mobile ApplicationRead More
Insurance
Create Claim Product Models

Create Claim Product Models

A claim product model describes a claim that an insurance policyholder can file against an insurance policy.

The structure defined by this product model is used by the InsClaimService: createUpdateClaim service. The claim product model defines the structure of the input JSON used by this service to create and update a claim.

Plan Your Claim Product Model

When you plan your claim product models, think of them in terms of claim types. Each claim type will define the structure of the claim and include a set of rules to handle that type of claim. Product modeling is part art and part science, so there is no one-size-fits-all structure to recommend. Instead, you can take several different approaches for any given claim type.

Important
Important

These examples illustrate just a few valid configurations. Your actual business requirements may differ.

Method

Example

Unique claim product per root product

Homeowners, Renters, Personal Auto, and Watercraft claims can be structured and handled differently enough to warrant distinct root product and claim product definitions for each one.

Diagram that shows unique claim product per root product

Single claim product for multiple root products

Personal Auto and Commercial Auto can be unique root products because of the different selling and rating processes inherent in these two lines of business. But the types of claims made for these root products can be similar enough to handle through a single Auto claim product.

Diagram that shows a single claim product for multiple root products

Multiple claim products for a single root product

You can sell an Identity Protection coverage under a Homeowners root product along with standard Dwelling and Contents coverages. But the claim handling structure and rules for claims made against the Identity Protection coverage are probably nothing like those used for Dwelling and Contents coverages. An Identity Protection claim product, distinct from a Homeowners claim product, is a way to segment the structure and rules for handling Identity Protection claims separately from standard Homeowners claims.

Diagram that shows multiple claim products for a single root product

What's in a Claim Product

A claim product can include one or more claim injury specs and claim property specs. It also includes coverage specs—the same coverage specs attached to the insurance product model(s) that this claim product relates to.

Claim products, claim injury specs, and claim property specs are built using attributes, which can be the same attributes that root product specs and child product specs are built from, and attributes created specifically for claim products.

Tip
Tip

Vlocity recommends that you add all the coverage specs to a claim product model that exists on the insurance product model(s) this claim product relates to.

A claim product can also include rules that define how a claim moves through state transitions (for example, from "new" to "open"), and how actions happen when a claim product is used by Vlocity at runtime to create or update a claim.

Note
Note

You'll create claim rules in the Underwriting Rules section of the Rules tab on your claim product models.

Despite the name on the UI, these are not underwriting rules. They're claim rules.

Here's an example of a basic structure of an Auto Claim Product model:

Auto Claim Product model diagram

In this structure:

  • The Claim Involved Vehicle spec is used at runtime for both the insured item (vehicle) on the policy that's involved in the claim, and for any third-party vehicles that are also part of the claim.

  • The Injury spec is used to define the injuries that are incurred by any person on the claim.

Claim Property Specs are fairly straightforward in that if you're adding an involved property to a claim, it's sustained some damage, and that would be captured on the Claim Property Spec. On the other hand, if you're adding people to a claim, it’s less obvious if the Claim Product Model needs to be used.

Most of the characteristics about people are actually stored in Accounts and Contacts, so these don't need to be captured in the Claim Product Model. And you don’t need to capture the roles for a person associated with a claim. All the “person” details are stored on the claim directly through the Claim Participant.

Use of the Claim Product Model is necessary only when additional information needs to be captured about a person’s involvement in a specific claim, like if they have an injury as modeled in this P&C Auto Claim Product.

Workflow for Claim Product Modeling

 
Loading
Salesforce Help | Article