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)`

Configuration Management System (CMS)2018.05

Use > JMX Reference > Administration Methods > How to Show/Hide the "Cannot invoke trigger" Error Message on UI

How to Show/Hide the "Cannot invoke trigger" Error Message on UI

The JMX setting appilog.collectors.ShowCanNotInvokeError in the getInternalSetting method allows you to show or hide the "Cannot invoke trigger" error message on UI. The default value for the setting is true.

To hide the "Cannot invoke trigger" error message,

Go to JMX Console > UCMDB:service=Settings Services > getInternalSetting.
Invoke the getInternalSetting method with the following parameters:
- customerID: <Customer ID>
- key: appilog.collectors.ShowCanNotInvokeError
On the result page,
- To show the error message, replace the null value with true (default) and click Set.
- To hide the error message, replace the null value with false and click Set.
Note that for the error message displayed for a specific trigger, the change takes effective the next time the trigger CI is triggered. Since not all triggers are scheduled to run at the same time, you may still see occurrences of the error message on the UI for some time before it completely goes off.

Send Help Center feedback