Use Local Drive / Share for export

Use the procedure in this topic to configure the Local Drive / Share export channel. When you select Local Drive / Share, processed documents and extracted data are exported to a local drive or network share.

Before you begin

Before configuring the Local Drive / Share export channel, we recommend that you complete the following steps:

For users with OPMT and Azure deployments, an on-premise Integration Server installation is required. Also, ensure that the Integration Server has access to the destination path.

For more information on installing the on-premise Integration Server, refer to the Tungsten TotalAgilityDocAI Studio Administrator's Guide.

Procedure

From the ribbon, select  Steps.
Select the Export tab.
From the Export channel list, select Local Drive / Share.

Configure the following settings.

Setting	Description
Destination path	The file system path where documents should be saved. You can provide a static path (for example, C:\Export\ProcessedDocs or \\NetworkShare\Documents) or select a variable containing the path by clicking the variable selector icon. Secure server variables are supported. The path must be accessible by the Core Worker Service account. If the destination path does not exist or the service account lacks write permission, the job is suspended with an error message.
Unzip on save	Select this checkbox to extract the zip file contents at the destination. When selected, the ZIP is extracted at the destination, and the ZIP is then deleted, leaving only the loose files. When cleared (default), the ZIP is saved as-is without extraction.
On filename collision	Select the behavior when a file with the same name already exists at the destination. Choose from: Overwrite: Replaces the existing file with the new file. (Default: Selected) Rename: Creates a new file with an incrementing number appended until a free name is found. Suspend: Suspends the job with an appropriate error message indicating the file collision.

Setting

Description

Destination path

The file system path where documents should be saved. You can provide a static path (for example, C:\Export\ProcessedDocs or \\NetworkShare\Documents) or select a variable containing the path by clicking the variable selector icon. Secure server variables are supported.

The path must be accessible by the Core Worker Service account.

If the destination path does not exist or the service account lacks write permission, the job is suspended with an error message.

Unzip on save

Select this checkbox to extract the zip file contents at the destination. When selected, the ZIP is extracted at the destination, and the ZIP is then deleted, leaving only the loose files. When cleared (default), the ZIP is saved as-is without extraction.

On filename collision

Select the behavior when a file with the same name already exists at the destination. Choose from:

Overwrite:: Replaces the existing file with the new file. (Default: Selected)
Rename:: Creates a new file with an incrementing number appended until a free name is found.
Suspend:: Suspends the job with an appropriate error message indicating the file collision.

A green check appears next to Export to indicate that it is activated and configured with no errors. A red circle indicates the configuration is incomplete (for example, if the destination path is empty).

The document export activity is added to the DocAI Studio workflow.

Once export is configured, Save  your solution.

Once your solution is published, documents are exported to the specified location during production.

Next steps

Optional. Configure other export settings.
Optional. Configure other steps.
Optional. If you complete the configuration, publish your solution.