ILINX 6.X Database Lookup IXM

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.

Like almost all other database lookup modules, ILINX’s IXM Database Lookup module can perform a simple SQL Select statement to return values for the Batch Profile or document fields based on a Where clause. The Select statement is written in such a way to not only identify the database table column to return, but also identifies the Batch Profile or Document Field to place the returned value. As an example a simple database lookup may be required in an Invoice processing application to lookup the PO Number entered in by the user to both verify the PO exists and to return certain values about the PO Number from the database table. In this case a table exists with a lot of information that can assist the end users to properly process this invoice for this PO.


However, this same Database Lookup IXM can be used in a different location in the workflow to update a single table’s columns. In the example below the IXM is updating an ILINX Content Store database table with a fixed string value that identifies where in the workflow the document is currently located. Other field values in the ILINX Content Store database table are updated from the current Document fields. This allows end users to perform an Imaging search and know if the invoice is being processed and where in the process it is currently located.


These two examples show the power of the ILINX Database IXM.

Next time I will provide some examples of how other of these IXM’s can be configured and placed into a workflow to provide the kind of electronic routing and processing of documents that allows users to perform their work with better accuracy, more efficiency and less frustration.

Chris Hillenburg
Sr. Systems Engineer
ImageSource, Inc.