Skip to main content
(Distributed) (Distributed) Important! A document set cannot be transferred to a different processing stage in parts — it has to be moved in its entirety. When determining the requirements for transferring the document set to the processing stage and the routes for transferring the batch out of the stage, FlexiCapture will use statistics gathered for the entire document set. Batch processing order is specified for each of the Batch Types. When a batch is created, its type is specified and the batch is processed in accordance with the settings for this batch type. If no Batch Types are created, all batches will be processed using the <Default Settings> configured beforehand (Project → Project Properties…, Workflow). The batch processing settings are configured on the Workflow tab of the Batch Type Properties dialog box. (Standalone) Processing settings:
  1. (Standalone) (Standalone) Skip verification and data verification if percentage of characters that need verification is equal or less than - If the percentage of highlighted characters is lower than specified in the (Standalone) % per document field, the (Standalone) Data verification and (Standalone) Verification stages will be skipped.
  2. (Standalone) For documents to be exported automatically, select the (Standalone) Enable auto export option on the (Standalone) Export tab of the Document Definition properties dialog box.
(Distributed) You can set a deadline by which the batch must be processed. To do this, click the Set Time Limit… button and specify the time when you need the batch to be completely processed. In the Warn in field, specify when a warning should be displayed informing the user that the time allotted for the batch is running out. If you leave this field empty, the warning will be displayed automatically. The specified deadline and the status of the batch will be displayed in the (Distributed) Expires on and (Distributed) Status columns of the list of batches on the Project Setup Station and the list of queued tasks on the Verification Station. (Distributed) The following workflow modes are available: (Distributed) Simple, (Distributed) Advanced, (Distributed) Unattended, (Distributed) for Web Capture station, and (Distributed) Advanced for Web Capture station.
(Distributed) The (Distributed) Simple mode includes the following stages: Scanning, (Distributed) Rescanning, (Distributed) Recognition, (Distributed) Data verification, (Distributed) Document assembly check, (Distributed) Verification, (Distributed) Batch integrity check, (Distributed) Export confirmation, (Distributed) Exceptions, (Distributed) Export and (Distributed) Processed.(Distributed) You can specify the following processing options:
  1. (Distributed) (Distributed) Process entire batches
    • (Distributed) If this option is selected, the entire batch is processed (i.e. the batch will not be forwarded unless all of its documents are processed).
    • (Distributed) If this option is not selected, each document from this batch is sent to next stage as soon as it is processed.
  2. (Distributed) (Distributed) Skip verification and data verification if percentage of characters that need verification is equal or less than - the document will be sent for verification only if there are errors or if the number of highlighted characters is higher than the one specified in the (Distributed) % per document field.
    (Distributed) Note: If you selected (Distributed) Always for any field in the Field Verification settings, the document will be sent to verification under any circumstances.
  3. (Distributed) Use separate stages for:
    • (Distributed) (Distributed) Rescanning
    • (Distributed) (Distributed) Data verification
    • (Distributed) (Distributed) Document assembly check
    • (Distributed) (Distributed) Verification
    • (Distributed) (Distributed) Batch integrity check
    • (Distributed) (Distributed) Export confirmation
    • (Distributed) (Distributed) Exceptions
(Distributed) All stages except (Distributed) Verification are optional.
Creating separate verification stages divides the verification stage into substages, each handled by its own Operator. Thus, each Operator will be responsible for only one job: data verification, document assembly check, etc.
If all of the above stages are handled by one Operator, he/she will have to do all the tasks in turn: take the document from the Document Assembly Check stage, check the assembly, take the data from the data verification stage and verify them, etc.
You can also use web-stations for all stages, except the (Distributed) Rescanning stage. For this, in the Allow web-stations column select a checkmark next to corresponding stage. Data Verification will be executed in the Data Verification or Verification web-station, other stages will be executed in the Verification web-station.
(Distributed) The (Distributed) Advanced mode allows you to configure complex workflow schemas. In this mode you can both edit base stages and create custom stages.(Distributed) (Distributed) Note: There is a time delay between the time (Distributed) Advanced workflow settings apply in the (Distributed) Project Setup Station and when they are displayed in the (Distributed) Verification Station.(Distributed) The (Distributed) Advanced schema consists of the following base stages:
  • (Distributed) (Distributed) Exceptions
  • (Distributed) Scanning
  • (Distributed) (Distributed) Rescanning
  • (Distributed) (Distributed) Recognition
  • (Distributed) Unattended Processing
  • (Distributed) (Distributed) Data verification
  • (Distributed) (Distributed) Verification
  • (Distributed) (Distributed) Document assembly check
  • (Distributed) (Distributed) Batch integrity check
  • (Distributed) (Distributed) Export confirmation
  • (Distributed) (Distributed) Export
  • (Distributed) (Distributed) Processed
(Distributed) Select the stages to be included in the workflow schema. All stages except Scanning and (Distributed) Processed are optional.(Distributed) To change the sequence order of stages, use the (Distributed) Move Up and (Distributed) Move Down buttons on the right. For stages, which cannot be executed earlier or later, the corresponding buttons are greyed out.(Distributed) For each stage, the maximum number of documents a task can contain is specified in the (Distributed) Documents Per Task column. To change the number of document per task for a stage, click on the number and enter a new value.(Distributed) (Distributed) Note: In the (Distributed) Batch integrity check and (Distributed) Processed stages, batches are processed in their entirety and not divided into tasks, so, for these stages, the number of documents per task cannot be changed.(Distributed) The base type for each stage is specified in the Base Type column. The base type indicates the type whose base settings were used when creating the stage.(Distributed) For each stage, you can view and edit its properties. To open a stage properties dialog box, select a stage and click the (Distributed) Edit… button on the right. For details, see Editing Stage Properties.(Distributed) Apart from base stages, you can also create custom stages to be included in the workflow schema. Custom stages can be based on stage tools and allow you to create stages of the same base type but with different stage properties.(Distributed) To add a stage, click the (Distributed) Stage… button on the right. In the window that will open, select a base stage on whose basis a new stage will be created and specify the stage properties. The new stage will be added to the schema. For details, see Creating Processing Stages.(Distributed) To delete a custom stage, select the stage and click the (Distributed) Delete button on the right.(Distributed) If transfer to the stage is conditional, the stage is marked with the icon. If documents are always admitted to the stage, the stage has the icon.(Distributed) (Distributed) Note: During verification, you can check the classification and document assembly results without having to verify the data. To do this, create a (Distributed) Verification stage, click the (Distributed) Field Set tab, and make sure that the (Distributed) Selected fields column is empty. Note, however, that if at least one field is selected, its data will be displayed on the data form awaiting verification.
(Distributed) In the (Distributed) Unattended mode, the documents are processed and exported without Operator intervention. If processing errors occur, the unrecognized image can be saved in a dedicated folder (this is specified on the Export tab) and the successfully processed documents will be automatically exported. In this mode, batches are processed in their entirety.
(Distributed) For Web Capture Station, workflow can be configured using the (Distributed) for Web Capture station and (Distributed) Advanced for Web Capture station modes.
(Distributed) In the (Distributed) for Web Capture station, you can specify the condition under which documents are routed to verification. If the option (Distributed) Skip verification and data verification if percentage of characters that need verification is equal or less than is selected, documents will be sent for verification only if they contain errors or if the number of highlighted characters is higher than the one specified in the (Distributed) % per document field.
(Distributed) The (Distributed) Advanced for Web Capture station mode similarly to the (Distributed) Advanced mode allows you to configure complex workflow schemas by editing existing stages and adding new ones. As compared with the (Distributed) Advanced mode, the (Distributed) Advanced for Web Capture station has the following restrictions:
  • (Distributed) The set of predefined stages cannot be modified.
  • (Distributed) A custom stage can be based on the (Distributed) Automatic stage only.
  • (Distributed) In stage properties, only the stage name, exit routes, and enter conditions are allowed for editing.
(Distributed) (Distributed) Note: When switching from the (Distributed) Advanced for Web Capture station mode to the (Distributed) Advanced mode and vice versa, all specified settings are reset to default.