Skip to main content
To configure data export, in the Document Definition editor select Document Definition → Export Settings. You can set up multiple export profiles in a Document Definition, so you can export processing results to several file formats and destinations.

Export profiles

On the Export Destinations tab, you see the configured export profiles and the following information about each:

Export conditions

You can export data only when certain conditions are met, for example only documents with rule errors, only documents without them, or only documents where a field has a particular value. Set conditions under Export if these conditions are true. To condition export on errors, select an option from the Documents condition dropdown list: To condition export on a field value, select Field condition, and in the Export Conditions dialog box, select a field, select the condition that triggers export, and specify the field values. The field value conditions are: To add a value, type it and click Add; to remove one, select it and click Delete. To add an empty value, click Add without typing anything; it appears as <Empty value>. A value can be added only once. Export conditions can involve text fields (including fields with continued regions), barcodes, and table columns. They cannot involve checkmarks, checkmark groups, fields with multiple instances, images, or table cells.
If an export condition involves a table column, the data is exported if at least one cell in the column meets the condition.
You can use export conditions to choose where processed documents are stored. For example, you can put documents into different folders based on a field value (such as Subsidiary), or export documents with rule errors to a specific folder (such as Failed).

Fine-tune export

The set of fields to export is generated from the field properties (whether Export field value is selected). When you set up an export profile, you can remove fields from that set, and fields from the same set can be exported to different destinations. Select Export Settings, and then click Edit → Options → Setup Fields Mapping to open the Field Mapping dialog box and set the destinations.

Redact information when exporting documents

When exporting data to graphical formats (including PDF), you can redact fields that contain sensitive information.
1

Enable redaction

In the export profile settings, select Redact sensitive data on images.
2

Open the redaction dialog box

Click Select Fields to Redact.
3

Choose the fields

In the All fields section, select a field and click the add button to move it to the Redacted fields section. Use the add-all button to move all fields at once.
In a document set where one document is included in several sub-documents, the fields of that document appear only once in the Select Fields to Redact dialog box. The sub-documents show a broken-chain icon to indicate that they contain fields that are not displayed because they come from another document.

Automatic export

You can export documents automatically. In the Document Definition properties dialog box, click Export Settings and select Enable auto export. Processed documents are then exported automatically, without an Operator clicking an export button. For test batches, this option is off by default. Automatic export works only if the Document Definition states the exact number of pages in documents. It does not work if certain pages can occur several times, if the number of sections is given as an interval (including 0-1), or for documents submitted for verification.
When documents are exported automatically, batch integrity is not checked, and a warning is added to the task log.

Save results to the file system

You can save captured data and document images to the file system. For an absolute path, you can specify a local path or a UNC network path. (Standalone) For a relative path (only a subfolder specified), the subfolder is created in the Export subfolder of the project folder. To use a different location, specify an Export root path in the project settings; new subfolders are then created relative to it. The root path can be a local or a UNC network path. (Distributed) For a relative path (only a subfolder specified), the data is exported to a file storage location on the Application Server, and you use the API to get the results.