Knowledge Base

Article ID: 1308 | Category: Project Setup | Type: FAQ | Last Modified: 8/27/2015

Advanced Workflow

Description

How can I use the Advanced workflow in my FlexiCapture project? What are the differences between it and the other workflow types? How to setup the Advanced workflow?

Solution

The advanced workflow schema was introduced in version 10 and is the primary means of customizing FlexiCapture.

First of all, let's examine the workflow schemas currently available in FC 10.

  1. The Simple workflow schema offers a set of stages that can be turned on or off. It also allows you to skip verification. This workflow schema can be used to handle simple processing scenarios.
  2. The Unattended workflow schema is, as the name suggests, fully autonomous, and has no configurable settings.
  3. For Web Capture is a workflow schema which allows a Web Capture station to function as a front office. This schema has no customizable features other than the option to skip verification.
  4. The Advanced workflow schema offers a comprehensive set of customization options that cover everything users are likely to need. This workflow schema allows creating custom stages and defining rules that govern how documents are routed between them.
  5. The Advanced for Web Capture station mode similarly to the Advanced mode allows you to configure complex workflow schemas by editing existing stages and adding new ones. As compared with the Advanced mode, the Advanced for Web Capture station has the following restrictions:
                      The set of predefined stages cannot be modified.
                      A custom stage can be based on the Automatic stage only.
                      In stage properties, only the stage name, exit routes, and enter conditions are allowed for editing (for more information about routing rule see this article).

Let’s take a closer look at the Advanced schema.

Here is an example of a customized workflow:

As you can see, this workflow contains several custom stages. It was used in a project that had a complex double verification scheme that utilized regular verification stations.

The advanced schema provides five important capabilities.

1.      Adding stages
There are three types of stage: interactive, automatic, and custom.
Automatic stages run on a Processing Station and do not require any input from an operator.
The Unattended Processing stage combines recognition and export.
Example:
Let’s assume that we need to pre-recognize the first page of a document, then use the results to select the Document Definition that will be used to recognize the entire document. To accomplish this, we’ll need to add a second recognition stage.

Automatic stages typically involve scripts. To create one, select Automatic in the Create Processing Stage dialog box.

This stage provides access to all documents in a task, making it ideal for any checks and changes.
For example, you can populate the registration parameters using the values of fields in your documents.
The script can run for the whole batch or independently for each document.
The method can be selected from the drop-down list:

Interactive stages require input from an operator. These stages are typically used to include Verification Stations and Data Verification Stations (including Web stations) in a project. An interactive stage can be used, for example, for double verification. For double verification, you need two Verification Stations and interactive script stages which will record and compare verification results. Double verification is natively implemented for Data Verification Station:

Custom stages are mainly used for interactions through the Web API. Any batches routed to this stage will not be routed anywhere else until a command from the Web API is received. Custom stages can be used as a temporary storage mechanism for processed documents and documents that have already been exported (documents can be called back). This type of stage is rarely used.

2.      Ordering stages
As you can see in the first screenshot, stages can be arranged in any order as may be required by your project. In the 4th release a stage linking feature was added: a document is not  able to skip linked stages.

3.      Specifying routing rules
You can specify conditions that must be met before a document enters or leaves a certain stag. Routing scripts can also be used. For more information about routing rule see this article.

4.      Limiting the number of documents in a task
Everything is simple here:

Limiting the number of documents can be useful in many cases, but is mainly used to optimize processing and verification.     

5.      Restricting which Document Definitions may be used
There is an option to choose Document Definitions that will be used in a specific stage (see screenshot above).

In the AdvancedWorkflow.rar archive you can find 2 sample projects:

534 people think this is helpful.
Was this information helpful to you?