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

Codar1.80

HTML Template Configuration/Troubleshooting Notes

Be sure the HTML template file names are correct. The names must be the same as the default HTML template file names, with the exception of the design-specific email templates, which also follow a specific naming convention. Only the contents of the HTML files can be changed.
The name of the directory under csa.war\WEB-INF\classes\notifications must be the same as the Organization Identifier, and not the Organization Display Name.
Two or more versions of a service design will use the same template if a design-specific template is defined. If the components differ widely across these versions, it is not possible to create different design-specific templates for each version.
The notification tokens are case-sensitive. For example:${INFRASTRUCTURE_SERVICE-SERVER_GROUP.serverCount} is not the same as ${infrastructure_service-Server_group.serverCount}.
If tokens are seen as-is in email notifications, check to see if the tokens are entered correctly. Verify that the components containing these properties, and the properties, are visible. Properties with encrypted data cannot be accessed.
The tokens must be entered exactly as shown in the HTML Template Configuration/Troubleshooting Notes section. If the token is entered incorrectly, the email notification will show the token name rather than the name that the token represents.
To debug any possible issues in collecting data required for HTML notifications, enable debug logging for the following in log4j2.xml. This file can be found under csa.war\WEB-INF\classes:

com.hp.csa.service.notification.NotificationMailServiceImpl

com.hp.csa.service.notification.templates

Debug log entries will be seen in the csa.log file.

Note For Clustered Codar nodes, email templates, csa.properties and log4j2.xml must be identical across all nodes so that the behavior is consistent in a cluster. The HTML templates and any modifications to the templates must be applied to each Codar node in the cluster.

Legacy text notifications will be sent under these conditions:

If there is an error while creating emails in HTML. Look up csa.log and correct any parsing issues.
If notifications are sent for Service Instance Upgrade, Pause On Failure and Transfer Subscription.

Send Help Center feedback