1. Business Process Framework: Workflow Guide
  2. Using Standard Comparisons in the Conditions List

Using Standard Comparisons in the Conditions List

The following table describes the standard operators that the Comparison field supports. An example, showing how each operator might be used for a typical database, is also included. The format requirements for a particular RDBMS might vary.

Operator Description Examples

>=

Greater than or equal to

>=5

<=

Less than or equal to

<=5

=

Equals

=A

LIKE

LIKE

LIKE Abc%

IN

IN

IN (1, 2, 3)

NOT IN

NOT IN

NOT IN ('A', 'B', 'C')

BETWEEN

BETWEEN

BETWEEN 1 and 2

BETWEEN

BETWEEN

BETWEEN 'A' and 'B'

IS NULL

IS NULL

B IS NULL

IS NOT NULL

IS NOT NULL

B IS NOT NULL

You must use the following requirements:

  • If you use LIKE, IN, NOT IN, or BETWEEN with a character field, then you must enclose the value with single quotes.

  • If you use IN or NOT IN, then you must enclose the value with parentheses.

  • Siebel CRM implies an AND operator between multiple conditions that use these comparison values. AND means that all the conditions must be met for the statement to evaluate to true.

  • LIKE and NOT LIKE allow you to use wildcards. For example, LIKE Smith%, or NOT LIKE Sm%th%.

You must use the following requirements for the database:

  • Any value that you define for a LIKE, IN, NOT IN, or BETWEEN operator in the Value field of the Conditions list of the Workflow Policies view must be in a format that the RDBMS supports.

  • The IN, NOT IN, and BETWEEN operators require you to use the format that the RDBMS supports. For example:

    • IN ('a', 'b', 'c') or IN (1, 2, 3, 4)

    • BETWEEN 'A' and 'B'

    • BETWEEN 1 and 10

  • If your implementation uses an MS SQL Server database, and if you define a Workflow Policy condition on a LONG column, then you can use only the following operators on this column:

    • IS NULL

    • IS NOT NULL

    • LIKE

    • NOT LIKE

You must manually make sure you use the correct format. The Process Designer passes the BETWEEN clause to the RDBMS. It does not confirm format, except for date and time. For date and time fields, the Process Designer converts the date and time columns to the following format:

month/day/year
hour:minute:second