Advanced Search

An advanced option is available next to the quick search to enable search on a combination of attributes. In the advanced search dialog, the user can enter values for multiple fields. Click Advanced to display the search component. When a user clicks the Advanced Search button or link, the Advanced Search dialog is displayed providing the ability to add multiple search criteria (using the Add Criterion button (hover text: Add Criterion, icon: qual_plus_24.svg and the Criteria dropdown list). It is possible to enter the search criterion based on the property type (of the lowest level property) next to it. Individual attributes adhere to single value or referenced property design.

This component supports search on string (enums, booleans), integer, date, date-time, referenced type properties. For details refer to the "Properties" chapter in the Developer Guide.

The advanced search component:

"advancedSearch": {
  "criteriaMandatory":true|false,
  "properties": [
   {  "name":"name of the property"
      "sequence": 1,
      "queryOperator":"bet|gte|lt|like|likeic|eq",
      "toUpperCase":"false|true
    },
    { "name":" name of the property"
      "sequence": 2
      "queryOperator":"bet|gte|lt|like|likeic|eq"
    },
    ...
  ]
}

When a user selects the search criteria, enters search values for them and clicks the Search button (hover text: Search, icon: magnifier_16), the dialog closes and a search is performed based on all entered search values. If a criterion is entered, but no value is given, then the criterion is not considered for the search.

Specifying criteriaMandatory as true restricts a user from performing a blank search on any property. When not specified system considers it to be false.

The dialog can be closed by clicking anywhere outside the dialog. The selected criteria and entered search values are remembered until the user changes them, clicks the Reset link or signs out of the application (or the user session expires).

If advanced search specifies only one property, then instead of "Advanced" link, the property is directly displayed on the page. Selecting the value triggers the advanced search.

The search is case-insensitive. The default search operator is like for text attributes that allow wildcards like % and , the search operator is _equals for other types of attributes. Multiple input parameters are combined using an AND statement. OR-search is implemented between the various values of a property when the same search property is added multiple times, For example, A can search for claims with Code like CL004% AND (Status=Enter OR Status=Change) is possible.

NOTE

Personalization ensures that minimum one valid property (when a specified property does not exist, system ignores that property) is specified.

Consider the following example for configuring advanced search on the claims object:

"advancedSearch": {
  "properties": [
    { "name":"servicedMember",
      "sequence":1,
      "refType":"person"
    },
    { "name":"claimantProvider",
      "sequence": 2,
      "refType":"provider"
    },
    { "name":"claimantRelation",
      "sequence": 3,
      "refType":"relation"
    },
    { "name":"startDate",
      "sequence": 4
    },
    { "name":"claimPendReasonList",
      "sequence": 5,
      "properties": [
        { "name":"pendReason",
          "sequence": 2,
          "refType": "codeDescr"
        },
        { "name":"resolved",
          "sequence": 1,
          "label": "GEN_RESOLVED"
        }
      ]
    },
    { "name":"status",
      "sequence": 6
    }
  ]
}

This displays an advanced search dialog with the following options:

Field	Input
Label[1] for serviced member	LOV component on person
Label for claimant provider	LOV component on provider
Label for claimant relation	LOV component on relation
Label for start date	Date picker
Label for pend reason in ClaimPendReason entity	LOV on pend reason
Label for Indicator resolve on pend reason	Yes or No dropdown
Label for Status	Dropdown on status

---

1. For more details on the label, refer examples in the section "Boilerplate" in Properties chapter of the Developer Guide.