ILINX 6.X is an easy to configure and easy to use software package to scan, index, and provide workflow. The workflow steps are based on IXM (ILINX eXtension Modules) that are very similar to a programming language. There are several different types of IXM’s available out of the box. The following is a quick listing by name of the out of the box IXM’s:
By using the IXM’s, the designer of a workflow can have a batch move through single or multiple steps to perform any required task.
In addition to the IXM’s there can be actual code executed through a Client Side Extension or through a Server Side Extension. So there is little that cannot be accomplished using the ILINX Capture workflow IXM’s.
This week I would like to concentrate the discussion on a single IXM Database Lookup. The Database Lookup IXM is one of the most powerful when it comes to interacting with entities outside of ILINX. It not only allows ILINX to perform a database lookup and return column values to the Batch Profile or Document fields, but it also allows for the update of a database table’s columns. Continue reading →
Once ILINX Capture 6.0 is installed, you should find a subfolder under the install folder (c:\Program Files\ImageSource\ILINX Capture) named “Sample Code”. This subfolder contains a zip file that you can use to unzip the contents to a folder on your hard drive. You can then use the provided Visual Studio shell (Visual Studio Express 2013 for Windows Desktop is free) to open and code/de-bug/build the Server Side Extension. The files listed in the zip file are:
As you can see, there is a solution file that you can open in Visual Studio Express 2013 for Windows Desktop that will allow you to access the layout for each section listed. When you open this file you will get Continue reading →
Let’s say you want to route a batch in the ILINX Capture workflow depending on the value of a certain index. Maybe this is an AP solution and you want to route to a different queue based on document type. Here is the simple way to do that:
I ran into an interesting challenge with a customer and thought it might be something of interest to others. The challenge was in creating a way to have an entire batch of documents go through Advanced Capture processing and be returned to the input software, in this case ILINX Capture, as a single batch upon export.
Are you tired of separator sheets? Tired of wasted paper and countless hours of flipping through pages and inserting a barcode sheet at the start of a new document just to take it out after the batch is scanned or leave it in the batch and have more paper to store? Why not have the computer do the work for you? That’s the idea behind the Project Planner module in KTM. There is a standard separation functionality built into KTM that works very well on structured and semi-structured documents but when you have more complex separation rules the Project Planner component of KTM is what you need.
I have been working with the Kofax Capture product for over ten years now. To prove that, let me tell you the configuration on one of my first installs. I remember setting up a Bell and Howell 3338 scanner (you know, the one that required a cherry picker to get out of the box and on to the desk) with the Kofax KF board and Kofax Capture version 2.x. Ah yes, I look back fondly on the old days of deploying a scanner with the Kofax card and software. I know it has been out for a while now, but I recently started working with version 9 of Kofax Capture and I am pleased to say that they have finally addressed some of the Kofax gotchas that have been plaguing us for years.
For starters, they made client deployment 100% easier by creating the MSI package. I can’t tell you how many conversation I have had with client admins that go like this:
Me: No we don’t have a SMS or other type deployment package you can use, but you can make your own.
Client Admin: (Furrows brow) Huh?
I will be much happier when those conversations are a little less embarrassing. Now the workstations can be deployed using Microsoft SMS, Group Policy, IBM Tivoli, Symantec Altiris, HP Openview, or whatever deployment suite you use. Kofax has only tested SMS, but Continue reading →
With scanning software it is tempting to get carried away and create many different batch class configurations designed to be optimized for specific types of documents. The most common is when you see a batch class created for single page documents and another which uses exactly the same indexes and feeds the same application for multiple page documents. Often times the extra time spent separating the documents out into these multiple piles for input to the different batch classes offsets the time saved by the batch class optimization. In organizations which enact this you often find that the single page batch class has been abandoned as the workers tasked with document preparation, scanning and indexing come to the same conclusion. This is not an absolute but in general unless there are a large number of single page documents the extra batch class is not worth the effort. The follow up to this is when you do have one of these abandoned batch classes it should be deleted. It makes for less confusion for new employees being trained for scanning operations, and does away with wasted time spent on the non used batch classes being upgraded and tested during system upgrades.
Senior Systems Engineer