Designer 10.5 | webMethods BPM Task Development Help | Configuring Tasks | Configuring Business Data (Task Inputs and Outputs) | Creating Custom Search Fields from Task Business Data | About Task Search Operators
 
About Task Search Operators
When you create custom search fields as described in Creating Custom Search Fields from Task Business Data, you specify an operator to be used by the Task Engine to find matching field values.
Note:
By default, custom field searches are always case-sensitive. If you want to make case-insensitive searches available, see Implementing Case-Insensitive Searching.
All operators do a compare on the object type, except for the like operator, which implements a wildcard search (see below). For example, for a data type of Integer, all data comparisons are done with the integer object. Your search input is converted to an Integer and compared to the business data field's Integer value.
The following table lists the available operators:
Operator
Definition
=
Equals.
>
Greater than.
<
Less than.
<>
Does not equal.
>=
Greater than or equal.
<=
Less than or equal.
like
The like operator enables you to find task business data for a field by specifying partial search characters and an asterisk (*) character (a wildcard search). For example, to do a wildcard search for a zip code, you could enter "980*", which returns results for all zip code data from 98000 to 98099.
not like
This operator provides the same wildcard searching as the like operator, but with the opposite results.
between
The data returned by the search falls between two dates.
in
The data returned by the search contains a specified value in an array. For example, if an array [1,2,3] exists, searching for a value of 2 will obtain a match. This operator also works for a single string, but acts like the = operator.
not in
This operator provides the same array searching as the in operator, but with the opposite results.
Related Topics