Adding references to codes in Gosu classes and configuration files

For ClaimCenter to take full advantage of new codes from PolicyCenter, you must add references to new codes in page configurations (.pcf), Gosu classes (.gs), and other configuration files.

The following notes apply to changing new coverages.

• ClaimCenter accepts data in ACORD format and maps the data to new claims. Review the following files for two places to add ACORD mappings for new coverage types.
  • In configuration > gsrc, gw.fnolmapper.acord.impl.AcordExposureMapper.gs
  • In configuration > config, fnolmapper.acord.typecodemapping.xml
• To support ISO Claim Search for new coverage types, add entries to the following CSV text file.
  • In configuration > config, iso.ISOCoverageCodeMap.csv
• ClaimCenter has a number of methods that categorize PIP coverages. These methods govern the display of benefits tabs in ClaimCenter. For new or removed PIP coverage types, review the following Gosu class.
  • In configuration > gsrc, libraries.PolicyUI.gsx

The following notes apply to changing new policy types.

• Review the programming logic for exposure tier and claim tier mapping. You may need to change the logic in the following Gosu classes for new policy types.
  • In configuration > gsrc, gw.entity.GWClaimTierEnhancement.gsx
  • In configuration > gsrc, gw.entity.GWExposureTierEnhancement.gsx
• Review the programming logic for setting initial value on new claims. ClaimCenter generally sets the LOB code on new claims based on the loss type for the claim. You may need to change the logic in the following Gosu function.
  • In configuration > gsrc, libraries.ClaimUI.setInitialValues
• To enforce aggregate limits and policy periods for new policy types, review the settings in the following files.
  • In configuration > config, aggregatelimit.aggregatelimitused-config.xml
  • In configuration > config, aggregatelimit.policyperiod-config.xml