Client and Policy Search Enhancement Prototype
The results of searches on the Client Search screen and Policy Search screen can now be sorted by configurable criteria.
Prototype Configuration
- The PolicySearchScreen business rule was configured to sort search results based on the values of three fields: PolicyNumber, StatusCode and IssueStateCode. In the Global Rules Explorer, navigate to Business Rules | Screen Rules | PolicySearchScreen | Plan Overrides|PolicySearchScreen (Functional Prototype Plan) to view the configuration, the key aspects of which are explained below.
- The <OrderBy> element is repeated three times in order to use the values of the following three fields in the sorting of the search results:
- PolicyNumber
- StatusCode
- IssueStateCode
- PolicyNumber has an ordinal value of 1, meaning it is the main criterion used in the sort operation. The results will be sorted in ascending order with respect to PolicyNumber.
- StatusCode has an ordinal value of 2, meaning it is the secondary criterion used in the sort operation. The results will be sorted in ascending order with respect to StatusCode.
- IssueStateCode has an ordinal value of 3, meaning it is the tertiary criterion used in the sort operation. The results will be sorted in descending order with respect to IssueStateCode.
- The IssueStateCode column is configured to be hidden in the search results table, but is still used as a criterion in the sorting operation.
- The <OrderBy> element is repeated three times in order to use the values of the following three fields in the sorting of the search results:
- The ClientSearchScreen business rule was also configured to sort search results based on the values of three fields: LastName, AddressLine1 and AddressLine2. In the Global Rules Explorer, navigate to Business Rules | Screen Rules | ClientSearchScreen | Company Overrides | ClientSearchScreen (Prototype Company) to view the configuration, the key aspects of which are explained below.
- The <OrderBy> element is repeated twice in order to use the following data in the sorting of the search results:
- LastName
- Address, a composite column composed of the AddressLine1 and AddressLine2 database columns
- LastName has an ordinal value of 1, meaning it is the main criterion used in the sort operation. Because no value was specified for the ORDER attribute in the configuration, the search results will by default be sorted in ascending order with respect to LastName.
- AddressLine1 has an ordinal value of 2, meaning it is the secondary criterion used in the sort operation. The results will be sorted in descending order with respect to AddressLine1.
- AddressLine2 has an ordinal value of 3, meaning it is the tertiary criterion used in the sort operation. The results will be sorted in descending order with respect to AddressLine2.
- The <OrderBy> element is repeated twice in order to use the following data in the sorting of the search results:
View Prototype in OIPA
- Log into OIPA using credentials for a user assigned to the Prototype Company.
- Navigate to the Policy Search screen.
- In the Company Name field, select Prototype Individual Child Company.
- If Products are enabled, in the Product field, select Individual Prototype Product.
- In the Plan field, select Functional Prototype Plan.
- Enter some search criteria and select Find.
- Note that the search results are sorted as described in the Prototype Configuration section above.
- Navigate to the Client Search screen.
- Enter some search criteria and click Find.
- Note that the search results are sorted as described in the Prototype Configuration section above.