Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| Search for | Example | Results |
|---|---|---|
| A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
|
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
Limitations on cross-table join queries
The new implementation of the Cross Table Join mechanism has the following limitations and behavior changes:
- You can only run a query on the eight functions that are described in Cross-table join functions
- The
DISTINCTclause is not supported. -
You cannot run a join operation on the following:
-
BLOB or CLOB objects (This is a limitation common to most RDBMSs)
- Image data-types
- Text data-types
-
Encrypted fields
-
LDAP files
- Joined files
- Merged files
- Tables in different RDBMSs
-
-
Queries on IR files now behave differently. Specifically, the following behaviors now occur:
-
Full text search no longer stems. The revised mechanism uses an SQL
LIKEclause to retrieve results. Therefore, a search based onLIKE "%printer%"will no longer return stemmed variants such as "printing" or "printed." In the previous implementation, stemming was included because the query was run entirely in Service Manager and leveraged the stemming dictionary. -
You can no longer perform a full text search in the Cross Table Query in SM. Full-Text Search can only be performed in the initial relational search.
-
Results are returned only from the exact fields\ that you specify. For example, if you searched for the term "printer" on the "Title" field by using the previous mechanism, you would receive a hit even if the term was not mentioned in the "Title" field, but only in the associated "Desc" field. With the new mechanism, you will only receive a hit if the term appears in the "Title" field.
-
- You can no longer
GROUPorSORTby BLOB objects.
