Parts of a Search Specification

The following table describes some of the parts of a search specification.

Element Description

Comparison Operator

Compares the value in a field to a constant, or the value in one field to the value in another field. Siebel CRM allows the following operators:

  • = (equal to)

  • <> (not equal to)

  • > (greater than)

  • < (less than)

  • >= (greater than or equal to)

  • <= (less than or equal to)

The following is an example search specification that uses the greater than comparison operator:

[Revenue] > 5000

String Constant

You use double quotation marks to enclose the string constant. A string value is case sensitive. Uppercase and lowercase letters in a string constant must match exactly the string that the Siebel CRM record contains. The following is an example search specification that uses the COST LIST string:

[Type] <> "COST LIST"

Logical Operator

The logical operators AND, OR, and NOT negate or combine elements in a search specification. Siebel CRM ignores case in these operators. For example, and does the same operation as AND. The following is an example search specification that uses the AND logical operator:

[Competitor] IS NOT NULL and [Competitor] <>  "N"

Field Name

You use square brackets to enclose a field name in a search specification. The following is an example search specification that references the Conflict Id field:

[Conflict Id] = 0

LIKE Operator

The LIKE operator creates a text string search specification where the specification compares the value of a field to a constant, or compares the value of a field to the value of another field. A match on only the first several characters in the string is required. The LIKE operator uses the following wildcard characters:

  • * (asterisk). Indicates any number of characters.

  • ? (question mark). Indicates a single character.

The following is an example search specification that uses the LIKE operator:

[Last Name] LIKE "Sm*"

In this example, the Last Name values of Smith, Smythe, Smallman, and so on, causes the search specification to evaluate to TRUE.

Length

The search specification must not exceed 255 characters.