Operators

You use operators to build conditions that compare attribute values to a static value or another attribute.

The following table describes the operators available in Oracle CRM On Demand Marketing.

Operator	Description
Equal To	The profile attribute value must be the same as the value provided in the condition.
Not Equal To	The profile attribute value must be different from the value provided in the condition.
Exists	The profile attribute has a value. The value for the attribute might be valid or invalid.
Not Exist	The profile attribute does not contain a value (the value is NULL or blank).
Is Less Than	The profile attribute value must be less than the value provided in the condition.
Is Less than or Equal To	The profile attribute value must be less than or equal to the value provided in the condition.
Is Greater Than	The profile attribute value must be more than the value provided in the condition.
Is Greater Than or Equal To	The profile attribute value must be more than or equal to the value provided in the condition.
In List	The profile attribute value must be available in the list of values provided in the condition. The different values in the list must be separated by a comma.
Not In List	The profile attribute value must not be available in the list of values provided in the condition. The different values in the list must be separated by a comma.
Contains	The profile attribute value contains the text or characters provided in the condition.
Does Not Contain	The profile attribute value does not contain the text or characters provided in the condition.
Starts With	The profile attribute value must start with the text or characters provided in the condition.
Ends With	The profile attribute value must end with the text or characters provided in the condition.
AND	The filter condition includes contact records in the list only when both conditions related to this operator are true.
OR	The filter condition includes contact records in the list when records match either or both conditions. Note: OR conditions must be listed first in the sequence of conditions.

Guidelines for Using Operators

This topic provides guidelines for using operators. Consider the following:

• Equal To/Not Equal To. These operators perform precise, exact case-sensitive matching. Therefore, Denver is not the same as denver. You can use Contains and Does Not Contain to target variable values that are entered as a comma-separated character strings.

• Exists. This operator returns all records where a value is present for the chosen attribute. This does not mean that the value present is valid or formatted correctly. The Exists operator can help determine how many contact records in your database have a value for a particular attribute, such as Industry.

  
  

  Tip: A best practice is to use this operator to make sure that a value for Email exists for each contact in your target list for outbound email programs.

  
  

• Not Exists. This operator returns all records where no value is present for a particular attribute. This operator is not synonymous with a negative value, such as No, False, or zero (0). For example, if you enter a condition, such as Email Permitted is Not Equal To No, this condition excludes any contact records that are blank.

• In List/Not In List. These are powerful operators for selecting multiple values from a list of valid entries for an attribute. For example, if you are building a target list to include contact records for five countries in Europe only (Germany, Italy, France, United Kingdom, and Spain), you might want to use the In List operator for the Country attribute, and select the five target countries while pressing the Ctrl Key. This method is much more efficient than building a separate condition for each country. If you are creating a list to download contact records for all countries in Europe except Norway, Finland, and Sweden, use the Not In List operator to select these countries from the list while pressing the Ctrl key.

• Contains/Does Not Contain. You can use these operators to build conditions with inexact or incomplete matching. You can enter a character string for your value or multiple values separated by commas. To define a list condition to find all contact records for a certain target account, it is more efficient and accurate to search by email domain rather than company name, which might be entered in a variety of ways.

You can also use the following auto-generated conditions in Oracle CRM On Demand Marketing as operators:

• Within past XX days. Enter the number of days within which the profile attribute value was last modified.

• Restricted by. A list of values for a particular restriction.