Logical Operations and Comparisons

When defining a condition, you can include logical operators, comparison operators, and the data map entry state operator. These operators can be used to define special conditions in a conditional, whileLoop, or dataService business rule component, or to define an executionCondition in any type of business rule component. Each operation results in a value of true or false, and you can nest operations to produce complex expressions.

Important! Content in a business rule is case sensitive. This includes business rule component names, attributes, and values.

About the syntax documentation

Logical Operators

You can use the following logical operators.

Operator	Description
and	The result is true if the results of all child operations are true.
nand	The result is true if the result of at least one child operation is false.
or	The result is true if the result of at least one child operation is true.
nor	The result is true if the results of all child operations are false.

The following is the syntax for logical operations that can be used when defining a condition.

<and|nand|or|nor failOnFalseCondition="false|true">

<falseLogMessage>Text written to log if condition is false</falseLogMessage>

<trueLogMessage>Text written to log if condition is true</trueLogMessage>

</and|nand|or|nor>

Comparison Operators

You can use the following comparison operators.

Tip: Comparison of DATE values is supported using the equals, greaterThan, lessThan, and notEquals operators.

Operator	Description
equals	The result is true if the left and right values are equal. This comparison is case sensitive.
notEquals	The result is true if the left and right values are not equal. This comparison is case sensitive.
equalsIgnoreCase	The result is true if the left and right values are equal. This comparison is case insensitive.
notEqualsIgnoreCase	The result is true if the left and right values are not equal. This comparison is case insensitive.
greaterThan	The result is true if the left value is greater than the right value. This comparison is case sensitive.
lessThan	The result is true if the left value is less than the right value. This comparison is case sensitive.

Important! Specifying the type is required for each value being compared. Depending on the type, that value can be interpreted as a literal value or as a data map entry name (key).

Note: If you use an empty string as a value in a comparison, it is interpreted as a null value A value that is unknown. A null value is different from an empty string or a zero value. instead. You can test for an empty string by using a mapState operator with stateCheck="NOT_EMPTY" and inverseResult="true".

Note: A comparison operator cannot have child business rule components.

The following is the syntax for comparison operations that can be used when defining a condition.

<falseLogMessage>Text written to log if condition is false</falseLogMessage>

<trueLogMessage>Text written to log if condition is true</trueLogMessage>



<left type="KEY|LITERAL" valueType="STRING|INTEGER|BOOLEAN|NUMBER|BINARY|DATE">

<value>Value_to_compare</value>

</left>



<right type="KEY|LITERAL" valueType="STRING|INTEGER|BOOLEAN|NUMBER|BINARY|DATE">

<value>Value_to_compare</value>

</right>

Data Map Entry State Operator

You can use the data map entry state operator to determine whether a specified data map entry exists and whether it contains a value.

Note: When using a mapState operator, you must specify a the name of a data map entry as the value for key. A data map entry state operator cannot have child business rule components.

Operator	Description
mapState	The result is true if the data map entry specified by key has the state specified by stateCheck and the result is not inverted. If the result is inverted, then the result is true if the data map entry specified by key does not have the state specified by stateCheck.

Operator

Description

mapState

The result is true if the data map entry specified by key has the state specified by stateCheck and the result is not inverted.

If the result is inverted, then the result is true if the data map entry specified by key does not have the state specified by stateCheck.

The following is the syntax for a data map entry state operation that can be used when defining a condition.

<falseLogMessage>Text written to log if condition is false</falseLogMessage>

<trueLogMessage>Text written to log if condition is true</trueLogMessage>

</mapState>

Syntax Tips

Additional information is available about the following items.

dataType or valueType

The type of data that the component returns or to which it refers. The default value is STRING.

Additional details for specific types of components.

For a parameter, the dataType specifies the data type of the parameter value. For a parameter in a dataService business rule component, the result map for a JDBC data service can be represented as a string.
For a comparison in a condition, the valueType specifies the data type of a value to be compared.
A dateTime business rule component always returns a value with a data type of STRING regardless of the dataType specified.
For an exportData business rule component, only STRING and BINARY are supported for the dataType element.

Value	Description
STRING	A text string. Any number or date/time included is treated as text.
INTEGER	A signed integer value.
NUMBER	A signed decimal value.
BOOLEAN	A value of true or false.
BINARY	An array of bytes.
DATE	A date/time value stored in one of the following formats: Epoch time The number of seconds since 00:00:00 UTC on 1 January 1970, not including leap seconds. yyyy-MM-dd hh:mm:ss

failOnFalseCondition

This attribute of a logical operation or a comparison specifies whether the job should fail if the value retrieved from the data map does not match the literal value returned by the logical operation. The default value is false.

Value	Description
true	If the value retrieved from the data map does not match the literal value returned by the logical operation, then the job fails.
false	If the value retrieved from the data map does not match the literal value returned by the logical operation, then the job does not fail due to this condition.

inverseResult

For a data map entry state (mapState) operator, whether to invert the result of the comparison of the state of the data map entry specified by key and the value of stateCheck. The default value is false.

Value	Description
true	If the state of the data map entry specified by key and the value of stateCheck are equivalent, then the mapState operation returns false. Otherwise, the operation returns true.
false	The result of the comparison is not altered.

key

stateCheck

For a data map entry state (mapState) operator, the value to compare to the state of the data map entry specified by key. The default value is EXISTS.

Value	Description
EXISTS	The data map entry exists in the data map. Note: It is possible for the value to be an empty string or to never have been specified.
NOT_NULL	The data map entry exists in the data map and a value has been specified for it. Note: It is possible for the value to be an empty string.
NOT_EMPTY	The data map entry exists in the data map and the value is not an empty string.

Value

Description

EXISTS

The data map entry exists in the data map.

Note: It is possible for the value to be an empty string or to never have been specified.

NOT_NULL

The data map entry exists in the data map and a value has been specified for it.

Note: It is possible for the value to be an empty string.

NOT_EMPTY

The data map entry exists in the data map and the value is not an empty string.

type

Required. Whether to interpret a value for comparison as a literal value or as a data map entry name (key) containing the value for comparison.

Tip: This functionality is comparable to that of the resolveValue attribute of parameters and xmlData business rule components but uses different syntax.

Value	Description
KEY	Interpret the value specified by the value element as the name of a data map entry that contains the value for comparison. Resolve the data map entry to its value at run time.
LITERAL	Interpret the value specified by the value element as a literal value for comparison.

value

valueType

Tip: For assistance with a business rule that you have created or to have Loftware create business rules for you, contact Loftware's Professional Services Group.