PolicyCenter database search functionality

To search for a specific entity, select the Search tab from the PolicyCenter interface. In the base configuration, you can search for the following:

• Policies
• Accounts
• Producer Codes
• Activities
• Contacts

During a search, PolicyCenter uses only those fields on the form for which you enter data. For example, if you search for a Policy and enter a Last Name but not a Policy Number, PolicyCenter omits Policy Number from the search.

In the base configuration, PolicyCenter also provides database search from screens other than those accessed through the Search tab. For example, you can do a database search for policy form patterns, policy locations, regions, and other entities and objects.

For each search, PolicyCenter uses one of the following types of objects to encapsulate search criteria.

Object type	Description
Gosu class	In the base configuration, PolicyCenter implements most search criteria with Gosu classes. An example of a Gosu class as a search criteria object is the AccountSearchCriteria class, which is defined in AccountSearchCriteria.gs.
Virtual entity	PolicyCenter implements some search criteria objects as virtual entities. A virtual entity has no underlying table in the PolicyCenter database and do not persist beyond the session in which you use it. An example of a non-persistent entity as a search criteria object is DocumentSearchCriteria, defined in search-config.xml.

Every field on the Search screen maps to an attribute on the relevant search criteria entity. For example, in the Activity search screen:

• Assigned To maps to AssignedUser in the ActivitySearchDV PCF file.
• AssignedUser maps to searchCriteria.SearchAssignedUser in the same file.
• SearchAssignedUser maps to gw.activity.ActivitySearchCriteria, the Gosu class definition that contains the business logic to search on the assigned user field.