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 |
|
Insufficient message for a failed Case Exchange task
The SMIS task log does not contain sufficient information for a failed Case Exchange task (QCCR1E114322)
When a Case Exchange task fails, the SMIS task log does not contain sufficient information for you to troubleshoot the root cause of the failure.
Workaround
Use the following workaround if the SMIS task log does not contain sufficient information:
Note Remember to adjust the Log Level setting in the SMIS integration instance before you debug the error. For more information about how to configure this setting, see Integration Instance Information fields.
-
For an inbound task, the native system internally handles the exchange request from the endpoint system. In this scenario, you can find more information by using one of the following methods:
-
Check the latest message in the sm.log log file. For more information about how to view the sm.log file, see Review log file.
- Run the failed task again and then check the messages in the message history box.
-
-
For an outbound task, the native system sends the exchange request to the endpoint system and the endpoint system handles the request through RESTful APIs. In this scenario, you need a third-party tool (for example, SoapUI or Postman) to simulate and debug the exchange request.
You need to collect the following information from the Task Log Detail page of the failed task to simulate and debug the exchange request in the third-party tool:
- The request URL. You can find this URL in the latest message in the Journal Messages field.
- The request data in the Task Request Data field.
For more information about how to access the Task Log Detail page,
