Skip to content

RAW - NON NEGATIVE

Description

The NON NEGATIVE validator checks if an item is a negative number, and if so, it throws a violation. It is designed to ensure that numeric data points do not contain negative values, allowing only positive numbers or zero. This validator is particularly useful for scenarios where only non-negative values are acceptable.

Supported Data Types

The NON NEGATIVE validator supports all numeric data types, including:

  • Integer
  • Decimal
  • Double

Config Location

The configuration for the NON NEGATIVE validator is defined within the <rawDPValidator> element of a schema data point. This section is crucial for specifying the logic that the validator will execute to determine if the data item meets the specified criteria.

Config Requirements

For the NON NEGATIVE validator, the <config> element is not required. This means that the validator can be applied directly to numeric data types without the need for additional configuration parameters.

Example Config

Below is an example of a NON_NEGATIVE raw validator configuration. This validator checks if the current item is not negative, and throws a violation if the condition is not met.

1
2
3
4
5
<dataPoint name="QUANTITY" dataType="INTEGER">    
    <rawDPValidators>
        <rawDPValidator name="CHECK_NON_NEGATIVE" execPriority="10" entity="NON_NEGATIVE"/>
    </rawDPValidators>
</dataPoint>

Example Results

Consider a scenario where the NON_NEGATIVE validator is applied to a data item named "QUANTITY" with a value of 5. Since the value is positive, the validator will pass successfully without throwing a violation.

On the other hand, if the value of "QUANTITY" were -3, the validator would throw a violation because the value is negative, which is not acceptable according to the validation criteria.

Common Mistakes

  • Ensure that the data type of the data item being validated is numeric. The NON NEGATIVE validator is designed to work with numeric data types only.
  • Remember that the NON NEGATIVE validator does not require a <config> element, so ensure that the validator is correctly applied to the data item without additional configuration.
  • Verify that the entity attribute of the <rawDPValidator> element is correctly set to "NON_NEGATIVE" to apply the NON NEGATIVE validation logic.