Claim Incident Configuration table
Summarize
Summary of Claim Incident Configuration table
The Claim Incident Configuration table ([sninsclaimincidentconfig]) in the Insurance claims application allows you to associate service definitions with incidents and adjuster tasks. This table facilitates the creation of claim incidents in the workflow and automatically generates adjuster tasks, reducing the need for manual notifications.
Show less
Key Features
- Active Status: Indicates whether the incident is active and displayed in the first notice of loss playbook.
- Adjuster Task Service Definition: Defines the service that creates adjuster tasks for claims.
- Adjuster Task Generation: Configurable to create tasks either per incident or per incident type.
- Incident Table Name: Specifies where incidents are stored.
- Itemized Loss Support: Indicates if the claim incident allows itemization of losses.
- Order: Determines the sequence in which service definitions appear in the playbook.
- Short Description: Provides a brief description shown in the playbook.
Key Outcomes
Utilizing the Claim Incident Configuration table enables streamlined incident management within the Insurance claims application, ensuring efficient task creation and enhancing user experience in reporting claims. For example, in travel insurance, it supports itemized loss reporting and integrates seamlessly into the claims workflow.
Associate the service definition of a case with the incident and adjuster task service definitions by using the Claim Incident Configuration [sn_ins_claim_incident_config] table in the Insurance claims application.
Claim Incident Configuration table overview
You can define the claim incidents that can be created in the Insurance claims workflow by making an entry in the Claim Incident Configuration [sn_ins_claim_incident_config] table. This incident type also creates an adjuster task in the system for the corresponding case so that you don't have to notify the adjuster about the case.
To access the Claim Incident Configuration [sn_ins_claim_incident_config] table, set the application scope of your instance to Insurance claims, and then navigate to .
The following example shows the table fields of the Claim Incident Configuration (sn_ins_claim_incident_config) table. For more information, see the next section.
Claim Incident Configuration Table fields
| Field | Description |
|---|---|
| Name | Name of the claim incident configuration entry. |
| Active | Status of whether this incident is active or inactive and whether the incident displays in the first notice of loss playbook. |
| Adjuster task service definition | Adjuster task service definition (that is, a service definition that creates an adjuster task in a claim). For more information, see Create a service definition for Insurance claims. |
| Create adjuster task | How an adjuster task is generated:
|
| Incident table name | Table in which the incidents are stored. For more information, see Claim incidents. |
| Incident type icon | Icon that displays in the playbook for the claim incident. |
| Itemized loss available | Whether the claim incident supports itemizing each loss (for example, to itemize each item in a baggage claim). |
| Order | Order in which the service definition appears in the playbook. |
| Service definition | Service definition for the case (for example, Report travel claim). For more information, see Creating a service definition for Insurance claims. |
| Short description | Brief description of the claim incident, which is also displayed in the playbook. |
Travel insurance example of the Claim Incident Configuration table
In the following travel insurance line of business (LOB) example, the claim incident configuration is reflected in the workflow when reporting a travel claim. The Incident details activity in the first notice of loss playbook shows the entries in the table and information about each entry.
If the claim incident supports an itemized loss as defined in the table, the Itemized Loss/Expenses tab is also displayed when the incident is saved as shown in the following example.