Configure the mapping extension file
The REST endpoint generator automatically adds the following mappers to claim_ext-1.0.mapping.json file:
- Incident
description
id
lossParty
severity
- Risk unit
RUnumber
description
id
policySystemId
- Damageable
- (none)
Configuring the incident
This is the syntax for a foreign key from a custom incident to a custom damageable.
For example, suppose you has a custom incident named
TowableIncident_Ext
that has a foreign key field to
Towable_Ext
. The mapping property for the foreign keys would
be:
If the incident has additional business fields you wish to make readable, you must add them to the file manually. For most fields, you can find information on how to add them to a schema in Endpoint architecture.
Configuring the risk unit
This is the syntax for a foreign key from a custom risk unit to a custom damageable.
For example, suppose you has a custom risk unit named TowableRU_Ext
that has a foreign key field to Towable_Ext
. The mapping property
for the foreign keys would be:
If the risk unit has additional business fields you wish to make readable, you must add them to the file manually. For most fields, you can find information on how to add them to a schema in Endpoint architecture.
Configuring the damageable
All fields in the damageable mapper must be added manually.
Guidewire recommends making the displayName
property in the
damageable schema readable. The syntax for this is:
As an example of a damageable mapper, suppose you have a custom damageable named
Towable_Ext
that has the following readable fields:
PolicySystemId
PolicyTowable
LicensePlate
(a business field)TowableRU_Ext
(a one-to-one toTowableRU_Ext
)
The mapper for the damageable would be: