...

A search can be equated to an extremely flexible API, in that the Filters of a search define what parameters are supplied and how those parameters are used to filter out results; the Value Fields of a search define what data is returned

...

The documentation includes

• a Glossarya Glossary, which defines the terms used in the Search Editor and gives examples.
• Understanding the UI elements, which describe the UI's partitioning and some design decisions
  • Rows in the grid
  • Columns in the grids.
• How-to guides
  • Guides, which guides the reader through very basic functionality.
  • Use cases, which puts the use of the Search Editor into a wider context.

...

The suggested way of approaching these documentation pages is to first get acquainted with the UI elements; then trying to perform the examples in the Guides. finally reading the Use cases to put the gathered knowledge into a wider perspective. All the while revisiting the Glossary whenGlossary when/if there is any confusion/doubts.

MUST, SHOULD

The key words keywords "MUST", "MUST NOT", "REQUIRED", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in these pages are to be interpreted as described in RFC 2119.