Use full-text search to look for entries within the internal Designer database. You will find the full text search on its own menu bar in the Designer.
To search for a term
You can enter more than one partial terms. Use of wild cards (*) is permitted. Case sensitivity is not taken into account. Entries are searched for that contain all the partial terms given.
Entries (objects) are already displayed while the search term is being entered.
Figure 6: Displaying the Source
If there is not entry found for an search term, suggestions are made that you can accept by double clicking with the mouse.
Figure 7: Suggestions for Search Terms
If you have selected an entry, the search term is added to the search history and is therefore available for further searches.
The number of entries in the search history depends on your program settings.
Figure 8: Search History
|
TIP: Update the full text catalog of the Designer database if you need to include objects in the search that have been edited after the program started, like new processes or column names. You do this with the Update index item, in the search history. |
It is possible to limit the number of list entries in certain Designer editors by using a filter. After creating a filter, the filter conditions are immediately implemented on the set of result currently displayed. A filter remains in use until you reset it.
Ad hoc filters are used for a one-off reduction of list entries. These filters are not saved and are applied to the data immediately.
A permanent filter is recommended if you want to reuse it more frequently. Permanent filters are saved in the user configuration and therefore are always available for use.
Ad hoc filters are used for a one-off reduction of list entries. These filters are not saved and are applied to the data immediately.
To use an ad hoc filter
This opens the wizard for creating database queries. The wizard helps you to formulate a condition (where clause) for database queries. The complete database query is composed internally. It always refers to the database table that is specified when you start the wizard.
|
IMPORTANT: Enter the condition for limiting the result set in SQLite notation. The condition is defined as a valid where clause for database queries. The condition relates to the selected database table found that is determined when the editor starts. |
For more information, see the One Identity Manager User Guide for One Identity Manager Tools User Interface and Default Functions.
Permanent filters are saved and are therefore always available for use. There is a wizard to help you maintain permanent filters.
Icon | Meaning |
---|---|
Adds a new filter. | |
Edits filter name. | |
Deletes filter. | |
Switches between displaying database query input in SQLite notation or in the wizard. | |
Tests filter. |
To create a permanent filter
This opens the wizard for managing filters.
|
IMPORTANT: Enter the condition for limiting the result set in SQLite notation. The condition is defined as a valid where clause for database queries. The condition relates to the selected database table found that is determined when the editor starts. |
After the test is completed, a test report is displayed. All the list items are shown that meet the condition. A summary of the test status is also shown.
For more information, see the One Identity Manager User Guide for One Identity Manager Tools User Interface and Default Functions.
© 2023 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy