XML documents resemble regular, paper-based documents in the Verify module. The process of verifying them is basically the same, but there are a few important differences:
The document image is for display purposes only.
No field rectangles are drawn on the image, nor is it possible to draw on the image yourself. The field guide is deactivated.
It is not possible to reroute, reject, or manually change the sender/receiver for XML documents in Verify. You need to use Save to Optimize on the Document menu so that you can do that in the Optimize module.
These Verify options/actions do not apply to XML documents and are therefore not available:
(See an illustration of the flowchart in a separate window.)
When a job that contains XML documents is started, the image for the first document (using the PDF that was created when the document was identified) is displayed in the same way as any other document. If similar documents for the sender have been processed in the system previously, you can also approve them in the same way as any other document if they are OK. However, if the sender or receiver needs to be adjusted, or if field values need to be remapped to other XML elements, the document must be sent to Optimize by selecting Document > Save to Optimize.
When you save a document to Optimize, you are asked if you want to reprocess the document (see 1 in the flowchart illustration). What you select depends on whether you feel you can approve the document or not and if you have multiple documents in Verify that belong to the same XML document definition or profile. You should normally select Yes so that any subsequent documents that belong to the document definition are automatically given Scanned status awaiting the optimization of the document definition. See "Document can be approved" below for different scenarios when you may want to select No.
This first scenario would normally be used if you only have one or very few documents in Verify that belong to the same XML document definition or profile that you want to optimize. The errors are such that the document can be approved, but you still want to optimize the definition for it/them. In other words, you feel the document is OK as is or you want to check with the sender such that you feel it can be approved, for example:
Select No when asked about reprocessing. The document will not be reinterpreted after the document definition has been optimized.
Complete fields.
Approve the document.
The document is sent to Transfer and the document definition is sent to Optimize and has status 99.
However, if you have multiple documents in Verify that belong to the same XML document definition or profile, and they need to be optimized, you may still want to select No. (More information.)
If you feel the document cannot be approved:
The document is given Scanned status and will be reinterpreted after the XML document definition or profile has been optimized. The XML document definition is sent to Optimize and has status 99. Any subsequent documents that belong to the XML document definition/profile are also automatically given Scanned status and will be removed from Verify until the document definition/profile has been optimized and the documents have been reinterpreted.
Verify skips to the next document.
Processing XML documents using COLLECTOR: Overview
Adding additional important information to the PDF image for an XML document