From Simple Wiki

Back to Batch Processing Stages

At the end of batch processing, SimpleIndex exports images and index data to the destinations configured in the Job Settings.

Export Settings[edit | edit source]

Starting the Export[edit | edit source]

For a Pre-Index batch, export happens automatically after processing.

For batches with manual review, you must use the Save Index button to initiate the export. You will be prompted to export only when all required fields have been filled in and you click Save Index on the last file.

Export Steps[edit | edit source]

The following workflow steps are executed during the Export process.

Document Presence Auditing[edit | edit source]

If Document Presence Auditing is enabled, the batch will be checked for required documents before the export begins. A dialog will be shown if any are missing.

See Document Presence Auditing

Create Export Files[edit | edit source]

If multi-page files are used, the first step is to combine files in the current batch with the same index settings into multi-page files.

See File Naming Schema

Imprint Files[edit | edit source]

If the Imprint option is selected, automatic watermarking of TIFF and PDF files will occur at this point in the process.

See Imprinting

Move Files[edit | edit source]

When multi-page files are used, the last step of the export process is to move files from the temporary processing folder to the Output folder.

Depending on the Existing Files setting, pages from the current batch will replace existing files or are appended to the start or end of the document.

If the Add Bookmarks to PDF Files option is selected, pages are inserted into the matching bookmarked sections in any existing file.

By performing the multi-page file export and move operations in two steps, SimpleIndex greatly improves performance when exporting to large, multi-page files on a network drive.

Custom Code Export[edit | edit source]

In the Advanced File Output Settings you can select Custom Export and enter the path to a .NET Framework dll class module and function path in the format Path|Namespace.Classs|Function


The function prototype is:

public string SampleExport(string ExportFilePath, string[] FieldValues)

This function will be called for each exported file in the batch, after pages have been combined and saved to the Output folder, using the file naming schema defined by the job file.

Sample code in C# .NET Framework 4.8 can be found in the Custom Code Integrations subfolder of the Sample Jobs.

The Sample Jobs folder also contains a job file called E - Read Invoices with Custom Autofill and Export.sic that demonstrates the use of the Custom Export feature.

Related Knowledge Base Articles[edit | edit source]