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

Service Manager9.52

Upgrade > Upgrade the applications from a version earlier than 9.50 > Appendix A: Additional manual migration tasks on Service Manager 9.52 Hybrid > Optional manual migration tasks > Revert to using the "escalate to Change" wizard

Revert to using the "escalate to Change" wizard

The escalation to change process in Process Designer-based systems and in Classic systems is different. After you upgrade to Service Manager 9.52 Hybrid, the escalation wizard no longer appears when you click Escalate in an Interaction, and the Change is not created in the background. Instead, the Change form is launched for you to input the details.

To revert to using the Classic escalation wizard, follow these steps:

Open the "escalate.interaction" process, and modify the condition so that it evaluates to "true" for escalation to change. This ensures that the escalation wizard is displayed.

For example, modify the condition from $L.use.legacy.sd.solution.matching=true and ($L.string="create" and $exit.code.fc="normal") to ($L.use.legacy.sd.solution.matching=true or category in $L.file="request for change") and ($L.string="create" and $exit.code.fc="normal").
Open the "cc.createchange" process, and modify the expression that is evaluated before the RAD call from $escalation.wizard.call=false to $escalation.wizard.call=true. This ensures that the change is created in the background.
If it does not already exist, add the following expression to the "number" link line of the "screlate.incidents.cm3r" link:

requestedDate in $L.related=nullsub($requested.end.date, tod())

Note You can further tailor "escalate to Change" wizard by adding additional expressions or field mapping to copy data to change records.

Send Help Center feedback