What is the Ardexa Search?
The tab within Ardexa Web Application is a view that provides you the ability to retrieve, view and analyse your historical data collected from your workgroup devices, your sources and from your teams user activity within the application itself.
Building a New Search
All new searches start with first selecting the table where your data is stored. For a table to be available for selection, the table must be first defined and populated with data collected from your devices and their sources, otherwise it won't appear in the list.
Table definitions are pre-configured. To create a new table definition please contact your account manager for assistance. This help article assumes that your tables are defined and populated.
The Search View Layout
After selecting the table with your data, the Ardexa Web App will automatically present to you the search view ready for you to manage and execute your searches.
Your Total Available Records
When you first select your table, the total number of records in your selected table are immediately provided to you in the upper-left corner of the view.
The button, found on the right-hand side of the view is used to execute searches against your data collected from your devices. At any time while building your search you may click the button and a search will be conducted based on the current parameters you have set in the view.
Building your search
Search time-frames are periods from which you would like the data to be retrieved.
Common timeframes are a list of preset periods that are provided to you for easy selection.
The default value is 'today'. If you were to click button with 'today' selected, this example common time-frame would attempt to retrieve all records from the selected table from midnight (last night) until 11pm, 59 minutes today in your local time.
As an example, today may translate to:
Start: 01/01/2019T00:00 End: 01/01/2019T59:59
Hint: To review a literal translation of a pre-set Common timeframe, simply select the value custom after your initial selection and then the literal timeframe translations will appear in the view.
NB: However, keeping the selected value as custom will maintain the literal values against the search should you ever decide to save the search. This is important when you come to retrieve a saved search, as you will be supplied the literal timeframes from the past if the value of Common timeframe is kept as custom. Hence, the pre-set Common timeframe will not be applied if it is saved with custom. More on custom selection and saved searches below.
Concept: Time Zones
All searches are conducted using your local time wherever that may be.
Example; you might move time zones, log into the Ardexa Web App and then run a saved search. The search will be conducted using your new time zone and the data retrieved are likely to be different had you been in your old time zone.
Example; two different people in your team run the same 'today' search from different time zones, at-the-very-same-time; then the concept of today would apply locally and the data retrieved for each person would likely be different. Essentially, the period defined for, what is today for me in one timezone is different for what is today for you in another timezone.
The following demonstrates a 'today' query taken at the same time from different time zones against the same data:
|Time Zone: AEDT (Australia)||Time Zone: CET (Germany)|
|Current Date-Time: 08/11/2019 @ 12:35pm
|Current Date-Time: 08/11/2019 @ 2:35am