...
If an associated unit with a measurement variable is specified, the corresponding Item values must reflect the values using the associated units specified. Refer to ItemRef/@UnitsItemOID. Proper conversion of units must be done as part of the range check.
| Example |
|---|
| title | RangeCheck: Value must be positive |
|---|
|
| Include Page |
|---|
| RangeCheck - Positive Value |
|---|
| RangeCheck - Positive Value |
|---|
|
|
| Example |
|---|
| title | RangeCheck: Value IN (list) |
|---|
|
| Include Page |
|---|
| RangeCheck - 1, 3, or 5 |
|---|
| RangeCheck - 1, 3, or 5 |
|---|
|
|
| Example |
|---|
| title | RangeCheck: Value between 18 to 65 inclusive |
|---|
|
| Include Page |
|---|
| RangeCheck - Low-High |
|---|
| RangeCheck - Low-High |
|---|
|
|
...
When using FormalExpression a range check can represent anything (e.g., one-sided or multisided checks). These type of checks must not provide CheckValue or Comparator as they would all be expressed in the FormalExpression itself. The FormalExpression takes the value of the ItemData element and returns a boolean value which is the result of the expression. Multiple FormalExpressions can be provided if each has a different Context attribute, allowing the same expression to be represented in forms appropriate to multiple systems. Multiple different expressions, with different meanings, must be represented as separate RangeChecks
| Example |
|---|
| title | Range Checks using FormalExpression |
|---|
|
| Include Page |
|---|
| RangeCheck - Formal Expression |
|---|
| RangeCheck - Formal Expression |
|---|
|
|
...