Context Validation

The context validation node has tasks that represent each level. The final task represents the error codes to use for a failure. The order of the tasks is important. Validation rules are evaluated in the configured order with the first task having the highest precedence. Changes to the order result in a modification of the hierarchy of rules. The last task contains the error codes to apply. An XML sample is shown here:

<?xml version="1.0"?>
<nodeDescriptor name="NachaContextNode" type="ValContextNode">
  <tasks>
    <task name="NachaOriginatorContextTask"/>
    <task name="NachaDepositorContextTask"/>
    <task name="NachaProductContextTask"/>
    <task name="NachaContextTask"/>
    <task name="NachaRecordTypeTask"/>
  </tasks>
</nodeDescriptor>

If the NachaRecordTypeTask has an entry with a record type of 0, an SEC code of an asterisk, and an addenda type of 0, it enables additional validation in the context validation node. If these fields are set, the context validation node verifies that the combination of record type, SEC code, and addenda type is valid for the record. Invalid records are assigned an error code of unknown record.

Enable this additional validation if records with an incorrect addenda type should be rejected. For records with incorrect addenda, the content validation node will not be able to find any rules and will not report validation errors for the other fields in the record.