- 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
Prohibit sending documents from one stage to any stage other than the specified stage
This section describes how you can use roles to prohibit an Operator from sending documents from stage A to any stages other than B.
If stage B is Exceptions
To allow an Operator to send documents to the Exceptions stage, simply include this stage in the routing schema on the Workflow tab of the Project Properties dialog box (click Project → Project Properties...) or on the Workflow tab of the Batch Type Properties dialog box (click Project → Batch Types..., select the desired batch type, and click Edit...).
If stage B is Rescanning
Use the Advanced routing schema. First, open the properties of stage A and select the item that allows sending documents to the Rescanning stage:
- For batches of the Default type, click Project → Project Properties... For other batch types:
- Click Project → Batch Types...
- Select the batch type which you want to make accessible or inaccessible
- Click Edit...
- Click the Workflow tab.
- In the Schema field, select Advanced.
- From the list, select the stage from which documents should be sent.
- Click Edit....
- In the Workflow Stage Properties dialog box, click the Exit Routes tab.
- Select the Allow operator to send tasks to rescanning stage item.
- Click OK to save the changes.
Now you need to prohibit an Operator from sending documents to any stage. Create an appropriate role and assign it to the Operator in the Administration and Monitoring Console:
- Click Project → Project Properties...
- Click the User Roles tab.
- Click New...
- Provide a name for the role in the corresponding field.
- Clear the Send tasks to any available stage item. Clear or select any other items depending on which permissions you need to grant to the Operator.
- Click OK to save the changes.
- Assign the role to the Operator for the corresponding batch type in the Administration and Monitoring Console.
If stage B is neither Exceptions nor Rescanning
In this case you need to create a role that is not permitted to send documents to any stage. Next, in the properties of stage A explicitly allow the Operator to send documents to stage B.
To prohibit the Operator from sending documents to any stage, create an appropriate role and assign it to the Operator in the Administration and Monitoring Console:
- Click Project → Project Properties...
- Click the User Roles tab.
- Click New...
- Provide a name for the role in the corresponding field.
- Clear the Send tasks to any available stage item. Clear or select any other items depending on which permissions you need to grant to the Operator.
- Click OK to save the changes.
- Assign the role to the Operator for the corresponding batch type in the Administration and Monitoring Console.
To allow the Operator to send documents to stage B:
- For batches of the Default type, click Project → Project Properties... For other batch types:
- Click Project → Batch Types...
- Select the batch type which you want to make accessible or inaccessible
- Click Edit...
- Click the Workflow tab.
- In the Schema field, select Advanced.
- From the list, select stage A, from which documents should be sent.
- Click Edit...
- In the Workflow Stage Properties dialog box, click the Exit Routes tab.
- Add the stage by clicking the Stage... button or select the name of the stage from the list and click Edit...
- In the Next Stage dialog box, select the Allow operator to send tasks to this stage item.
- Click OK to save the changes to the sending options.
- Click OK to save the changes to stage A.
Note: If the Create task option is not selected when a document is sent by the Operator, the conditions for entering stage B will be checked. If these conditions are not met, the document will be sent to the stage following stage A in the routing schema.
02.03.2021 8:10:42