Output: Overview

After documents are sorted, and data is extracted and verified, DOCUMENTS sends the data to a target system by writing the data to a file.

You can specify output methods for documents, compound documents, and batches. Batch output is saved in the folder you specify in the General output settings. Document output can be saved in a subfolder, specified in the output activity, that is identified by the document specification name. Note that output from documents that are members of a batch are also saved to subfolders.

You can choose whether to generate a separate output file for each batch, compound document, or document:

If you specify an output method in the document specification, you get one output file per document.
If you specify an output method in the compound document specification, the output is per batch or compound document.
This overrides the output method (if any) defined in the document specifications that are included in the compound.
If you specify an output method in the batch specification, you get one output file per batch. (Note:Keep batch together must also be selected on the Structure tab.)
This overrides output method (if any) defined in the document specifications or compound document specifications that are included in the batch specifiation.

See instructions.

Important: Most output methods actually send document data to a target system. However, you can also use an output method to check documents and change their document status based on certain criteria. If you are using such a method, for example for handling rejected documents, it is important to place this type of method high in the list, or even first, so that they are applied before documents actually leave the system.

When do rejected documents proceed to output?

Data available for documents:

Document data:
- Document specification name – the name of the document specification that the document is based on
- QueueName – the name of the queue, if any, that the document belongs to.
- ID – the document DBID
- Create date and time – the system date when the document was created, scanned, or read from file
- Change date and time – when the document was last modified
- BatchNumber – the number of the batch that the document was in
- BatchID – the Batch ID string of the batch that the document was in
- NoOfAppendices – how many appendices the document has
- AutoPageGroupStatus
- IsSeparator
- Pages Count – the number of pages included in the document
- Fields Count – the number of fields included in the document
- Input type – 1 if the document was imported from an image file and 2 if it was scanned
All pages as own records:
- IsAppendix
- PageNoInDocument
- PageFlip
- HasPageName
- PageFileName
- OriginalFileName
- PageNoInFile
- PageFileType
- PageFileTypeVariant
- ImprinterString
- SheetNoWithinBatch
All fields as own records:
- Name
- FieldNo
- Value
Email source data (if input from email):
- From
- To
- CC
- Subject
- Message
Specification data:
- ID – the DBID for the document specification
- Create date and time
- Change date and time
- Name
- Scanning specification data:
- Name – the name of the specification
- ID – the DBID for the specification
- ScannerName – the name of the scanner and model
- DPI
- Brightness
- Vendor
- Contrast
- Bit depth
- Description
- Driver

Data available for compound documents:

Data available for batches:

You use the Administration module to:

Specify an output method determining the content, layout, and format of the data in the file.
Define an output activity in a production task.

You use the Production module to:

Run the production task that contains the Output activity. This results in output.

After output is complete, data cannot be sent to output again.

Output data