Skip to main content
The Verification Station allows more complex checks than the Data Verification Station. Besides verifying the data, the station allows its Operator to process problem batches or documents, correct assembly errors, apply data rules, and check batches for integrity. The station can work in a local or a remote network (over the Internet); for more details, see Remote Verification Station. You can authenticate using a login and password, Windows authentication, or SSO authentication (for details on setting up SSO, see Single Sign-On authentication).

​
Operator roles

Data Verification Operators, Verification Operators, and Senior Verification Operators can operate the Verification Station. The tasks an Operator can see and process depend on the role selected when logging onto the station. The Administrator can create additional processing stages and the corresponding queues. Whether an Operator can access these queues depends on the Operator’s role and on the required permissions for these queues, which are defined by the Administrator.
The list of available roles depends on the Operator’s access permissions. If only one role is available, the list of roles is not displayed.

​
Task queues

The following queues are available on the Verification Station.
The document processing parameters (that is, separate queues) are specified for batch types or for the entire project if no batch types are used.

​
Get and view tasks

To perform a task, select the queue in the list of queues and click . To receive tasks automatically, click or select Task → Automatic Task Receive. On the Verification Station, you can preview a task’s documents in Details and Thumbnails view modes. In Details view, only the documents of the active task are displayed.

​
Work with batches

In addition to the task queues, the Senior Verification Operator can access a list of batches from the projects they have permissions for. These and other Operator permissions are assigned from the Administration and Monitoring Console. To open the list, click Batches on the View menu or click the batches button on the toolbar. Batches view shows each batch’s confidence level, page and document counts, batch type, and more. Select a batch to:
  • Send it to any processing stage.
  • Set its priority.
  • Assign a user to verify it.
  • Add a comment.
This lets you gather documents from one batch across different queues and send them to a single stage. Double-click a batch to open it and work through its documents (verify data, correct rule and assembly errors, and so on). Select one or more documents to send them to a processing stage and create a separate task for them.

​
Send documents to other stages

To mark selected documents for sending to Exceptions, Rescanning, or any processing stage, select the corresponding item from the Task menu or the document shortcut menu. In the dialog box, enter a comment or pick one from the Recent Comments list (the 10 most recent comments). To reuse and edit a comment, select it, click OK, and edit it in the input field. You can delete a comment you rarely use. The comment list is stored in the registry at HKCU\Software\ABBYY\FlexiCapture\12.0\Shell\Stages\RecentStageCommentList. Comments are separated by commas. A literal comma in a comment is written as /,, and a line break as //. A multiline comment is displayed as a single space-separated line. Comment text can contain any characters. All FlexiCapture users sharing one Windows session on a local Verification Station share this list. For documents sent to Rescanning, you can also specify the Operator the task will be assigned to. By default, the Operator who scanned the document is selected. If this Operator does not have the necessary permissions, or the images were imported from a Hot Folder, the user Any is assigned as the Scanning Operator. After the task is closed, documents marked for sending are sent to the corresponding processing stages.
When sending batches to stages, make sure that the documents of the batch do not belong to already created tasks. Otherwise, empty tasks will be created. You can check whether a document belongs to a task in the Task ID column.