- 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
File naming options
File names and paths are generated automatically during export, based on the options specified by the user. File naming options can be specified both for data files and for image files.
Note: A file naming template for data files can be specified when exporting to files. A file naming template for image files can be specified when exporting to files, an ODBC-compatible database, SharePoint or image files.
Note: When working with document sets, the file naming options selected for original fields will also be used for index image fields.
Use the Destination and File Naming Template dialog box to specify file naming options and paths. Depending on the selected export type, click Edit... (to the left of the field with the file naming template) or File Naming Options... to open this dialog box.
In the View field, you can choose one of two ways to create a file naming template:
- Simple,
details
In this view, you can specify an additional path (not available if you set up export of images together with data to a file), a meaningful part of the file name, and, optionally, identifiers to be added the meaningful part of the name.
To specify an additional path, select Use additional path and then specify if the path should be based on the structure of the Hot Folder (Source path relative to the Hot Folder) or on the name of the batch name (Batch name).
The following can be used as meaningful parts of file names:
- Source file name, which is determined as follows:
- When adding files from a folder, the names of source files are used.
- When adding multiple files, the name of the first added file is used.
- For files scanned on a Scanning Station, the name of the scanning source is used and the output file is named {Empty Value}.
- For files scanned on the Project Setup Station, the names of temporary files are used.
- Document Definition name
- Specified file name, which is a combination of characters specified by the user.
The following can be used as additional identifiers:
- Document identifier (select Add document identifier to file name);
- Index field value (select Add index field to file name, then click ... and select an index field in the Select Fields dialog box).
- Advanced,
details
In this view, you can enter a file naming template in the File name template field. Your template can include an invariable part and tags to be replaced by specific information for specific files. You can type tags manually or use the Add tag... and Delete tag buttons.
The following tags are supported:
Important! Tag names are case-sensitive.
- <Project> – the name of the project within which the document is to be processed.
- <Batch> – the name of the batch within which the document is to be processed.
- <DocumentDefinition> – the name of the Document Definition applied to the document.
- <ImportSubPath> – the path to the import subfolder (must be specified for images imported from a subfolder).
- <SourceFile> – the name of the source file without the extension.
- <Identifier> – the identifier of the document in the folder.
- <BatchType> – the name of the batch type within which the document is to be processed.
- <Time> – the time of export in the format yyyy-MM-dd_HH-mm-ss.
- <ExportRootPath> – the root export path (as specified on the General tab of the Project Properties dialog box).
- <RegParam:...> – the value of the registration parameter (after the colon, specify the name of the parameter, for example: <RegParam:ParameterName>).
Note: First, the program will look for the registration parameter in the document. If there is no such registration parameter in the document, the program will look for the registration parameter in the batch.
- <Index:...> – the value of the index field (after the colon, specify the full path to the field in the Document Definition, for example: <Index:InvoiceName\Invoice Layout\Status>).
Make sure that the file naming options you specify do not result in empty file names. If the options you have specified may result in empty file names, the program will display a warning message.
Note: If document images are exported together with data, the same template that is used for naming data files can also be used for naming image files. To use the same template for both kinds of files, select the Same as data option in the Image Export Settings section of the Destination and File Naming Template dialog box.
20.02.2021 12:32:38