Third Party Extensions Kofax Image Products (in operation since 1985) is headquartered in Irvine, CA. In 1999, it was acquired by DICOM Group (DCM.L). The company manufactures and sells computer hardware, software, and services.
Kofax claims that their Products and Services help accelerate business processes by collecting paper documents, forms and e-documents, transforming them into accurate, retrievable information and delivering it into business applications and databases. (YT)
Integrating Kofax and Alfresco provides complete Content Management support including capture, management and publishing of Content. Kofax captures content from all kinds of sources usually via scanning & OCR. The captured information is then 'released' to Alfresco, for it to be managed in an ad-hoc manner or via pre-defined business processes.
The Kofax architecture provides a plug-in point for deploying a 'Kofax Release Script' which is responsible for mapping and transferring the information captured by Kofax to the destination application or database.
The intention is to provide the following capabilities in the first version of the Release Script.
Release Script Administration (Setup)
The following information will be captured via a UI Dialog allowing configuration of the Release script.
Alfresco Server Connection Details (username, password, repository instance)
Destination Alfresco Folder where Kofax captured information should be placed
Mapping of Kofax captured information (meta-data, tiff, ocr and pdf renditions) to Alfresco Content Model
Kofax Document Class -> Alfresco Content Type (Content or sub-type of Content)
Kofax Index Value (as extracted from document by Kofax) -> Alfresco Property (of appropriate data type)
Kofax Tiff, OCR or PDF document -> Alfresco Property (of binary data type)
Note that advanced configuration such as security policies to apply, versioning behaviour, workflows to start, sub-folders to create etc will be kept outside of the Release Script. The control of this behaviour is deferred to Alfresco rules on the destination folder where they can be managed centrally and shared across all import channels.
Connect to Alfresco (using supplied connection details in Administration dialog)
For each supplied Kofax documentï¿½
If document does not already exist in destination folder, create using Content Type as defined in Administration), otherwise update existing document
Apply appropriate Aspects (as defined in Administration dialog)
Set Property values (as supplied from Kofax using mapping defined in Administration dialog)
Set Content (as supplied from Kofax using mapping defined in Administration dialog)
Return new Content Id to Kofax providing cross-reference between systems
Commit or Rollback Transaction based on success or error
For each document that could not be processed (due to error etc)ï¿½
report error back to Kofax so that some form of quality control can take place
The Kofax interface point for Release Scripts is Microsoft COM based. This means itï¿½s natural for the release script to be implemented against Alfrescoï¿½s Web Services (repository, content and dictionary apiï¿½s) as they are accessible from any environment. The script will be implemented in .NET (C#). This is an approved and tested Kofax configuration.
One advantage of using Web Services is that the release script may be downloaded and easily deployed to Kofax without requiring the installation of other Alfresco dependencies.
Installation Environment Prerequisites
The Kofax Release Script for Alfresco has the following prerequisites: