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 |
|
- Understanding links
- Advanced link editing features
- Specifying a link query
- Copying fields by name during fill operations
- Scalar/non-scalar field links
- Keeping changes
- Link dependencies within Service Desk
- Document Engine master link record
- Add a new link file
- Modify an existing link
- Test a link
- Delete a link
- Access advanced link maintenance
- Copy information from structure fields to scalar fields
Scalar/non-scalar field links
A simple link cannot copy information from a non-scalar field (composed of more than one data element of the same type) to a scalar field (composed of a single data element). For example, information from a record in the incident file cannot be projected into a probsummary record. Even though the field names are the same, the fields in the incident record are not scalar fields. They exist in one of the three structures that make up the problem table descriptor. The fully-qualified name of the assignment field in the incident record is really header,assignment.
The system can project the logical.name value in the incident file into the incident record’s logical.name field. It cannot project the incident file’s non-scalar middle,logical.name field into the scalar logical.name field in the incident file. To copy non-scalar information to a scalar field, the Fill operation copies each field using instructions in the link record.
Related concepts
Advanced link editing features
Specifying a link query
Copying fields by name during fill operations
Keeping changes
Link dependencies within Service Desk
Document Engine master link record
Specifying a link query
Related tasks
Add a new link file
Modify an existing link
Test a link
Delete a link
Access advanced link maintenance
