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

Develop > Process Designer Tailoring Best Practice Guide > Best practices for using the condition editor > Use user option fields

Use user option fields in Condition Editor

You can configure the User Option fields as part of a condition by specifying the names and values of the user option fields in Condition Editor.

However, using the user option fields might be time-consuming because the system needs to prepare variables for the user option fields at run time. For example, you configure to use the User Option as part of a task condition in Task Planner as follows:

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

$L.UO.EmployeeType="Regular"

The variable $L.UO.EmployeeType is prepared by the system.

If you use the condition in your own scenario, make sure that you invoke the JavaScript method below at run time before evaluating the condition expression, which automatically prepares the user option variable for you:

lib.Workflow.initVarForCondition(conditionXml);

Note: The instance data of a user option is stored as a string value in the file userOption, and thus at run time, when the user option value is evaluated, it is also treated as a string value.

Send Help Center feedback