- 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
Assembling documents
How to correct assembly errors
- Incorrect page order
There may be too few or too many pages, or document pages may not arranged in the correct order. To correct such errors, you can use your mouse to move the page both within a single document and from one document to another.
Pages of several documents can be merged into a single document as follows: - Highlight documents to be merged (use Ctrl-Click to select several documents);
- Right-click and select Merge from the shortcut menu.
To split pages in a document and to place each one of them into a separate document:
- Highlight the document in which you want to split pages;
- Select Split from the shortcut menu.
- Incorrect recognition of a multipage document.
If a multipage document is recognized as a collection of one-page documents, this means that the Document Definition has been correctly applied only to the first page. To fix the error, you need to group the faulty pages into one section: - Check the order of the pages in the document (see "Incorrect page order" above), making sure the pages belong to the same document.
- Select the pages that belong to the same section (e.g. all pages with tables).
- Right-click the selection and then click Group into Section on the shortcut menu.
The grouped pages will now be recognized as a multipage document.
- If the Document Definition requires verification of key fields for the correct assembly of pages, the values of the key fields will be displayed under the image of each page:
- highlighted in gray in the event of a match
- highlighted in red in the event of a mismatch
Key fields may not match if they have been recognized or filled in incorrectly. Check the values of the key fields. If the values of the key fields still do not match, the respective pages most likely do not belong to the same document. If the order of pages is wrong, find pages with identical key fields and assemble them into documents as described in "Incorrect page order" above.
How documents are assembled
Documents are assembled automatically or by an explicit user command. The assembly principle can be described when creating a Document Definition for multipage document processing or when creating custom processing stages in the Batch Type Properties dialog box. These assembly types differ in when they are performed and in what kind of documents they can access.
Specifics of assembly described in Document Definition properties
- Runs:
- when selecting a command: Tools → Refresh Assembly
- after analyzing/recognizing a set of documents; in this case, the assembly includes only documents involved in analysis/recognition
- Both standard assembly rules and a Document assembly script can apply.
- Documents with locked boundaries will not be combined with any other documents but can be added into document sets. If the boundaries of a document set are locked, automatic document assembly will be performed within the locked boundaries.
- No assembly is performed if the Document Definition is not matched. For example, if all pages of the batch are annex pages, no assembly is performed.
- The order of pages cannot be changed during the assembly.
Specifics of assembly described in batch type properties
- Runs when documents enter the corresponding stage.
- Described by processing scripts.
- Allows you to move and delete pages and documents.
The Operator's task is to identify and correct possible document assembly errors.
Assembly errors can be corrected most conveniently in the page outline mode that gives the user a good view of page images and the documents to which they belong. You can switch to this mode by clicking the button.
Note: You can change the scale of page outlines to view details by holding down the Ctrl key and turning the scroll wheel.
When creating a Document Definition, you need to configure a document assembly rule (i.e. the order and number of recurring document sections). You can also configure an assembly verification based on the values of key fields: in this case the values of key fields must be identical on all pages of the document.
Note: The order of sections will not be checked if the Disable sections order check option is selected on the Assembly tab when creating the Document Definition. The program will still check to make sure that all the sections are present in the document, but the order of the sections will be ignored.
Documents with assembly errors will be marked with . An error description will be provided beneath the name of the Document Definition.
Locking document boundaries
Document boundaries are locked when:
- Images are separated into documents at the import stage.
- Assembled documents are sent to their intended destination.
- Pages or documents added into a document using a drag-and-drop operation.
- The Match Document Definition... command is executed.
- The IsExcludedFromAutomaticAssembly flag of a document is set to true by a script that is allowed to edit the document.
- The Operator clicks the Lock Document Boundaries command on the shortcut menu.
Document boundaries are unlocked when:
- The Operator clicks the Unlock Document Boundaries command on the shortcut menu.
- A document is split using the Split command.
- The IsExcludedFromAutomaticAssembly flag of a document is set to false by a script.
Documents or document sets with locked boundaries will have the icon next to them in the Bound column (in list view) or next to their page thumbnails (in thumbnail view).
02.03.2021 8:10:42