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 |
|
- Optional manual migration tasks
- Configure the Change Management module to use the new Task Planner
- Upgrade to the Process Designer related record subform
- Use the Process Designer workflow viewer in your forms
- Configure the Search form
- Migrate the solution matching configuration from security profiles to security settings
- Update reports to use Process Designer-based category tables
- Make the Category field in the Interaction form read-only
- Revert to using the "escalate to Change" wizard
- Remove the button in the Incident form that cancels the Interaction escalation process
- Migrate any customization of the knownerror table
- Remove the legacy Request Management dashboard and report definitions
- Enable legacy Request Management and Process Designer-based Request Fulfillment to run in parallel
Configure the Search form
Search forms in Process Designer-based systems and in Classic systems are different. For example, the Process Designer-based Incident module uses the "im.advFind.incident.search" search form, instead of the "advFind.incident.search" search form. If you had previously customized some fields in a search form, you must manually add these fields to the Process Designer-based version of the search form.
We recommend that you use the Process Designer search form. However, if you want to continue to use the Classic search form, you must update the SearchConfig record to revert the changes applied by the Applications Upgrade Utility. To do this, set the value of the Search Format field to the appropriate Classic search form for that table.
The following table lists the mapping between Process Designer-based search forms and their Classic equivalents.
|
Table name |
Classic search form |
Process Designer search form |
|---|---|---|
|
probsummary |
advFind.incident.search |
im.advFind.incident.search |
|
cm3r |
advFind.search.change |
advFind.search.chm |
| cm3t | advFind.search.task | advFind.search.task |
|
incidents |
advFind.SD.search |
sd.advFind.search |
|
rootcause |
advFind.search.problem |
pbm.advFind.search.problem |
|
rootcausetask |
advFind.search.problem.task |
pbm.advFind.search.problem.task |
