Chapter 3 Defining rules and queries 47
Defining rules
Constant syntax (constant|<string>)
This syntax allows you to generate a value to be placed into a field or class.
Integration Engine does not perform a database lookup in this case; instead, the
specified value is used. This syntax is useful if you populate some fields with
known values when you create a request.
Integration Engine attempts to assign a data type to the constant. To force the value
to be a string, put quotes around the value. If not, Integration Engine tries to
determine if the value is a date or a number before it defaults to a character value.
Table 3-2 provides examples of how to use the constant syntax.
Precedence syntax (<{rule}> <{rule}> <{rule}>)
This syntax allows you to set the precedence for a set of rules. Each set of curly
brackets (
{}) encloses a field mapping rule that Integration Engine evaluates
independently. The first rule to return a response value is considered the value to
be returned.
Table 3-3 provides examples of how to use the precedence syntax.
Table 3-2: Constant syntax examples
Example Results
constant|Hardware
Returns the character string Hardware.
constant|15
Returns the number 15.
constant|”15”
Returns the character string 15.
Table 3-3: Precedence syntax example
Example Results
{PO Number}
{Notification Number}
{constant|Unknown
Value}
The PO Number is returned if not null.
If the
PO Number is not found, the
Notification Number is returned if not null.
If the
Notification Number is not found, the
Unknown Value string is placed in the field.
