|
In addition to the SE Suite simple search, it also possible to define some properties that allow filtering the results in a better way. See below some advanced options to be added to the search token.
Within the SE Suite full text search, it is also possible to perform specific searches for some properties of documents, workflows and other components. These properties include: exact token, attributes, title, ID #, description and name of electronic files.
KEYWORD
|
DESCRIPTION
|
exact
|
Used to return records with the token exactly as defined in the original record, ignoring the radicalization rules.
|
attributes
|
Used to return records only through the value of its attributes.
|
title
|
Used to return records only through the value of its title.
|
id
|
Used to return records only through the value of its ID #.
|
description
|
Used to return records only through the value of its description.
|
fileName
|
Used to return records through the names of electronic files.
|
See below an example of the use of the keywords described above:
SEARCH EXAMPLES
|
exact: any content to search
|
attributes: sample attribute value
|
title: doc title sample
|
id: DOC-SAMPLE
|
description: softexpert SE Suite
|
fileName: SE Suite-integration-guide
|
|
Logical operators are a way of better filtering which kind of content the components should have to perform the search. See below the logical operators that can be used in the SE Suite search engine:
OPERATOR
|
DESCRIPTION
|
AND
|
Logical operator that unites all tokens in the search. It filters only the components that have all of those tokens.
|
OR
|
Logical operator that separates each token on the search. It filters the components that have any of the searched tokens.
|
NOT
|
Logical operator used to exclude a token from the search. It filters the components that do not have the token entered after this operator.
Instead of using this operator, it is also possible to use a hyphen before the token to apply the same effect. Follow the example below:
To have the same effect as:
SE Suite AND NOT softexpert
it is possible to use:
SE Suite -softexpert
|
By default, the searches performed in SE Suite use the AND logical operator between each searched token.
It is important to point out that the logical operators must always be entered with uppercase letters; otherwise, they will be interpreted as search tokens.
|
|
SEARCH EXAMPLES
|
SE Suite AND sample
|
softexpert OR SE Suite
|
SE Suite AND NOT softexpert
|
SE Suite -softexpert
|
title: softexpert OR attributes: SE Suite
|
sample AND (SE Suite OR softexpert)
|
|
Wildcards are key symbols that can be used to complement a search token, being dynamically replaced to find the desired results. See below a table with the wildcards supported by the SE Suite search mechanism:
WILDCARD
|
DESCRIPTION
|
*
|
Used when you wish to search for a token and you do not know part of it. This wildcard is used to replace the unknown part of the token. See some examples below
To search for softexpert, you can use:
soft*
*pert
softe*t
It is important to point out that this wildcard is used to complete a word automatically, but searches that start or end with the wildcard are harder and may take longer.
|
?
|
Used when you wish to search for a token without entering a single character. This wildcard will replace the unknown character. See some examples below
To search for softexpert, you can use:
soft?xpert
?oftexpert
softexper?
|
See below some examples of searches using these wildcards:
SEARCH EXAMPLES
|
SE Suite s?mple search
|
soft?per? search engi?e
|
sesui* s*rch sample
|
system soft*pert
|
|
Another feature supported by the SE Suite search mechanism is the use of whole sentences. In this case, unlike a basic search, the order of the tokens is relevant to bring the right result. That is, only records with those tokens in that specific order will be returned.
To search by sentences, simply add the search tokens between double quotation marks (""). See below some examples of searches by sentences.
SEARCH EXAMPLES
|
“how to search in SE Suite search engine?”
|
“the process is finished”
|
“softexpert integration guide”
|
“the big stack of samples”
|
|
|
