Restart both applications and test the new subtypes

After adding new contact subtypes and configuring the user interfaces in ClaimCenter and ContactManager, restart both applications and test that they support and communicate about the new subtypes.

Before you begin

Complete Add the new subtype to the ContactManager contact picker menus.

Procedure

  1. If they are running, stop the ClaimCenter and ContactManager servers, and then restart them to refresh each application with your PCF and data model changes.
  2. Log in to ClaimCenter as a user who can create new contacts.
    For example, log in as user ssmith with password gw.
  3. Open a claim and navigate to the Parties Involved > Contacts screen.
  4. Choose New Contact > Vendor > Interpreter to see the New Interpreter dialog. Verify that Interpreter Specialty is listed in the Additional Info section.
  5. Enter enough information to create an interpreter contact, such as name, address, interpreter specialty, and tax ID.
  6. Add a role for the contact on the claim, and then click Update to save the new contact information.
  7. Because you are logged in as a user with permission to create contacts, ClaimCenter sends the new contact to ContactManager.
    If you click the contact on the Contacts screen right away, you are likely to see the following message:

    Waiting for link message from ContactManager. Refresh screen to get updated status.

  8. You can refresh the screen by clicking another contact on the list and then clicking this one again.
    Eventually, you see the following message:

    This contact is linked to the Address Book and is in sync

  9. Click the Address Book tab.
  10. In the Search Address Book screen, pick Interpreter from the Type drop-down list and search for the new contact.
  11. Select the new contact found by Search and verify that the entry is correct and that you can see the Interpreter Specialty field.
  12. Return to the claim and click Actions > New > Service.
  13. For Request Type, choose Perform Service.
  14. For Vendor Name, click the contact picker and choose New Vendor > Interpreter from the drop-down list.
    The contact picker is a second drop-down button to the right of the field:

  15. Enter a name, an address, an interpreter specialty, and a tax ID, and then click OK.
  16. On the Create Service Requests screen under Services to Perform, click Add to specify a service to perform.
    There is no Interpreter service in the base configuration. Just pick any service on the list.
  17. At the bottom of the screen, choose a Service Address, and then click Submit.
  18. In the Sidebar, click Parties Involved.
    The Contacts screen opens.
  19. Verify that your new contacts have been added. Click one of the contacts to open the Basics card and verify that Interpreter Specialty is listed under Additional Info.
  20. Log in to ContactManager as a user who can create new contacts.
    For example, log in as user aapplegate with password gw.
  21. In the Sidebar, choose Search, pick Interpreter as the Contact Type, and search for one of the interpreter contacts you created in ClaimCenter.
  22. Click the contact’s name to see the details screen for the contact.
  23. On the Basics tab, click Edit and change the value of Interpreter Specialty, and then click Update to save the change.
  24. In the Sidebar, choose Actions > New Person > Vendor > Interpreter to see the New Interpreter screen.
  25. Verify that Interpreter Specialty is listed in the Additional Info section.
  26. Enter enough information to create an Interpreter contact. For Tags, click Vendor. Click Update to save the new contact.
  27. Return to ClaimCenter.
  28. Click the Address Book tab.
  29. On the Search Address Book screen, pick Interpreter from the drop-down list and search for the new contact you created in ContactManager.
  30. Click the contact found by Search and verify that the entry is correct.
  31. Search for the interpreter that you originally created in ClaimCenter and then edited in ContactManager.
  32. Click that contact and verify that the changes you made in ContactManager are in this contact’s data.