The following new features, updates, and bug fixes are included in the initial release of OCR for AnyDoc Foundation 25.1.
New Features
This release provides the following new feature:
- The Microsoft Vision engine can be used for the enhanced data extraction quality, especially for barcodes and handwritten data.
Product Updates
This release provides the following updates:
- Removed the support for Windows Server 2016 and Windows Server 2019.
- Multiple users can simultaneously import image files from the same computer.
Bug Fixes
This release includes the following fixed defects:
- User Settings configuration error: Resolved an issue where after configuring the Start Time setting in User Settings, an error message was displayed. Now, after setting the Start Time for a user and clicking OK in the User Settings window, the value of the Start Time setting is retained as entered, and no error message is displayed.
- OCR for AnyDoc Service failure: Resolved an issue where OCR for AnyDoc Service did not run properly. It now works as expected.
- OCR for AnyDoc Service stopped: Resolved an issue where OCR for AnyDoc Service stopped unexpectedly. It now works as expected.
- Instant OCR was not working by roping: Resolved an issue where instant OCR did not work when using right-click to rope. Instant OCR now works as expected.
- Converting large PDF error: Resolved an issue where converting large PDFs displayed an error and failed to complete. Large PDFs can now be successfully converted.
- Black section instead of the text: Resolved an issue where the imported PDF displayed black sections instead of text when the Aspose engine was used. Black sections are no longer displayed when the Aspose engine is used.
- Crop Mask failure: Resolved an issue where Crop Mask did not work properly. Crop Mask now works as expected.
- Endorser setting with Kodak scanners - i4x50 Driver failure: Resolved an issue where the Activate Mechanical Endorser setting was not properly interacting with Kodak scanners. It now interacts with scanners as expected.
- Odd characters in the Batch number header: Resolved an issue where, in the Pending Batch Viewer, odd characters were displayed in the Batch Number header. These characters are no longer displayed.
- The upward-facing arrow navigated to the previous document: Resolved an issue where the upward-facing arrow, during verification, navigated to the previous document instead of the previous zone. The arrow now works as intended and navigates to the previous zone.
- OCR for AnyDoc and Conversion Assistant error: Resolved an issue where Conversion Assistant encountered an error connecting to an Oracle database. In Conversion Assistant, users can now successfully create a new database and configure a Control Path, which opens in OCR for AnyDoc.
- Lost values in the DeletedBy, DeleteTime, and DeleteReason fields: Resolved an issue where values in the DeletedBy, DeleteTime, and DeleteReason fields were lost in the ADImage table when restarting a batch with deleted images. The values in these fields are now correctly updated when restarting a batch with deleted images.
- Confusing "100% correct" statement: Resolved an issue where, in the Verification window, the 100% correct statement was confusing. The statement is no longer displayed.
- Oracle error at the Commit phase: Resolved an issue where an Oracle error (ORA-01790) was displayed at the Commit phase of the process when at least one image was marked for deletion in the Quality Assure phase. This error is no longer displayed.
- The Up Arrow key navigated to the previous page: Resolved an issue where the Up Arrow key navigated to the previous page instead of the previous zone, during the Pass 1 Verify phasey for non-first images. The Up Arrow key now works as expected and navigates to the previous zone.
- Batch status information error: Resolved an issue where batch status information was not displayed correctly after all Docsets were routed. The batch status information is now displayed correctly.
- Suspended batch blocked the next batch: Resolved an issue where a manually suspended batch in the Quality Assure phase blocked the next batch from being classified. A manually suspended document can now advance to the next phase and be committed.
- The click counts did not reset when a new license was activated: Resolved an issue in the Client License Utility where the numbers of clicks, such as used or remaining, did not reset when a new license was activated. The click counts now work as expected and reset after activating a new license.
- ImportName column was empty after a commit: Resolved an issue where the ImportName column was cleared after a commit. The ImportName column in the AnyDoc.ADImage table is now updated to the name given in the imprint.ini file after importing a batch.
- No batch information in Log Database Viewer: Resolved an issue where batch information was not displayed in the Log Database Viewer with the Oracle DB configuration. The batch information is now displayed correctly in the Log Database Viewer.
- A batch caused a commit failure: Resolved an issue where one batch caused a commit failure on all servers. The Commit phase now works as expected.
- OCR for AnyDoc failure when connected to an Oracle database: Resolved an issue where OCR for AnyDoc crashed during import when connected to an Oracle database. OCR for AnyDoc now works as expected when connected to an Oracle database.
- ScannedBy populating for non-scanned batches: Resolved an issue where the ScannedBy column was populated for non-scanned batches after a batch was committed. The ScannedBy column is now populated only for scanned batches.
- Unsupported characters in a log database password: Resolved an issue where using a database password beginning with "~" and ending with "1" or "0" caused a login failure and displayed the password as unencrypted. Now, when a user configures a database connection with a password that begins with "~" and ends with "1" or "0", an error message is displayed prompting to change the password into the correct format.