When the job starts, ENTRANCE first checks the database to see if there are XML document definitions that have been optimized. Documents associated with these are reinterpreted first.
After COLLECTOR receives and processes XML documents, those documents are ready to be interpreted. Interpreting XML documents consists of:
Importing document data.
Strictly speaking, interpretation of document data—in the way that paper or image documents are interpreted—does not occur with XML documents. The Interpret module imports the data directly into the database. However, you must still run an Interpret job with the appropriate settings.
Document sorting.
The Interpret module uses the same method of sorting documents as with other documents.
Document classification.
When XML documents are received by email, you must use the <SYSTEM> document profile to differentiate between general expense (GE) and purchase order (PO) documents. (This applies to all documents, not just XML ones.)
Tip: Run Interpret as a Windows service to process XML documents automatically.
The documents are converted to SMXL so that ENTRANCE can recognize them and a PDF image is created. After an XML document is interpreted, by default the original file, with the SMXL version and the PDF file, is moved to the folder that was specified in the COLLECTOR job. What happens next depends on whether the sender matches one that is already in the COLLECTOR and ENTRANCE databases.
(See an illustration of the flowchart in a separate window.)
When the Interpret job starts, it checks the ENTRANCE database for documents from document definitions that have been optimized. Those have priority and are re-interpreted first. See 1 in the flow chart.
If available, COLLECTOR then begins retrieving new XML documents (see 2 in the flowchart). How files are processed depends on the format and whether or not the sender is known (see 3 in the flowchart).
If the sender is known (that is, it matches a sender in the COLLECTOR database and is found in ENTRANCE's master data, if used), it is interpreted and sent to Verify. The original file, the SXML version, and the corresponding PDF are all saved in the identified folder specified in the job.
If it is found to be correct, it can be approved and sent to Transfer.
If it is not found to be correct, it can be saved to Optimize for optimization.
However, if the sender is known to COLLECTOR but is not found in ENTRANCE's master data, the document is marked as unidentified and must be fixed and reinterpreted.
If the sender is unknown to COLLECTOR, the document definition is automatically sent to Optimize and marked with status 99 for easy recognition when the document definition is optimized. However, documents from unknown senders can be displayed in Verify anyway (that is, not automatically sent to Optimize) if desired.
Any documents that are associated with the document definition are blocked in the job and given Scanned status. They will be reinterpreted once the document definition has been optimized.
The document definition is optimized and any documents associated with it are reinterpreted.