beautypg.com

Administrator's guide, Overview, Features – Kofax Export Connector 8.0.0 User Manual

Page 5: Kofax values {document guid, Sharing data among kofax capture export connectors

background image

Kofax Export Connector 8.0.0 for Documentum Content Server Administrator's Guide

5

Administrator's Guide

This document gives you information about installing Kofax Export Connector for

Documentum Content Server, which exports document images, OCR full text files, PDF

documents, eDocuments, and data to a Documentum Content Server repository.

Overview

With Kofax Export Connector for Documentum Content Server, batches are processed based

on export settings. Documents and index data are exported to your repository based on the

settings defined during export setup.

In a multiuser installation, the export process typically runs on an unattended workstation

that polls for available batches at regular intervals. The process may be configured to run

during off-hours to avoid any impact to the performance of Kofax Capture, Kofax Express, or

the network system.

Features

This section describes the major export connector features.

Kofax Values / Documentum Content Server Properties
This export connector provides an easy-to-use interface for linking Kofax Values to

Documentum Content Server document properties and folder properties. Examples of Kofax

Values include document index fields, folder index fields, batch fields, and text constants.

Kofax Values {Document GUID}
The Kofax Value {Document GUID} is a unique value that can be used for index fields and

export values.

Sharing Data Among Kofax Capture Export Connectors
The Kofax Capture Export Connector Information Interchange feature is useful when more

than one export connector has been configured for a particular batch class and document class

combination.

The sharing of information is accomplished by allowing the export connectors to pass

information to other export connectors. The Kofax Values {Repository Document ID} is used

to store and retrieve the RepositoryDocumentID that will be used by the first invoked export

connector.

Therefore, the first export connector that runs can set this value, and subsequent export

connectors can read the same value.