Revalidation
During revalidation, the Gateway engine requests that validation be performed on an inbound transmission or batch (ICL) that has already been validated at least once.
When revalidation begins, the condition field of the selected unit of work is changed to the validating state for the duration of the revalidation process. After revalidation, the condition and overridable fields associated with the selected transmissions or batches (ICLs) are updated with new values if necessary. The condition state change can be used to add additional workflow events for revalidation to the Transaction Server Scheduler.xml file. For example, configuring an event to call the transmission acknowledgment task during revalidation.
Each time validation is performed on a transmission or batch (ICL), a new version of validation results for the transmission or batch (ICL) is created and the version number of the results is incremented. The contents of each new version of the validation results is determined by the error code and error categories configuration that the user defined for revalidation. The initial validation results and the validation results for all of the revalidation requests are available to be displayed using the rejects and warnings report page.
Starting revalidation
- The user accepts transmissions that are in the rejected and overridable states.
- The user releases transmissions or batches (ICLs) that are in the pending state.
- The activation of an open business day that has batches (ICLs) that are in the captured, but not loaded,
state. Use the
Enable business day activation revalidationproperty to control whether revalidation occurs when an open business day is activated.
Skipping revalidation
- The user runs the accept without revalidation action, which does not perform revalidation on the selected transmissions and batches (ICLs).
Configuring the error codes and categories for revalidation
- Revalidate
- Indicates whether an error code that recurs during revalidation is to be included in the revalidation result or ignored. When this property is set to yes for an error code that has recurred during revalidation, the error is included in the latest revalidation result and reported. When the property is set to no, the error is not included in the latest revalidation result and Gateway logs that the error code was suppressed during revalidation.
- Error categories to preserve during revalidation
- A list of error categories for which the initial validation results from ingestion are preserved when revalidation is performed. When revalidation is finished, Gateway copies the initial validation results for these categories into the latest revalidation results. Use commas to separate the names of the error categories to be preserved. For example: Image compliance (IQA), Image compliance (TIFF), Image compliance (IIA), Image correction (TIFF).
- Duplicate Detect
- Image Compliance
Even though the revalidate property is set to yes for all of the Image
Compliance error codes, they are not actually included in the revalidation results in the reference
implementation. Gateway copies the results from the initial validation into the latest
revalidation results because the reference implementation configuration has the Image
Compliance
error categories in the list of error categories to preserve during revalidation. For example, the value for
the error categories to preserve property in the reference implementation is Image compliance (IQA),
Image compliance (TIFF), Image compliance (IIA), Image correction (TIFF).