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.50

Develop > Process Designer Tailoring Best Practice Guide > Best practices for using the condition editor > Use cross-table fields

Use cross-table fields in Condition Editor

Cross-table fields, which are defined by a reference record, are the fields of related tables. The table relationship is maintained by the Relation Manager in Service Manager. You can use cross-table fields in Condition Editor to configure various conditions.

To configure the cross-table fields as part of a condition, you can select the cross-table field names in Condition Editor. However, using cross-table fields might be time-consuming because the system needs to prepare the variable of the reference record at run time. For example, an incident record has the field “Contact”, which refers to the Contact record. You can configure the Rule condition to use the Location of the Contact record directly, as shown below:

At run time, the expression is evaluated to something as follows:

location in $L.file.contact.name.contacts.contact.name="Asia"

The variable $L.file.contact.name.contacts.contact.name is prepared by the rule engine.

If you use the Condition in your own scenario, make sure to invoke the JavaScript method below at run time before evaluating the condition expression, which automatically prepares the cross-table reference record for you:

lib.Workflow.initVarForCondition(conditionXml);

Send Help Center feedback