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 |
|
- Problem Management overview
- Problem Management implementation
- Proactive and reactive Problem Management
- Using mass update with record lists in Problem Management
- Incident Management relationship
- Change Management relationship
- Priority, impact, and urgency
- Problem Management users
- Problem Management phases
- Problem Management assignment groups
- Problem Management Macro List Editor
- Problem Management tables
- Problem Management link records
- Problem Management and Service Level Management
- Escalation and Notification
- Historical problem records
- Incident trending for problem identification
- Integration
- Known Error
- Problem record data model
- Problem prioritization
- Problem records creation
- Problem workarounds
- Logs of problem record updates
Known Error
There are two main phases to the Problem Management process: Problem Control and Error Control. In the first phase, the Problem Manager or technician assigned to the process studies infrastructure trends and analyzes services and CIs to determine possible failure points. In the second phase, the analyst documents the findings related to an identified problem, and initiates a corrective course of action that may include: documenting a workaround; recording a Known Error condition pending future action; or creating a Request for Change. The “recording of a Known Error condition pending future action” could be the result of a defect that requires resolution from a third party such as a software patch or firmware upgrade.
Problems and Known Errors can be opened against multiple environments, including development, testing, and production environments, by using Category/Area/Sub-Area and/or CI names that identify the environment following the same general process.
Known Errors are visible in linked Incident records. Similar Known Errors can be searched for during Incident creation. Known Errors are also visible in related Change records. Known Errors are indexed by the search engine and presented in knowledge search results.
Known Error found in the development environment
Known Error records can be opened directly to show the known errors found in the development environment. This is a useful activity as Known Error records are automatically used to support other processes including Incident and Knowledge Management. Automatic searches and matching of problem descriptions in an Incident creation or knowledge search can highlight Known Error records for the user.