- Introducing ABBYY FlexiCapture
- Installing and running the program
- ABBYY FlexiCapture architecture
-
Program settings
- ABBYY FlexiCapture Setup
- Multitenancy
- Creating a project
-
Document Definitions
- Creating fixed Document Definitions
- Creating Document Definitions for semi-structured documents
- Document Definitions without automatic fields extraction
- Document sets
-
Document Definition fields
- Text entry fields
- Checkmarks
- Checkmark groups
- Barcodes
- Pictures
- Tables
- Field group
- Service fields
- Index fields
- Link to an existing field
- Fields without a region
- Creating a field with a non-rectangular region
- Fields with several instances
- Fields with several regions
- How to change a field name
- Copying, moving, deleting fields
- Exclusion of a region from recognition
- Document Definition Wizard
- Editing and publishing a Document Definition
- Creating Document Definitions
- Document Definition properties
- Properties of a Document Definition section
- Rule validation
- Export settings
- Configuring data presentation in the document window
- Testing Document Definitions
- Localizing a Document Definition
- Classification
- Field extraction training
- Operating a configured project
-
ABBYY FlexiCapture for Invoices
- Features of ABBYY FlexiCapture for Invoices
- How to capture invoices
-
How to set up an invoice capture project
- Country and language settings
- Connecting vendor and business unit databases
- Data export settings
- The status of documents in ABBYY FlexiCapture for Invoices projects
- Training ABBYY FlexiCapture for Invoices
- Rules
- Capturing additional invoice fields
- Purchase Order Matching
- Enabling additional program features for operators
- Using multiple Document Definitions
- Editing invoice processing settings in XML files
- Updating the Document Definition for invoices
- Tax systems
- Specifications
- Capturing receipts
- Capturing purchase orders
- Using NLP to process unstructured documents
- ABBYY FlexiCapture interface
-
Appendix
-
Using scripts in ABBYY FlexiCapture
- Specifics of scripts written in .Net languages
- External assemblies
- 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
-
Event handlers
- 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
-
Objects
- IActionResult
- IAssemblingError
- IAssemblingErrors
- IBatch
- IBatchCheckResults
- IBatchItem
- IBatchItems
- IBatchTypeClassifier
- IBatchTypeClassifierResult
- IBinarizationParams
- IBoxedBoolean
- ICharacterParams
- ICharactersParams
- ICheckmarkGroupValue
- ICheckmarkValue
- IDataSet
- IDataSetQuery
- IDataSetRecord
- IDocument
- IDocuments
- IDocumentExportResults
- IDocumentsExportResults
- IDocumentDefinitionInfo
- IDocumentDefinitionInfoArray
- IEditablePictureObject
- IExportFieldsToRedact
- IExportImageSavingOptions
- IField
- IFieldRegion
- IFieldRegions
- IFields
- IFlexiCaptureTools
- ILocalContrastParams
- IMatchedSectionInfo
- IMatchingInfo
- IPage
- IPageClassificationResult
- IPages
- IPictureObject
- IPictureObjectsInfo
- IPrincipal
- IPrincipals
- IProcessingCallback
- IProject
- IProperties
- IProperty
- IPropertyModificationInfo
- IRecordCheckResult
- IRecordset
- IRect
- IRects
- IRoutingRuleResult
- IRuleContext
- IRuleError
- IRuleErrors
- IRuleTag
- IRuleTags
- IScriptBinaryAttributes
- IScriptDefinitionContext
- ISectionDefinitionInfo
- ISectionDefinitionInfoArray
- IShadowsHighlightsParams
- IStageInfo
- IUserAttachment
- IUserAttachments
- IUserSessionInfo
- IValue
- IVARIANTArray
- TAssemlingErrorType
- TBatchItemType
- TColorToFilter
- TExportFieldType
- TExportType
- TImageCompressionType
- TPageClassificationType
- TPdfAVersion
- TPdfDocumentInfoType
- TPdfTextSearchAreaType
- TPrincipalType
- TProcessingPriority
- TPropertyType
- TRuleErrorType
- TStateType
- Sample scripts
- Internal names of recognition languages
-
Types of scripts
-
Scripts for processing interface events
-
Event handlers
- 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
-
Objects
- IBoolean
- IBoxedFieldControl
- IDocumentEditor
- IDocumentItem
- IDocumentItems
- IDocumentsCollection
- IDocumentsWindow
- IDrawContext
- IErrorControl
- IErrorControls
- IErrorsWindow
- IFieldControl
- IFieldRegionControl
- IFieldRegionControls
- IFormWindow
- IImageWindow
- IMainMenu
- IMainWindow
- IMenu
- IMenuItem
- IPageControl
- IPageItem
- IPageItems
- IPagesCollection
- IPoint
- ISelection
- IShellRational
- IShellRect
- IShellRects
- ITaskWindow
- ITextEditor
- IToolbar
- IToolbarButton
- IToolbars
- TCommandBarType
- TCommandID
- TDockingType
- TDocumentState
- TErrorType
- TSelectionType
- TTaskWindowMode
- TTextSize
- TUserRole
- TWorkWindowType
-
Event handlers
- User scripts for the Web Verification Station
- Creating a machine-readable form
- Hot keys
- Additional options
- Description of Processing Server commands
- ABBYY FlexiCapture sample projects
- Supported recognition languages
- Supported classifier languages
- Fonts for correct characters rendering
- Supported text types
- Supported barcode types
- Supported input formats
- Processing PDF files
- Export file formats
- Date formats
- Alphabet used in regular expressions
- Patents
- Third-party technologies
- Glossary
- Technical support
- How to buy ABBYY FlexiCapture
- End-User License Agreement (EULA)
-
Using scripts in ABBYY FlexiCapture
Running the program
- in Administrator mode: go to Start → All Programs → ABBYY FlexiCapture 12 and select ABBYY FlexiCapture Administrator Station.
- in Operator mode: go to Start → All Programs → ABBYY FlexiCapture 12 and select ABBYY FlexiCapture Operator Station.
Important! Before running the program, ensure that:
- The scanner is connected to the PC and powered on. If your scanner has not been connected, refer to the scanner user guide. For the scanner to operate correctly, you must power on the scanner before you power on the PC.
- A protection key has been installed on your PC. You cannot run the program without it.
The server and processing station services are started automatically. The stations and the Processing Server may be either running or stopped. The processing Server is started from the Processing Server Monitor. The Processing Stations are started by the user or automatically by the Processing Server (if the corresponding settings have been selected).
To monitor and control the operation of the Processing Server and the Application Server, select the following items from the Start menu:
- Start → All Programs → ABBYY FlexiCapture 12 Servers → Processing Server to start the Processing Server Monitor.
- Start → All Programs → ABBYY FlexiCapture 12 Servers → Administration and Monitoring Console to open the main page of the console in your browser and control the Application Server
ABBYY FlexiCapture stations are started by selecting the corresponding menu items from Start → All Programs → ABBYY FlexiCapture 12 Stations.
Registry keys that control the launching of the application
You can use the following registry keys (in Shell\StartUp) to control how the application is launched:
These keys are not created in the registry by default. If required, the Administrator may add these keys into the registry of the user's operating system.
The registry keys can be overridden by the corresponding command line launch parameters.
Command line launch parameters
The following parameters can be used to launch the application via the command line:
FlexiCapture.exe [/Station:(Admin,Operator)] [/Project:"path to project"] [/Batch:"batch name"] [/ProhibitChangePath]
- [/Station:(Admin,Operator)] - defines whether the application runs in Operator or Administrator mode. If no mode is specified, a dialog box is displayed upon application launch which prompts the user to select the desired mode;
- [/Project:"path to project"] - sets the project that is opened automatically when the application is launched;
- [/Batch:"batch name"] - sets the batch that is opened automatically when the application is launched;
- [/ProhibitChangePath] - prohibits changing the batch and project that open automatically in Operator mode.
The following parameters are used to start stations from the command line:
"path to FlexiCapture.exe" [/Station:(Setup,Validator,RemoteValidator,Verificator)] [/Project:"path to project"] [/Batch:"batch name"] [/ProhibitChangePath]
- path to FlexiCapture.exe - for example, ?c:\Program Files (x86)\ABBYY FlexiCapture Stations\FlexiCapture.exe?
- [/Station:(Setup,Validator,RemoteValidator,Verificator)] - specifies the station (Project Setup station, Verification Station, Remote Verification Station, or Data Verification Station respectively). If no mode is specified, the program will prompt you to select a mode at startup;
- [/Project:"path to project"] - sets the project that is opened automatically when the application is launched;
Note: The path to the project can be viewed in the corresponding station in the following registry branch:
[HKEY_CURRENT_USER\Software\ABBYY\FlexiCapture\12.0\Shell\MRU_List.
The key List contains the list of projects that were opened in the station. From the value of this key, copy the path to the project on the server: http://<ApplicationServer>/<guid>/<project name>. Note that, in command line parameters, the project name must be enclosed in quotes. - [/Batch:"batch name"] - sets the batch that is opened automatically when the application is launched. You may need to open a particular batch in the Project Setup station. Other stations operate with queues;
- [/ProhibitChangePath] - prohibits changing the batch and project that open automatically in Operator mode.
For example, to open the Invoices_Eng project from the server in the Verification station, the following command can be used:
"C:\Program Files (x86)\ABBYY FlexiCapture Stations\FlexiCapture.exe" /Station:Validator /Project:http://127.0.0.1/84506f53-8ca7-4095-9444-d6af76e0c192/Invoices_eng
02.03.2021 8:10:42