When searching, you can make use of an extensive search syntax and search in field values. Some of the options are also available in the search settings: Search settings.

The extent to which the entries affect the search results depends on the configuration. The system can for example be configured in a way that no difference is made between upper and lower case when performing an exact search.

Search syntax

Operator	Function
AND, UND, +	Logical AND
OR, ODER, +	Logical OR
NOT, NICHT, -	Exclusion
*	Placeholder for any number of characters
?	Placeholder for exact one character
~	Fuzzy search
" "	Phrase search
[1 TO 10]	Range including boundary
{1 TO 10}	Range excluding boundary

Logical operators

You can use the logical operators AND, OR and NOT to combine queries.

The operators must be written in capital letters so that they are not interpreted as normal words in the search query.
Partial requests can be grouped in parentheses.
Example: (September OR November) AND invoice
If no operator is specified between the words, a logical AND operation is used by default for up to three words. If there are more than three search terms, only a part of the terms must be included.
For more complex logical expressions, you should always use full parentheses.
Alternatively, you can use the + and - operators before the search terms, where + is the AND operator and - is the NOT operator.
Example: house -city +countryside
Do not mix the two types of request with AND/OR/NOT and +/-.

When searching with wildcards like an asterisk * or a question mark ? or with the fuzzy search with a tilde ~ a timeout may occur or calculating the search result may be aborted. Narrow the search in the case.

Search method	To find	Syntax	Examples
Wildcard search	Documents where individual letters, or the ending are unknown.	te?m, term*	me?er finds meyer, meier, meder safe* finds safety, safeguard
Phrase search	With the phrase search, you can find documents in which certain words occur side by side. The words you are looking for are enclosed in quotation marks::	"phrase"	"Angela Merkel“
Fuzzy search	With the fuzzy search, you can find documents in which words occur that are similar to the search word. AUTO - default value. 1 - the result can differ by maximum one character. 2 - the result can differ by maximum two characters. More information: Elasticsearch Documentation More information about the number of edits: Levenshtein Edit Distance (Wikipedia)	term~AUTO term~1 term~2	mayer~AUTO (finds Mayer, Meyer, Meier etc.) meier~1 (finds Meier, Maier, Meyer but not Mayer)
Sloppy Phrase Query	With the Sloppy Phrase Query , you can find documents in which certain words occur at a maximum distance (measured in words) from each other.	''phrase''~10	“house garden“~10 (finds for example the house with the wonderful garden)
Range query	The range search finds documents that contain words that appear (alphabetically) between the search words. This is useful for area searches on numbers or dates. The following example retrieves all documents that were changed between 2004-06-29 and 2004-06-30.	[x TO y]	_long.datelastmodified:[2020-06-29 TO 2021-06-30]
Unit search	The unit search finds documents that contain units. About 60 technical and scientific units such as length, area, volume, speed, temperature, etc. are taken into account. In addition, dates and monetary amounts are normalized and recognized.	UNIT/*(unit)	UNIT/(km/h)*

The following characters are reserved: + - = && || > < ! ( ) { } [ ] ^ " ~ * ? : \ /. When you use these characters in the search query, they are interpreted as part of the search syntax. If the syntax is incorrect, the logic of the search query may change and lead to unexpected results.

Example: Monitor 25" AND 27" results in searching for the phrase " AND 27" and does not get the expected results.

Extended query syntax with special search modes

Note: Depending on the configuration, not all options may be available to you.

Search mode	Operating mode
NEAR	NEAR queries specify the distance which words - listed subsequently in parentheses - may have from each other. . It depends on the configuration if you can use wildcards like an asterisk * together with this.
NEAR/0 (IntraFind AND Software)	IntraFind and Software need to be next to each other.
NEAR/S (IntraFind AND Software)	IntraFind and Software need to be in the same sentence.
NEAR/P (IntraFind AND Software)	IntraFind and Software need to be in the same section
NEAR/P (car AND self-driving) AND NOT navigation	car and self-driving need to occur in the same paragraph, the word navigation must not occur.
MODE	Defines the mode of the search, for example with normalization, special upper and lower case, observance of umlauts (diacritics), etc. The various modes can be combined meaningfully.
MODE/E (INTRAFIND) MODE/E (IntraFind AND Software) MODE/E (Kanzlerin OR Merkel)	Exact match required, only finds documents that match the term INTRAFIND in capital case Only finds documents with IntraFind in exactly this spelling AND Software. Kanzlerin or Merkel have to occur in the document.
MODE/D (MÜLLER)	Replaces diacritics (e.g., German Umlaut), Mueller and Müller will be found. Includes MODE/E.
MODE/B (sang)	Base forms: Finds sing, sung. Includes MODE/E, and MODE/D.
MODE/C (booksellers)	Composed words: Also finds documents with sellers of books. Includes MODE/E, MODE/D, and MODE B.
MODE/P (Meier)	Phonetic processing: Also finds documents that are pronounced similarly (Maier, Meyer, Mayer)
*UNIT/(km/h), UNIT(miles per hour)*	Search for an arbitrary speed. Note the asterisk!
*UNIT/(°C), UNIT/(kelvin)*	Search for an arbitrary temperature.
*UNIT/(dollar), UNIT/(€)*	Search for an arbitrary amount of money in Dollar or Euro, respectively.
DATE/*	Search for an arbitrary date.
DATE/(03.04.1995;7 days)	Search for a date around 3^rd of April 1995 +/- 7 days.
UNIT/>=(1 million dollar)	Search for at least $1.000.000.
UNIT/>=(50 kW)	Search for an output of at least 50 kW. Due to unit normalization this will also match the document, The motorcycle has an output of 68 hp.
UNIT/(20 Meter;2m) or UNIT/(20 Meter)~2a or UNIT/(18-22 meter) or UNIT/(18 to 22 meter)	Search for a length between 18 and 22 meters. Note the different ways to specify the interval.
*NEAR/S(UNIT/(km/h) AND “speed limit” AND Canada AND highway)**	Search for a sentence containing speed limit, highway, and Canada and an arbitrary speed. Only matches if a sentence contains an actual value for the speed limit.
NEAR/S(“melting point“ AND UNIT/(1400 to 1600 °C))	Search for a sentence that contains melting point, a temperature between 1400 and 1600 °C. Note that this query will also match if a temperature is specified in Kelvin or Fahrenheit, but fits into the specified range after normalization. The query could help to find a substance with a melting point in the specified range.

Searching in field values

The field value search enables you to search within a specified search such as file name, file extension, author, date. You can also use search operators. You can use the normal search bar for the field search and combine it with other search terms. Searching in field values is rarely necessary, because you can filter the search results using metadata, see Filtering the hit list.

Searching with actual field names

In the standard configuration, the field _str.language is used to store the document language.

Syntax: fieldname:query

The following field value search returns all documents that are in German and contain the terms Stuttgart and Messe.

_str.language:de Stuttgart Messe

Search with logical field names

If your administrator has enabled this feature, you can also use logical field names for the search. The administrator must be configured by the administrator.
Example 1: For the actual field name _str.attachment the following logical names can be configured:attachment, fileattachment, emailattachment, Example 2: The logical field name language has been assigned to the actual field name _str.language and can thus also be used for the search. The following field value search returns all documents that are in German and contain the terms Stuttgart and Messe:

language:de Stuttgart Messe

Syntax examples

The following table shows some syntax examples for the specific use of field value searches.

Field values	To find
_str.fileextension:pdf	Documents of type PDF. Alternatively, you can enter *.pdf pdf and *pdf.
_str.author:melanie	Documents that contain the name Melanie in the metadata field Author.
_str.author: "melanie may"	Documents that were created by the author Melanie May.
*_str.filename:casepdf**	Documents that start with the filename case and end with pdf.
_str.language:de	Documents that contain German text.
_str.company:microsoft	Documents that contain the value Microsoft in the metadata field Company.
_str.application:directory	All folders for which you are authorized.
_str.application:directory launcher	All folders whose names contain the term launcher.

Default field names and logical variants

Note: The fields in your installation might be different, and they also depend on the connected data sources.
The list of field names and their logical equivalents are based on the default configuration and the assignments made by the administrator.

Default field name	Logical variants (as implemented in administration)
_str.aboutme	aboutme, about
_str.abstract	abstract
_str.account	account, user
_str.address	address
_str.application	application, program
_str.attachment	attachment
_str.author	author,
_str.bcc	bcc
_str.category	category
_str.cc	cc
_str.cellphone	cellphone
_str.client	client
_str.company	company
_str.connector	connector
_str.creator	creator
_long.datecreated	date, createdate, creationtime, creationdate
_long.datelastmodified	changedate, modifieddate, modificationdate
_str.department	department
_str.description	description
_str.doctype	doctype
_str.editor	editor
_str.email	email
_str.enclosingfile	enclosingfile
_str.filename	name
_str.fileextension	extension, file type

Searching for phone numbers

If the search for phone numbers is configured on your system, you have the following options for entering them:

Full phone number with or without country code: 0049351833, 351833
Start or end of phone number with or without country code: 49351, 0049351, -124
Without separator: 0049351833
With separator: 49-45179-351-833, 49179-987-833

The search finds all phone numbers with and without separators and spaces, e.g. 49351, 0049351, 0049351833, 351833, +49 (0) 351/833 820, 49-45179-351-833

To find all phone numbers with a specific beginning, you can use the wildcard search, e.g. 0049351*, which will result in longer search times.

Confluence Query Language (CQL) field references

In the iFinder Confluence Search you can enter search queries with the used Confluence field names. The iFinder detects and interprets the Confluence Query Language (CQL) syntax used for these queries.

Note the following differences

Instead of the = operator, use a colon.
Operators must be written in upper case.
Other than in CQL syntax, filter values must be written in quotation marks.

Example:

Standard CQL syntax	iFinder Confluence Syntax
label = approved	label:"approved"
label = approved and space = DEV	label:"approved" AND space:"DEV"

Supported fields:

The following fields are supported by default:

favourite, favorite
label
parent
space
space.category

Limitations:

CQL date functions such as endOfDay() and others are not supported.