Changing match results and search scope settings

You can set the maximum number of matches that can be found for a contact and how wide the search is. In Guidewire Studio™ for ContactManager, navigate in the Project window to configuration > config and open config.xml. Change the following parameters under the heading DuplicateContactsFinderWorkQueue:

  • MaxDuplicateContactsFinderWorkQueueResults – By default, each DuplicateContactsFinderWorkQueue worker finds up to one thousand potential duplicates for a single contact. This parameter is intended to catch searches that have too loose a set of search fields and, therefore, match too many contacts in the database. If the worker finds more than the maximum allowed number of duplicates, it does not create the list of duplicates in its results list. Instead, it logs an exception that indicates the LinkID of the new contact. In addition, the new contact has an exception entry in the results list. The default setting is:
    <param 
      name="MaxDuplicateContactsFinderWorkQueueResults" 
      value="1000"/>
  • DuplicateContactsWideSearch – By default, this parameter is true, causing the process to perform a wide search using the match settings for ABPerson, ABCompany, and ABPlace. The default setting is:
    <param 
      name="DuplicateContactsWideSearch" value="true"/>
Note: This parameter applies only to duplicate finder batch processing. It does not set general searching behavior in the plugin FindDuplicatesPlugin.

When you specify wide search for duplicate finder processing, it can return matches for a larger number of subtypes than matching that uses DEFAULT_MAP (a setting of false for DuplicateContactsWideSearch). WIDE_MAP uses the contact’s supertypes, ABPerson, ABCompany, and ABPlace. This type of search aids in finding a contact that was added erroneously to the database as more than one subtype.

In the base configuration, DEFAULT_MAP additionally returns results for ABPersonVendor and ABCompanyVendor, which are subtypes of ABPerson and ABCompany. For example, if the subtype of the contact being compared against the database is ABDoctor, a DEFAULT_MAP search returns only matches for the ABPersonVendor subtype. This subtype is the closest supertype specified in the map. The wide search in the base configuration returns matches for all ABPerson subtypes, not just ABPersonVendor.

The plugin FindDuplicatesPlugin defines the ABContact subtypes used in this search in the variable WIDE_MAP.

See also