- Introducing ABBYY FlexiCapture
- ABBYY FlexiCapture architecture
-
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
-
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 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
-
References
- API Methods
- Data types
- Working with files
- Web Services Mobile API
- Web Services for user account management
- Examples of API Use
- Integrating Web Stations into third-party systems
- Configuring additional settings and customizing Web Stations
- Custom reports
-
Appendix
- 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
- Glossary
- Patents
- Third-party technologies
- Technical support
- End-User License Agreement (EULA)
English (English) - Change language
XML description file
The XML Description File contains information about a custom report and is used to enable the report in the Administration and Monitoring Console of ABBYY FlexiCapture. Several examples of reports are enabled automatically during installation. You can study their structure and use them as an example for creating your own reports.
The XML Description File includes the following elements:
- <customreport></customreport>
The main element of the report. Must contain the entire description of a report.
Attributes:
- Name the name of the report. It will be displayed in the Administration and Monitoring Console and is a required attribute.
- Type the type of your report. This is a required attribute. It can have two values: CrystalReportQuery (for reports based on Crystal Report queries) or DataSetReport (for DataSet based reports).
- Description the description of the report that will be displayed in the Administration and Monitoring Console. This attribute is optional.
- <crystalreportfile/>
This is a required element. It has only one attribute, Filename, which must contain the name of the report file (*.rdlc or *.rdl). The report with that name must be placed in the same catalog as the XML Description File.Note: Other elements are required only for DataSet based reports.
- <storedprocedure/>
This element is required for reports based on data extracted by a stored procedure. It has only one attribute, Name, which contains the name of the stored procedure. - <sqlText></sqlText>
This element is required for reports based on SQL queries. The contents of the query must be entered between the opening and closing tags.Note: If both <storedprocedure/> and <sqlText></sqlText> tags are present in the XML Description File, the DataSet will be created by the stored procedure.
- <parameters></parameters>
A range of parameters of the stored procedure or SQL Query. All of these elements bust be entered between the tags <parameter> and </parameter>. If no parameters are necessary to compile the DataSet, this element must not be included in the XML Description File. - <parameter></parameter>
Describes a parameter of a SQL query or stored procedure, and specifies details relevant to the parameters entry in the Administration and Monitoring Console. Attributes:
- Name The name of the parameter. This is a required attribute. It will be transferred to the SQL query or stored procedure.
- Type the type of the parameter. This is a required attribute. Possible values: Int, Date, String.
- Prompt the hint that will be displayed when a user enters this parameter. This attribute is optional.
- Default the default value of the parameter before the user enters a different value. This is an optional attribute. Date type parameters can have the value "now", which corresponds to the current date.
By default, the user enters the values of parameters into an entry field. If the value has to be chosen from a list, add the <possiblevaluelist> element.
- <possiblevaluelist></possiblevaluelist>
<possiblevaluelistitem /> elements are all of the possible values of a <parameter> element. - <possiblevaluelistitem />
Describes one of the possible values of a parameter. Attributes:
- value Possible value of a parameter. This attribute is required. Its type must match the type of the parameter.
- displayvalue a row that will be displayed in the list. This attribute is optional. If this value is absent, the value attribute will be displayed.
20.02.2021 12:32:38