Search Forms

If you leave all the search form fields blank, all objects of the same type will be displayed.

You can give the checkboxes in the search form a neutral status. In this case, they will not be evaluated.

When designing the form, the administrator can also define whether the search form entries are case-sensitive.

You can also enter placeholders in the search form fields

• ? stands for exactly one arbitrary character.

• * stands for any number of arbitrary characters.

In enaio® client, an invisible '*' (asterisk) placeholder is by default entered at the end of each text box in search forms. In the example above, simply entering 'S' would be sufficient. This setting can be changed (see 'Auto' area ). You can additionally set the client to have an invisible '*' asterisk as a placeholder before each entry. However, queries with a prepended asterisk '*' are very time-consuming.

You can search for all the objects that do not match the search criteria by placing the not-equal operators (<> or !=) at the beginning of a field. Not-equal operators can be combined with placeholders (* or ?). Not-equal operators can be used in text, number, date/time, and catalog fields, but not in index data fields with tables.

You can search for empty fields by entering the special value #NULL# in the corresponding text field. You can use the not-equal operators (<> or !=) to invert the value. If you enter <>#NULL# in a text box, only those objects will be found for which this field is not empty, i.e., which contain data.

The special value #NULL# can only be used in text fields. This value cannot be used for other data types, such as numeric fields.

Combined with other values, the query for #NULL# can lead to unexpected search results.

You can also enable the 'Search for parts of terms' option (see 'Auto' area ). If you enter several terms in a field, enaio® client will search for objects indexed with all terms regardless of the order in which they appear. If you want to search for terms separated by spaces in the entered order in this search mode, you will have to place the terms in quotation marks. This search method is also more time-consuming.

Here's an example of a search request: "Eric Peterson" Theorie

This search will present hits containing 'Eric Peterson' and 'theory', but it will not return hits in which the term 'Peterson' does not follow after the term 'Eric'.

If you search for a term sequence placed in quotation marks, you will need to enter the backslash '\' as a masking character in front of the quotation marks. You will get a notice if a field contains an odd number of non-masked quotation marks.

List catalogs may contain entries that can be used for queries but not for data capture.

The OR and AND buttons at the bottom of the list indicate whether multiple entries can be selected from a list catalog. Using these buttons, you can define how multiple values will be logically combined for the search. Add 'OR' and the hit list will contain all objects indexed with at least one of the entries, but enter 'AND' and the hit list will show all objects indexed with all selected entries. When running queries, the '*' placeholder is not set, regardless of the settings for this placeholder.

If you enter characters into the field, a list will automatically open, displaying only the list entries that start with the entered characters.

In the case of a search request, all objects with a corresponding catalog entry will be found regardless of the user language used to save the index data or the language in which the request was made. Search requests are evaluated in the user language.

For multilingual catalogs, the familiar search mechanisms (such as phonetic search with ~) as well as other familiar operators (such as > or <) are available. * and the user’s auto asterisk settings can be used for all searches, whether saved or not.

If you only enter a value for the date in a 'Date/time' field, 00:00:00 will be added as the time. If you do not enter a value for minutes or seconds, 00 will be added in each case. If you enter a single-digit value for hours, minutes, or seconds, 0 will be added as the first digit. If you do not enter a value for the year, the current year will be added. If you only enter a value for the day, the current month and year will be automatically added.

If you only enter a value for hours and minutes in a time field, 00 will be automatically added as the entry for seconds. If you enter a single-digit value for hours, minutes, or seconds, 0 will be added as the first digit.

Date fields in a search form have an extra feature. Enter the date in abbreviated form only, i.e., the month (MM) and year (YYYY) separated by a dot, to show all folders, registers, and documents from that month and year in the hit list, e.g., 01.2012 for January 2012. If you only enter a four-digit number, it will be interpreted as the year. Four-digit numbers less than 1901 will be interpreted as invalid.

If the administrator enabled localized entry of a date in enaio® enterprise-manager, dates will be entered in a format based on the regional Windows settings.

The <, >, and not-equal to (!= and <>) operators can be used to further narrow down searches.

Examples of searching via the date field:

• >01.01.2015 to search for objects containing a date after the date specified in the date field

• <31.01.2015 to search for objects containing a date before the date specified in the date field

• >=01.01.2015 to search for objects containing a date on or after the specified date in the date field

• <=31.01.2015 to search for objects containing a date on or before the date specified in the date field

It is also possible to search with operators for abbreviated forms of a date, e.g., <06.2015.

Smaller/larger operators can also be linked with time periods: day (d), week (w), month (m), and year (y).

Examples:

• <-2y to search for objects containing a date earlier than the current date minus two years in the date field

• >-4d to search for objects containing a date later than the current date minus four days in the date field

An interpolation search is available in date, date/time, time, and numeric fields. If you enter two values separated by a hyphen, the system searches for objects that are either indexed with one of the values or whose index data lies between the values.

Operators and interpolation searches are not permitted by the basic parameter fields Created, Edited, and Archived. The exact date must be entered. It is always preceded by >=.

In addition to interpolation searches, the <, >, and not-equal to (!= and <>) operators can also be entered in numeric fields.

When searching in table fields, the search will only include the column you entered the search term in. If you additionally enter a line number in the first column, only this line will be searched.

Text boxes can be combined by the administrator into a search group. If you enter a search term in a text box that is part of a search group, the search will include all fields of the group. Search groups are not flagged in the search form.

Some search forms have a full-text search input field. This is subject to the condition that the corresponding object type(s) has/have been configured accordingly for full-text search by your administrator. This field allows you to search for terms that appear in the document content or in the index data of the objects. You can combine this full-text index search with the index data query. An explanation of which search terms and operators you can use in full-text searches is provided in Full-Text Searches – Combinations and Placeholders.

The filing tray will not be included in a full-text search.