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:
ILINX Export supports the Microsoft Cluster Service (MSCS) for High Availability. MSCS provides the ability for a group of independent servers to be managed as single system. ILINX Export is a Cluster-Unaware Service and relies on the Generic Service Resource Type to manage services as a cluster.
When you install ILINX Content Store or ILINX Capture, generally it is assumed you install the ADFS (Active Directory Federation Services) authentication provider and the ILINX Application on the same server. However, in the case that you are already using ADFS on another server for authentication, it is possible to use that separate instance of ADFS.
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.
At some point there is going to be a need to convert an Imaging Systems image files from one format to another format when moving to a new Imaging system. ILINX® Import can be used to handle the conversion.
This is it. The final installment. The end. Our tunnel of light leading us to the promise land of perfect integrations with Serendipitous Cerebration as our Virgil guiding us through the Malebolge of Content Management.