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	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Operations Manager i10.62

Administer > Service Health > How to Customize Service Health > How to Customize the Changes and Incidents Component

How to Customize the Changes and Incidents Component

The following section describes how to customize which CIs have related requests for change and incidents displayed in the Changes and Incidents component, and in the Hierarchy component drill-down. For an overview, see Changes and Incidents Component.

By default, incidents and requests for change are displayed for the following CI types: Business Service, Siebel Application, Business Application, Node. If you want to view change and incident information for other CITs, perform the following procedure:

Within Administration > RTSM Administration > Modeling Studio, copy one of the TQLs within the Console folder, and save your copy with a new name. These default TQLs perform the following:

TQL name	Description
CollectTicketsWithImpacts	Retrieves Service Manager incidents for the selected CI, and for its child CIs which have an Impact relationship.
CollectTicketsWithoutImpacts	Retrieves Service Manager incidents for the selected CI.
CollectRequestForChangeWithImpacts	Retrieves Service Manager requests for change, for the selected CI, and for its child CIs which have an Impact relationship.
CollectRequestForChangeWithoutImpacts	Retrieves Service Manager requests for change, for the selected CI.

Edit the new TQL as needed. You can add CITs as described in Naming constraints for new TQLs below.
Open Infrastructure Settings:

Administration > Setup and Maintenance > Infrastructure Settings

Alternatively, click Infrastructure Settings.
1. Select Applications.
2. Select Service Health Application.
3. In the Service Health Application - Hierarchy (360) area, enter the name of the new TQL you have create in the corresponding infrastructure setting.
Note that by default these infrastructure settings contain the default TQL names. If you enter a TQL name that does not exist, the default value will be used instead.

After you modify the infrastructure setting, the new TQL will be used, and the Changes and Incidents component will show this information for the CITs you have defined.

Naming constraints for new TQLs

The following naming constraints should be followed in the request for change without impact TQL (see the TQL example below, on the right side of the image):

The request for change CI type should start with directPlannedChange.
The CI type related to the request for change should start with trigger.

The following naming constraints should be followed in the request for change with impact TQL (see the TQL example below, on the left side of the image):

impacterPlannedChange represents the request for change CI type.
The CI type related to the request for change should start with impacter.
triggerITUniverse represents the "impacted" child CIs.

Examples of request for change TQLs:

The following naming constraints should be followed in the incidents without impact TQL (see the TQL example below, on the right side of the image):

The incident CI type should start with directITIncident.
The CI type related to the incident should start with trigger.

The following naming constraints should be followed in the incidents with impact TQL (see the TQL example below, on the left side of the image):

impacterITIncident represents the incident CI type.
The CI type related to the incident should start with impacter.
triggerITUniverse represents the "impacted" child CIs.

Examples of incident TQLs:

Send Help Center feedback