You can use a variable as a condition's cell value. However, there are constraints:

  • Either all of the rule cell values for a condition row contain references to the same variable (with the exception of dashes), or none of the rule cell values for a condition row reference any variable.
  • Only one variable can be referenced by various rules for the same condition row.
  • Logical expressions in the various rules for the same condition row should be logically non-overlapping.
  • A condition value that uses a colon, such as A:B, is not valid.

Derived value sets are created by accounting for all logical ranges possible around the variable.

Note: The issue with using multiple attributes in a condition row (or attributes mixed with literals) is a warning, not an error; as such, analysis functions are not available.

The following Rulesheet uses the Cargo Vocabulary to illustrate the valid and invalid use of variables. Note that the Vocabulary editor marks invalid values in red.



Derived values when using variables

The following tables abbreviate the attribute references shown in the illustration.

Table 1. Rulesheet columns
Conditions 1 2 3 Derived Value Set
A.maxCV < C.v > C.v C.v {< C.v, > C.v, C.v}
A.maxCV <= C.v > C.v {<= C.v, > C.v }
A.maxCV < C.v > C.v {< C.v, > C.v, C.v }
A.maxCV < C.v {< C.v, >= C.v}

Incorrect use of variables

Table 2. Rulesheet condition f: Attempt to use multiple variables
Conditions 1 2 3
A.maxCV < C.v > FP.c.v C.v
Table 3. Rulesheet condition g: Attempt to mix variables and literals
Conditions 1 2 3
A.maxCV < C.v 5 10..15
Table 4. Rulesheet condition h: Attempt to use logically overlapping expressions
Conditions 1 2 3
A.maxCV < C.v <= C.v C.v