About this release
Purpose
Purpose of this release are bug fixes.
Several major issues have been resolved. You can find more information in the Resolved Issues section.
Build information
- Part Number: 1298/14
- Build Number: 11.0.105.42
History of releases for this product version
| Release | Date | Purpose | Key new features |
|---|---|---|---|
| FCE11 R3 Patch4 | 08/01/2017 | Bug fixes. See Patch 4 Resolved Issues | |
| FCE11 R3 Patch3 | 04/19/2017 | Bug fixes. See Patch 3 Resolved Issues | |
| FCE11 R3 Patch2 | 01/30/2017 | Bug fixes. See Patch 2 Resolved Issues | |
| FCE11 R3 Patch | 01/17/2017 | Bug fixes. See Patch Resolved Issues | |
| FCE11 R3 | 10/28/2016 | A maintenance release with new features and bug fixes |
|
| FCE11 R2 | 12/25/2015 | A maintenance release with new features and bug fixes |
|
| FCE11 R1 | 06/17/2015 | A major technology update with many new features |
|
Additional information
- ABBYY Technology Portal: https://abbyy.technology/
- Knowledgebase: http://knowledgebase.abbyy.com/?searchText=&ProductId=390
- Forum: http://forum.ocrsdk.com/
- Case Studies: http://www.abbyy.com/casestudies/
Upgrading from previous versions
Binary incompatibility
It is necessary to recompile host application regardless a version of Engine previously used.
API changes
Release 1
- long data type has been replaced with int data type in all properties and methods that used it.
- The InitializeEngine function now takes only one input parameter — the Project ID number.
- The SaveToMemory method provided by many objects returns the handle to the memory buffer as the Handle object.
- The LoadFromMemory method provided by many objects receives the pointer to the memory buffer as __int64.
Release 2
- REMOVED: BARCODETYPEENUM.BT_PDF417_CODEPAGE_IN_BYTEMODE
Release 3
REPLACED: SCANSOURCESETTINGS::COMPRESSION
- A new property ScanSourceSettings::CompressionType for compression type specification was implemented. It is used instead of the ScanSourceSettings::Compression property that did not have realization, was deprecated and removed.
REMOVED: SCANSOURCESETTINGS::ORIENTATION
- This property was deprecated and removed because it did not have realization and did not work.
ADDED: API FOR ASYNCHRONOUS SCANNING
- FCE 11 R3 has methods for asynchronous scanning.
- Please find more information in ‘Asynchronous scanning’ article.
ADDED: METHOD FOR SAVING TO MEMORY
- A new method FlexiCaptureProcessor:: ExportDocumentToMemory exports recognized document to memory using specified export settings.
- Please find more information in ‘Export to memory’ article.
ADDED: METHOD TO LOG UNRELEASED OBJECTS
- A new method Engine::LogUnreleasedObjects writes to the log file a list of objects that are not currently deleted. Please find more information in ‘Function for logging unreleased objects’ article.
Release 3 Patch
There are no changes in API
Release 3 Patch2
There are no changes in API
Release 3 Patch3
There are no changes in API
Release 3 Patch4
There are no changes in API
Release 3 Patch5
There are no changes in API
Changes in behavior
Release 1
| Folder | Description |
|---|---|
| %ProgramFiles%\ABBYY SDK\11\FlexiCapture Engine | Default value for a folder storing binaries, the Help file and the guides, and USB dongle driver redistribution. Also Read Me file takes place there. User can change the destination upon installation process. |
| %ProgramData%\ABBYY\SDK\11\Licenses | This is permanent place for protection subsystem files |
| %ProgramData%\ABBYY\SDK\11\FlexiCapture Engine | This is permanent place for auxiliary Engine files like include files and samples |
Release 2
There are no changes in behavior in this release.
Release 3
There are no changes in behavior in this release.
Release 3 Patch
There are no changes in behavior in this release.
Release 3 Patch2
There are no changes in behavior in this release.
Release 3 Patch 3
AN ABILITY TO SAVE LICENSE COUNTERS VALUE ON LICENSE DEACTIVATION
- A new section 'ZeroLevel' was added into License Wizard for FCE 11. The only one available option in this section is ZeroLevel.
- If this option is activated, a license counter value will be saved in ABBYY Registration Server during the license deactivation. On further activation counter will take value from ABBYY Registration Server.
Release 3 Patch4
There are no changes in behavior in this release.
Release 3 Patch5
There are no changes in behavior in this release.
New features and improvements
RELEASE 3
There are no new features or improvements for Patch and Patch2
Asynchronous scanning
FCE 11 R3 has methods for asynchronous scanning. This means that one can scan i.e. without blocking the execution of the program. FlexiCapture Engine also provides callback interface (IScanCallback) that could be used during the scanning.
Export to memory
There is a possibility to save extracted data into a file (to a disk).
Sometimes it is convenient and/or required to store no files on a processing PC disk and put them directly to a secured DB or a file storage. To facilitate that, an ability to save an output file into memory is implemented.
FlexiCaptureProcessor:: ExportDocumentToMemory method exports recognized document to memory using specified export settings. If export settings are not specified, the document is exported in XML format with default settings.
Function for logging unreleased objects
A new method Engine::LogUnreleasedObjects writes to the log file a list of objects that are not currently deleted. The method can be called any time when necessary.
This method is available only with programming languages which do not have garbage collections (for example, C++).
Automatic uninstallation of Runtime FCE installation
Uninstallation of FCE 11 runtime is more automatic from now on:
- It is possible to install several Runtime copies in different directories using License Server standalone.
- There is an opportunity to install FCE with parameter DEINSTALLRUNTIME=yes with setting install directory. In this case all the files will be deleted from the directory and licensing server will be deleted from the machine on necessity. It is controlled that such a kind of uninstallation does not damage the functionality of other products.
- Libraries is deactivated while uninstallation is processing, if it is necessary
Compatibility with FC11 R5 Patch2
FCE 11 R3 works with projects created in FC11 R5 Patch2, build 11.0.4.2059, or earlier. Projects saved in the FCE 11 R3 can be used in FC11 R5 Patch2, build 11.0.4.2059, or later.
RELEASE 3 PATCH 3
There are no new features or improvements.
RELEASE 3 PATCH 4
There are no new features or improvements.
RELEASE 3 PATCH 5
There are no new features or improvements
Resolved issues
This section contains a list of bugs that have been fixed.
This four-point scale will help you evaluate the severity of each issue, enabling you to make informed decisions on how important updates are for your system.
| Critical | A bug that causes crashes or hangings of software. Critical bugs can include access violations, internal program errors, stack overflow, out of memory or other exceptions that can lead to program failure. |
| Major | A bug that does not cause program failure but affects major functionality of a feature or impairs the system’s performance. Major bugs can include disparity between feature functionality and internal specifications, memory leaks or data corruption. |
| Minor | A bug that leads to feature malfunctions or affects minor functionality of the software. Minor bugs can include recognition errors, missing or lost objects, incorrect color detection, incorrect document analysis, license counter errors, etc. |
| Trivial | A cosmetic issue that does not affect the functionality of the product but which can cause inconveniences. Trivial bugs can include Help file errors, log errors, incomplete information in error messages, etc |
The following table contains bugs fixed in this release, sorted in descending order of severity. If the bugs have workarounds, root causes or side effects, they will be mentioned in the Description section.
Release 3
| Severity | Description | Technology Subsystem |
|---|---|---|
| Critical |
IPE occurred on processing of client’s document. Root cause: an error in FlexiCapture controller |
FCEngine 11/Controller |
| Major |
FCE hung on in case of using FlexiCaptureProcessor::RecognizeNextDocument method. Root cause: document was proceed for too long because of too big page’s id size (about 3 * 10^5 charachters) and outdated data structures were used. |
DAForms |
| Minor | FCE decreased counter in case of processing ImageDocument that has already been processed by FRE | API |
| Minor | In case of using IFlexiCaptureProcessor::SetUseFirstMatchedDocumentDefinition method, log file contains a wrong record of nonexistent method IFlexiCaptureProcessor::SetUseFirstMatchedTemplate. | API |
| Trivial | After developer installation of FCE11 R2 link to the documentation “FlexiCapture Engine Help” led to FRE help file | Install |
Release 3 Patch
| Severity | Description | Technology Subsystem |
| Critical | While working with runtime license, it was impossible to create ExportParams | API |
| Major | FCE was not able to open some specific PDF files Root cause: installation tool did not copy all the necessary resource files of APDL | Install |
Release 3 Patch 2
| Severity | Description | Technology Subsystem |
| Major | Problem with zero license counter in case of license written (activated) onto a Wibu key Update | Protection |
Release 3 Patch 3
| Severity | Description | Technology Subsystem |
| Major | Error occurs in case of saving or closing a document after changing any field’s value without checking (CheckRules method). | API |
| Minor | Not implemented old methods in API generate errors | API |
| Minor | On transferring ImageDocument from FCE to FRE using OutprocLoader, license counter decreases again when ImageDocument is re-recognized in FRE. | FRE API |
| Trivial | Log message ‘Unreleased objects list: FCEngine.Template’ is hard to understand for customers. | API |
| Trivial | Wrong description for ImageProcessingTools::RotateImage method in documentation | Help |
| Trivial | Wrong description of allowed compression types for export in documentation. | Help |
Release 3 Patch 4
| Severity | Description | Technology Subsystem |
| Critical | ‘Division by zero’ error occurs in case of geometry correction on specific customer’s images | Image |
| Critical | Internal program error occurs in case of recognition of specific customer’s document with package type "Счет-фактура_ОГ". | Barcodes |
| Major | In debug configuration on processing of specific user’s image with document definition IPE occurs when CheckResult method is called. | DAForms |
| Trivial | Hello sample on JavaScript does not work if not full path to .fcdot file is set. | Samples |
Release 3 Patch 5
| Severity | Description | Technology Subsystem |
|---|---|---|
| Minor | An error on passing export parameters to processing thread on Java API | API |
Known issues and workarounds
Integrated FRE has no visual components
ABBYY FineReader Engine 11 product included into ABBYY FlexiCapture Engine 11 distributive lacks of FRE Visual Components.
Uncompressed DCX and PCX files are not supported
If a file of PCX or DCX format file contains uncompressed image FRE and FCE opens it as a blank image. Fixed in the latest technology version. No plans to port back the fix to FCE 11
Invoice projects are unsupported
FCE 11 has no official support for the FC invoice projects. Though it is possible to run such projects w/o end-user interactive invoice definition training. To run the projects, you enable a special licensing option
Adobe Reader full-text search in FCEnging11UserGuide.PDF does not work
Adobe PDF Reader does not provide correct full-text search through FCEngine11UserGuide.pdf file. The search works in other applications, e.g. Foxit Reader.
Limited functionality of IImageDocument interface in FlexiCapture Engine vs FineReader Engine
Objects with IImageDOcument interface obtained through FCE 11 API provide less functionality than objects with the same interface created by FRE 11 API, namely:
1) SaveModified does not work. It is not possible to change an image FCE 11 works with.
2) Properties: IsInternalFormat, IsModified, and IsReadOnly, - always return same value. This is due ‘read-only’ nature of ImageDocument objects created by FCE 11.
Customer support
The ABBYY SDK Support team is ready to help you. Please refer to the contact information and hours below.
Contacts
- Customer Support Management (CSM) Portal: www.abbyy.com/csm
- Developer Support Email: Dev_support@abbyyusa.com
Office hours
Monday – Friday from 9AM to 6PM PST
Information required
When opening a support case or contacting support, please be prepared to provide the following information:
- Description of the issue
- Sample images for testing
- Run and send Ainfo Report from the Bin/Support folder of installation directory
- Full error messages that have occurred
- Any additional information you feel may be helpful for the investigation
The information above will assist the ABBYY Support team in investigating your issue and providing a prompt response.