Cloud API data model design without damageables

This topic only applies to ClaimCenter.

This section identifies the requirements for custom incidents and risk units that do not make use of a damageable. For example, an insurer could offer mobile phone policies. These policies cover only mobile phones listed on the policy. Therefore, there is no need for a damageable entity.

The following sections discuss an example of MobilePhoneIncident_Ext and MobilePhoneRU_Ext. The entities and required fields are summarized in the following diagram. Note the following text conventions:

  • Base configuration entities and fields are listed in blue.
  • Custom entities and fields are listed in orange.
  • Italics are used to denote fields that provide general information about the entities in question. They may be required from a business perspective, and they appear in the examples in later topics. But, they are not required from a data model design perspective.

Fields for risk units and incidents with no damagable

Cloud API custom incident entity without damageables

A custom incident must be a subtype of the Incident entity (either directly or indirectly). Thus, it inherits the following fields: Description, LossParty, Severity.

When the data model design does not make use of a damageable, there must be a foreign key pointing from the custom incident to the custom risk unit.

For example, the following .eti file creates a custom incident named MobilePhoneIncident_Ext. It contains a general information column (RepairEstimate) and the foreign key to the risk unit (MobilePhoneRU_Ext). The Description, LossParty, and Severity fields are not specified as they are inherited from Incident.

MobilePhoneIncident_Ext.eti
<?xml version="1.0"?>
<subtype
  xmlns="http://guidewire.com/datamodel"
  entity="MobilePhoneIncident_Ext"
  supertype="Incident">  
  <column
    name="RepairEstimate"
    nullok="true"
    type="decimal">
    <columnParam
      name="precision"
      value="6"/>
    <columnParam
      name="scale"
      value="2"/>
  </column>	
  <foreignkey
    fkentity="MobilePhoneRU_Ext"
    name="MobilePhoneRU_Ext"
    nullok="false"/>
</subtype>

Cloud API custom risk unit entity without damageables

A custom risk unit must be a subtype of the RiskUnit entity (either directly or indirectly). Thus, it inherits the following fields: Description, PolicySystemID, RUNumber.

When the data model design does not make use of a damageable, there are no additional data model requirements.

For example, the following .eti file creates a custom risk unit named MobilePhoneRU_Ext. It contains only a general information column (Model). The Description, PolicySystemID, and RUNumber fields are not specified as they are inherited from RiskUnit

MobilePhoneRU_Ext.eti
<?xml version="1.0"?>
<subtype
  xmlns="http://guidewire.com/datamodel"
  entity="MobilePhoneRU_Ext"
  supertype="RiskUnit">
  <column
    name="Model"
    nullok="true"
    type="varchar">
    <columnParam
      name="size"
      value="50"/>
  </column>
</subtype>