Find duplicates behavior

In their base configurations, the Guidewire core applications call the ContactManager web service ABContactAPI.findDuplicates to see if there are duplicates for a contact. The match types that ContactManager can return are exact match and potential match. For example:

  • ClaimCenter calls this API when setting up a link for a contact. If there is an exact match, ContactManager establishes the link automatically. If the match is potential, ContactManager sends the potential matches to ClaimCenter, which displays them and enables you to choose one. Linking proceeds as described in Linking in ClaimCenter.
  • Both PolicyCenter and ClaimCenter call this API when you click the Check for Duplicates button while adding a new contact. They also call this API when you save a new contact and you have not previously clicked Check for Duplicates.
    • If you click Check for Duplicates, ContactManager checks for exact and potential matches and sends the results to the core application, PolicyCenter or ClaimCenter. The core application shows the results and enables you to choose one.
    • If you click to save a new contact and have not clicked Check for Duplicates, the core application and ContactManager participate in the find duplicates exchange as described previously.
    • If you click to save a new contact and have already clicked Check for Duplicates, there is no additional find duplicates check. However, if there is an exact match that you have not chosen, the core application shows a warning that an exact match was available.

      You must confirm one of the following:

      • If you want to create a new contact, confirm that you do not want to choose the exact match.
      • If you do not want to create a new contact, click to cancel the operation.
  • BillingCenter calls this API when you add a new contact to an account or policy period, as follows:
    • The first time you click to save a new contact, BillingCenter and ContactManager participate in a find duplicates exchange. ContactManager checks for exact and potential matches and sends the results to BillingCenter. BillingCenter shows the results and enables you to choose one.
    • If you choose a contact from a list of exact or potential matches, BillingCenter links that contact and sets it up to be synchronized.
    • You might save a new contact if there were no matches listed or if you do not see a good match on the list of contacts. In this case, there is no additional find duplicates check. However, if there is an exact or potential match on the list that you have not chosen, BillingCenter shows a warning that a matching contact was available.

      You must click one of the following:

      • Update to continue and create the new contact
      • Check for Duplicates to choose from the list.
  • In ContactManager, to configure this matching behavior you can edit the FindDuplicatesPlugin plugin, which implements the interface IFindDuplicatesPlugin. Additionally, there is a set of Duplicate Finder classes that work with the plugin. You can edit these classes to add new subtypes and fields to the find duplicates process.

See also