It is important to note that users of the Cúram Generic Search Server should notice no functional difference between their searches and server searches implemented using SQL; in addition, the screens and general user experience can remain the same. As such, the following example assumes that readers will develop such application functionality (along with the appropriate Facade classes, etc.) as normal.
In our Person Search example, users will navigate to the relevant UIM page to perform a Person Search. On this page, they will fill in one or more search criteria. When they hit the 'Search' button, the search will be performed. The results will consist of a list of records matching the search criteria.
In application searches, it is common for the search criteria and details returned in the results list to be collated from multiple related entities. For the Person Search the following entities and their attributes are either used as search criteria or returned as result fields:
Each of these entities is related by a foreign key association; concernRoleID is thus the external key of the SearchService attribute for the PersonSearch Search Service (see SearchService Table)
The following attributes will thus be used in the search - either as part of the search criteria, or as a displayable part of the results list:
As such, these will be the Fields stored in the SearchServiceField table for the PersonSearch Search Service.