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.
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. |
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 |
|
Troubleshooting tips
Consider the following tips when you troubleshoot the Case Exchange integration:
- Incorrect configuration of the Base URL, User Name, and Password fields in the General tab usually causes authentication failure. In this scenario, 401 errors are recorded in the log file.
-
You can enable the error-handling feature when you configure the integration instance. SMIS can automatically create a new Incident record if a Case Exchange task fails. The Description field of this Incident record contains the details of the failed task record. For more information about the error-handling feature, see Error handling.
- Due to a known limitation, the error message in the SMIS task log may be insufficient to identify the root cause of a failed task. For more information about this known limitation and the workaround, see Insufficient message for a failed Case Exchange task.