Saved Search

Introduction

Search queries that are executed on a regular basis can be created as a ‘Saved Search’ and made available to end users. A Saved Search will comprise sort and filter criteria as well as a definition of which fields to show on the data set. By default, every new Saved Search is available to any user. Role-based restrictions can be configured using an exception profile.

The MX comes with the following pre-delivered saved searches:

Users can apply respective Saved Searches directly from the dropdown of the respective data set:

Configuring a Saved Search

Users with administration rights can create new Saved Searches by going to the respective data set. Once a search query has been configured (including sort and filter criteria as well as the respective columns to be shown), the administrator can launch the search configuration popup, and click on ‘Save as…’:

This search will now be available to all users under the name given.

Administering Saved Searches

To adjust the sequence of how the saved searches appear in the dropdown (the first search is the default search), maintain localization information as well as hide or delete saved searches, the administrator can make those adjustments directly in the search popup:

*Note: the pre-delivered searches cannot be deleted.

Maintaining Exceptions for Saved Searches

If searches are meant to be used by specific user roles, an exception profile can be created:

In this profile, the administrator can define whether the search query should be shown or hidden, or whether it should inherit the display or hide parameters from the Saved Search itself. For example, if a Saved Search is configured to be hidden, but the exception profile overwrites this by setting the visibility to ‘Show’, the search will only be available to users with the respective profile assigned to their roles.