Capture Blog

Newsletter for Kofax Users

Neal Fischer — Tue, 31 Jan 2012 19:40:00 GMT

Hershey Technologies welcomes the New Year with several exciting new features for users and managers affiliated with Kofax Capture software. We understand that change is a constant in our industry, with new operating systems, software product releases, evolving use of mobile devices and enterprise security issues are some to the topics Hershey Technologies technical support team is prepared to address!

How can I speed up the export of my custom export script?

Arjay Dohring — Fri, 19 Nov 2010 04:07:00 GMT

Your custom export is saving image files out to a folder and performs well when exporting to a local folder but is much slower when exporting to network storage. This problem increases dramatically as the number of pages in the multipage image file increase.

My batch class needs to support eDocs and use KTM but it won’t publish, what do I do?

Arjay Dohring — Thu, 18 Nov 2010 00:16:00 GMT

I have run into several scenarios where I needed my batch class to support eDocs and I needed to use Kofax Transformation Module. For example, I wanted to use the Kofax Capture Import Connector – Email, this requires that you set your batch class to allow import of eDocs. By default Kofax Capture will throw an error during publish if you set the batch class to allow eDocs and you include the KTM queues. This is for good reason as KTM will error if you try and run an eDoc through it.

Can I access index fields from Recognition Script?

Arjay Dohring — Thu, 18 Nov 2010 00:03:00 GMT

Not long ago I had a client that was using a barcoded coversheet to replace a previous version that required OCR. The client placed several values into the barcode with a delimiter and wanted them parsed out and placed into the appropriate index fields.

Recognition Script seemed like the most likely place to implement this little tidbit of code. Unfortunately I quickly found out that while I could parse the barcode into its separate values, Recognition Script only provides access to the index field its applied to. Therefore I had no access to the other index fields and could not set them.

Why do I have to install my workflow agent on every station?

Arjay Dohring — Wed, 17 Nov 2010 23:55:00 GMT

When using workflow agents with Kofax Capture it is best practice to deploy your workflow agent on every station in your Kofax Capture environment. This ensures that the workflow agent will be present and able to perform its function whenever needed. To enforce this best practice, Kofax Capture by default will through an exception and route your batch to Quality Control with an error status if it cannot load the workflow agent dll.

SharePoint Export Connector is not compatible with Item_Added event in a SharePoint event receiver

Tom Castiglia — Mon, 25 Oct 2010 21:47:00 GMT

Today we tested the SharePoint Export Connector with Kofax v9 with a document library in SharePoint 2010. This particular library included use of a custom SharePoint Event Receiver.