Validation version handling for the item level

Item level validation uses validation version numbering. As transmissions, batches (ICLs), segments, and transactions are loaded, they start with a validation version number of 0. Every time that a unit of work (UOW) is validated by Business Rules, the validation version number is incremented. Incrementing the validation version makes it easier to determine which errors and warnings still apply. For example, the most recent validation version contains all the errors and warnings that still need to be addressed. Business Rules revalidation includes only error codes that have the revalidate field set to yes.

The validation version number can also be incremented even though Business Rules is not called. The version can be updated anytime that errors are assigned or are resolved. Some examples of when the validation version number can be incremented without Business Rules are shown in the following list.

An error code is assigned in a PresentmentStatesEventHandler event stanza.: The validation version number is incremented when the error code is assigned and before the message is sent. Only the errors that are in the most recent validation version are the ones that are set in the stanza.
An applyUpdates request is received.: The validation version number is incremented when an applyUpdates request is received for a PresentmentUpdateBean and the update bean included setting validation errors. Only the errors that are in the most recent validation version are the ones that are set in the update bean.

Image validation is also a special case because its validation is not done during Business Rules processing. The image analysis results are evaluated only one time, which is during loading. Therefore, image quality errors and warnings are left in validation version 1 if they are not propagated by using revalidation. The following section describes how error codes can be propagated by using revalidation.

Propagating error codes by using revalidation

The following list describes how the error codes for specific components can be propagated by using revalidation.

Error codes that are assigned during ingestion and are related to the images must have a category that corresponds to Image Compliance, such as 5, 6, or 7. Any validation results that are caused by Image Compliance can be copied to the new versions if its error code is configured to be able to revalidate. Whether the validation results are copied is based on the rules in the following table.
Error codes that are assigned from Duplicate Detect have a category of 3. Any validation results that are caused by Duplicate Detect can be copied to the new versions if its error code is configured to be able to revalidate. Whether the validation results are copied is based on the rules in the following table.

The following table shows the rules that apply to propagating error codes by using revalidation.

Table 1. Validation rules
Component	Rules
Amount Keying	Business Rules validation is enabled. Every validation result that is caused by Duplicate Detect or Image Compliance are propagated to the next version. Business Rules validation is not enabled. No new version is created.
Duplicate Detect	Duplicate flag is turned on. All existing validation results are propagated to the next versions. Duplicate flag is turned off. The existing validation results, except the validation results that were caused by the original Duplicate Detect process, are propagated to the next version.
Image Review	Image is accepted. The existing validation results, except the validation results that were caused by the original Image Compliance process, are propagated to the next version. Image is rejected. No new version is created.
Payment Repair	Item is accepted. No new version is created. Item is rejected. A new version is created. Any existing duplicate and image errors are propagated to the next version.
Transaction Correction and Reconciliation	Business Rules validation is enabled. Every validation result that is caused by Duplicate Detect or Image Compliance are propagated to the next version. Business Rules validation is not enabled. No new version is created.