Configuring contacts

There are multiple levels of contact configurability.

  • PolicyContactRole and AccountContactRole are extendable, as are all of the roles in the default configuration.
  • You can define new contact roles by defining new subtypes of PolicyContactRole and AccountContactRole. Accompanied by appropriate account and policy level user interfaces, the new contact roles are automatically integrated into the contact scheme of the application.
  • You can configure which fields on a contact role are revisioned.
  • You can define whether a particular contact role can be held by a Person, Company, or both.
  • If you do not need them, you can disable contact roles defined in the default configuration.
  • You can configure at what points and on what policy transactions PolicyCenter synchronizes contact information. This behavior can vary by role.

Gosu classes for contacts

You can find the Gosu classes for Contact by navigating to configuration > gsrc and finding the Classes.gw.contact package in Studio.

Configurable Gosu classes for revisioned fields

Policy period entities with revisioned fields have configurable Gosu classes that maintain and synchronize these fields. Before the policy is bound, these fields get their value from the account. At binding, these fields are copied to properties in a Gosu enhancement associated with the entity. The fields in the entity are updated by calling the getter and setter methods in the enhancement.

The following table lists some of these classes provided in the base configuration.

Files

Fields

PolicyContactRoleAccountSyncableImpl.gs

PolicyContactRoleEnhancement.gsx

Synchronizes CompanyName, FirstName, and LastName for all policy contact roles. These files are in the gw.contact package.

PolicyDriverAccountSyncableImpl.gs

PolicyDriverEnhancement.gs

Synchronizes LicenseNumber and LicenseState for PolicyDriver. This role is specific to personal auto. These files are in the gw.lob.pa.contact package.

PolicyOwnerOfficerAccountSyncableImpl.gs

PolicyOwnerOfficerEnhancement.gs

Synchronizes RelationshipTitle for PolicyOwnerOfficer. This role is specific to workers’ compensation. These files are in the gw.lob.wc.contact package.

Plugins for contacts

The following plugins are related to contacts.

Contact Configuration plugin

The IContactConfigPlugin plugin configures the Contact entity.

The IContactConfigPlugin maps the PolicyContactRole to the corresponding AccountContactRole. For example, the code maps PolicyNamedInsured to NamedInsured.

The code also controls which Contact subtypes (Person or Company) are allowed for each role. For example, it specifies that an AccountHolder can be a Person or a Company, but a Driver or a PolicyDriver can only be a Person.

The IContactConfigPlugin can also disable roles. You disable roles by setting first argument in the line configuring the contact to false: 

new ContactConfig(false, {"company", "person"}, "AuditContact", {"PolicyAuditContact"}),

In the base configuration, each PolicyContactRole references one AccountContactRole. However, you can configure several PolicyContactRoles to reference one AccountContactRole.

See also

Account Syncable plugin

The AccountSyncablePlugin implements the IAccountSyncablePlugin interface. This plugin implementation handles the synchronization of revisioned fields between accounts and other entities such as contacts and locations.

The only method is refreshAccountInformation, which refreshes account information to ensure the account has the most current data when calling the other methods. This method takes an entity instance that implements the main AccountSyncable interface.

See also

Contact batch process

The Apply Pending Account Data Updates batch process applies pending updates to account data such as an update to revisioned contact information. In the default configuration, this batch process runs every day at 12:10 a.m.

For example, if you make a future-dated policy change to a policy contact’s name, the batch process applies the name change to the account on the policy change effective date.

See also