Configure the updater extension file

The REST endpoint generator automatically adds the following updaters to claim_ext-1.0.updater.json file:

  • Incident
    • description
    • lossParty
    • severity
  • Risk unit
    • RUnumber
    • description

If the incident or risk unit have additional fields you wish to make writeable, you must add them to the file manually. For most fields, you can find information on how to add them to a updater 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>",
     "valueResolver": {
       "typeName": "<fullyQualifiedNameForCustomRiskUnitValueResolver>",
       "resolvedValueToAncestorPath": "resolvedValue.Policy",
       "rootToAncestorPath": "<CustomIncident>.Claim.Policy"
     }
   ...
},
Java
For example, suppose you has a custom incident named MobilePhoneIncident_Ext, which has a foreign key field to MobilePhoneRU_Ext. The updater property for the foreign key in MobilePhoneIncident_Ext would be:
"MobilePhoneIncident_Ext": {
  ...
   "mobilePhoneRU_Ext": {
     "path": "MobilePhoneIncident_Ext.MobilePhoneRU_Ext",
     "valueResolver": {
       "typeName": "gw.rest.ext.cc.claim.v1.claims.policy.customriskunitext.
                      MobilePhoneRUExtJsonValueResolver",
       "resolvedValueToAncestorPath": "resolvedValue.Policy",
       "rootToAncestorPath": " MobilePhoneIncident_Ext.Claim.Policy"
     }
   ...
},
Java