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

If the incident or risk unit have additional 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 mapping file in Endpoint architecture.

The one field that has unique configuration requirements is the foreign key from the incident to the risk unit. This is the syntax for a foreign key from a custom incident to a custom risk unit.
"<CustomIncident>": {
  ...
   "<customRiskUnit>": {
     "path": "<CustomIncident>.<CustomRiskUnit>.RestV1_AsPolicyObjectReference",
     "mapper": "#/mappers/PolicyObjectReference"
   },
   ...
},
Java

For example, suppose you has a custom incident named MobilePhoneIncident_Ext, which has a foreign key field to MobilePhoneRU_Ext. The mapping property for the foreign key in MobilePhoneIncident_Ext would be:

"MobilePhoneIncident_Ext": {
  ...
   "mobilePhoneRU_Ext": {
     "path": "MobilePhoneIncident_Ext.
                MobilePhoneRU_Ext.RestV1_AsPolicyObjectReference",
     "mapper": "#/mappers/PolicyObjectReference"
   },
   ...
},
Java