Add ContactManager search capability in ClaimCenter

Enable ClaimCenter to search for ContactManager contacts by InterpreterSpecialty.

Before you begin

Complete Restart ContactManager and refresh web services in ClaimCenter.

About this task

In this step you set search criteria and search results in ClaimCenter that work with ContactManager. The topic uses the new Contact subtype named Interpreter that has one field, InterpreterSpecialty.

Procedure

  1. To support search on the InterpreterSpecialty field, add it to the entity ContactSearchCriteria.etx.
    1. In Guidewire Studio for ContactManager, in the Project window, navigate to configuration > config > Extensions > Entity, and then double-click ContactSearchCriteria.etx.
    2. In the editor, at the top of the Element hierarchy, select nonPersistentEntity (extension).
    3. Click the drop-down list next to and choose column.

      You use the column element because the data type is varchar and is not a typekey.

    4. To the new column, add the following values that support searches for IntepreterSpecialty:
      Name Value
      name InterpreterSpecialty
      type varchar
      nullok true
      desc Interpreter language specialties
    5. Click the drop-down list next to and choose params.
    6. Enter the following values to specify the size of this varchar column:
      Name Value
      name size
      value 30
  2. Add an entry for InterpreterSpecialty to the Gosu class ContactSearchMapper so you can use this field when you search for a contact.
    1. In Guidewire Studio for ClaimCenter, navigate in the Project window to configuration > gsrc and then to gw.plugin.contact.ab1000.
    2. Double-click ContactSearchMapper to open it in the editor.
    3. Press CTRL+F and enter convertToABContactAPISearchCriteria to find this method.
    4. Find the following line of code:
      searchCriteriaInfo.FirstNameKanji = searchCriteria.FirstNameKanji
    5. After that line, add the following code:
      searchCriteriaInfo.InterpreterSpecialty = searchCriteria.InterpreterSpecialty
  3. Add an entry for InterpreterSpecialty to the Gosu class ContactSearchResultMapper so you can see this field in the search results that come back from ContactManager.
    1. In the same Project window folder, gw.plugin.contact.ab1000, double-click the class ContactSearchResultMapper to open it in the editor.
    2. Press Ctrl+F and enter populateContactFromSearchResult to find that method, and then in the method enter the following statement:
      if (contact typeis Interpreter) {
        contact.InterpreterSpecialty = searchResult.InterpreterSpecialty
      }

What to do next

Configure the address book search interface in ClaimCenter