- Introducing ABBYY FlexiCapture
ABBYY FlexiCapture architecture
- System requirements
- ABBYY FlexiCapture servers
- ABBYY FlexiCapture stations
- Processing stages and queues
Using scripts in ABBYY FlexiCapture
- Specifics of scripts written in .Net languages
- External assemblies
- Script editor
- Object model
Scripts for customizing processing stages
Types of scripts
- Script rule
- Autocorrection script
- Export script
- User script (custom action)
- Document assembly script
- Custom recognition script
- Stage rule
- Processing scripts
- Data set update script
- Data set validation scripts
- Document classification script
- Batch created
- Batch deleted
- Batch parameter change
- Batch structure change (page added/page deleted/document added/document deleted)
- Pages moved
- Batch opened/closed
- Batch integrity check
- Document parameter changed
- Document state changed
- Export completed
- Script that is run after rule checks
- Before matching
- Field verification request
- Sample scripts
- Internal names of recognition languages
- Types of scripts
Scripts for processing interface events
- On Document Closed
- On Project Closed
- On Activate Document
- On Field Control Activate
- On Return From Task
- On User Command
- On Field Control Deactivate
- On Closing Document
- On Task Close
- On Closing Project
- On Region Change
- On Task Window Mode Changed
- On Open Document
- On Task Window Create
- On Task Reject
- On Region Control Draw
- On Task Send To Stage
- On Text Field Validating
- Event handlers
- User script for Web Verification Station
Application Programming Interface (API)
- About the ABBYY FlexiCapture Application Server Web Services API
- Using the Web Services API of the ABBYY FlexiCapture Application Server
- Batch types
- Licensing tickets
- Document Definitions
- Processing requests to the Application Server
- Working with files
- API Methods
- Web Services Mobile API
Web Services for user account management
- Data types
- User management
- Group management
- Tenant management
- Managing permissions
- Examples of API Use
- Integrating Web Stations into third-party systems
- Configuring additional settings and customizing Web Stations
- About ABBYY FlexiCapture Custom Reports
- Creating custom reports
- Processing of objects
- Access control
- Event Log
- Examples of custom reports
- Supported recognition languages
- Fonts for correct characters rendering
- Supported text types
- Supported barcode types
- Supported input formats
- Export file formats
- Date formats
- Alphabet used in regular expressions
- Protecting Document Definitions and additional modules
- Third-party technologies
- Technical support
- End-User License Agreement (EULA)
Processing stages and queues
Documents are processed in several stages, with certain routines performed at each stage, either automatically or assisted by the Operator. The stages have a specific order and to go through a particular stage the documents must first go through the previous stages. On the whole, the following stages are required: adding images, recognition, verification, export.
At each stage, a processing queue is formed (see Task creation for details). A queue represents a set of tasks in the corresponding stage. As the processing progresses, the documents are moved from the first queue (Scanning) towards the last queue (Processed).
In the case of large processing volumes, the verification stage can be subdivided into smaller stages, each processed by its own Operator. In other words, you can create separate stages for data verification, verification, document assembly checks, and export confirmation.
Some of the processing stages are required, while the other are optional. Whether the stage is required or not depends on the selected workflow scheme.
Tasks from this stage are processed on the Scanning Station. In the Simple mode, the entire batches are processed.
Tasks from this stage are processed on the Scanning Station. The task is always sent to the Operator who did the scanning.
Recognition is done automatically on the Processing Station. In the Simple mode, the entire batches are processed.
- Document assembly check
The tasks from this stage are processed on the Verification Station. If no separate document assembly stage is specified in the settings, batches or documents with errors are processed in the verification stage.
- Data verification
The tasks from this stage can be processed on the Data Verification Station or on the Verification Station.
If no separate stages are specified, all tasks with document assembly errors, data errors, and rule errors are sent to the verification stage. The tasks from this stage are processed on the Verification Station.
- Batch integrity check
Batches with integrity errors are sent to this stage. Integrity check options are specified by scripts when setting up a batch type. The tasks from this stage are processed on the Verification Station.
- Export confirmation
A stage which ensures greater accuracy of the captured data. A batch or document is exported only after the Operator confirms that it is suitable for export. The tasks from this stage are processed on the Verification Station.
The tasks from this queue are processed on the Processing Station.
Processed documents are sent to this stage.
Documents with errors are sent to this stage after automated processing. Besides, Operators may also send documents to this stage if for some reason these documents cannot be processed.
If some of the batch documents are sent to Exceptions, the whole batch is excluded from processing and is not exported.
To achieve the maximum efficiency during processing large amounts of documents, batches can be splitted into separate tasks.
Tasks are created from documents on the Application Server when documents arrive in the stage and become available for processing. Tasks are formed depending on the specified workflow settings.
In the Advanced mode, the number of documents in the task can be specified in the stage properties.
If the Wait for all documents of a batch option is selected, documents will be sent to the next stage only when all of them are processed in the current stage.
In the batch integrity check stage, access to all documents of the batch is required, so in this stage the Operator always receives the whole batch.
It is also possible to send to the stage the tasks that were created earlier, e.g. when sending documents to a stage from the Verification Station provided that the Create task option was selected in the Send To... dialog box.
Note: For tasks created in earlier versions of ABBYY FlexiCapture or tasks that dropped out of processing, new tasks must be formed in the Administration and Monitoring Console.
The workflow mode is specified in the Batch type settings.