Full Text Search

This is a Beta feature. If you are interested in this functionality, please contact your Redox representative.

Intro

Full text search is a tool that can be used to search for messages or transmissions that are associated with your organization. This feature is located under the ‘Full Text Search’ heading on the left hand menu.

If you’d like to dive in directly, take a look at the example search below. For a more detailed walk-through, there are several examples throughout this article.

Detailed Walk-Through

Getting Started

Step 1

Select the Source or Destination you’d like to search within. Currently, full text searches must be limited to a particular source or destination.

Clicking on the dropdown will give you a list of your organization’s destinations and sources, as seen in the screenshots below.

You must select a source or destination to submit a search query request.  Note that a source or destination is technically all that is required to submit a search. If no other search criteria is specified, all messages or transmissions associated with the specified source or destination will be returned.

Note: Queries will only search for messages and transmissions within the purge window (which, by default, is 2 days). Anything outside the purge window will not be searchable.

Step 2

Enter the string you’d like to search for in the query field and click ‘Submit Query’.

In the following screenshot, we are looking for messages or transmissions where the term “Timothy” appears.

Step 3

Sort your search results and see more detail on your message of interest. The following screenshot shows the result set. Clicking on the ID will open up more details on the resulting message or transition.

 

Boolean Logic

In search mode, boolean logic will be applied. For example, if you are looking for transmissions with the words Timothy or Elizabeth, you would type:

Timothy OR Elizabeth

Wildcards

Currently supported wildcards: *, ?

For example:

Timot?y

will match “Timothy”, and so will:

Timoth*

Further Reading

Under the hood, we are using Lucene Query Syntax provided by elastic search.  For more information, check out the documentation here.