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 |
|
- Incident Management overview
- What is an incident?
- Affected services option for Incidents and Changes
- Submitting an incident
- Alerts and escalation
- Categories
- Posting outages
- Cause codes and probable cause
- Incident Management summary link records
- Incident Management contract management records
- Incident Management and service level agreements
- Incident Management macro list editor
- Incident Management paging feature
- Incident Audit Trail
- Alerts and Escalation
- Field-Level Controls
- Incident record data model
- Incident and Service Request Separation
- User Satisfaction
Field-level controls
Service Manager provides two basic methods for setting field level controls including making the field mandatory. The system provides two methods to indicate that a field is mandatory in the UI.
If the field only needs to be mandatory on a screen-by-screen basis, you can set the field as mandatory via a RuleSet validation. This control can be visually indicated via a property in forms designer.
If the field needs to be mandatory for all access points throughout the system, you can set a workflow-level or table-level Rulset validations by using the supplied configuration tools. In this case, the visual indication is automatic.
Visually on the screen, the system identifies a mandatory field with a red asterisk.
