Added several new tuning options for the OCR process that may be helpful when addressing output file size issues.
Improved the Separator logic so multi-threading should be enabled to improve system performance.
Documents without tags can now be handled in one of three ways:
FILE_L&F - the document is assigned a system barcode and filed in the Lost & Found drawer in Postmark Scan
HOLD - the document is put on hold and waits for resolution by the administrator
DELETE - the scanned image is deleted
Most image instructions are now editable from the Postmaster admin tool instead of just through the SQL Management Studio.
Image instructions have been improved with better descriptions, help text and better user interface controls.
Renamed the "Alternative OCR Method" to "Chunked OCR Method" and made it the default processing method. There are now two possible OCR methods: Auto and Chunked. All customers should use the Chunked method for best performance and output.
Fixed a problem when determining the image resolution on a page that caused output file size to increase dramatically when images are scanned with mixed resolution. This was most noticeable when the first page was scanned in a higher resolution in an effort to improve barcode recognition. Scanning the first page of a document in higher resolution is never recommended by DocSolid.
Refined the Chunked OCR method to improve performance and reliability.
A new version of our OCR tool-set has been referenced in 3.2.5 to improve file compression, speed and accuracy. Due to an error in prior versions single-bit (B&W) images may not be compressed.
Fixed a problem with the Queue Builder - if a machine hosting an enabled scanner fails or is powered off, the Queue Builder could stall so as to prevent all scanned jobs from being queued for processing.
Barcode images and eCovers are only removed if OCR is enabled. This issue was recently reported and will be repaired in a future release.
Scanner instructions aren't handled correctly by the admin application so there is a workaround that is required until the next release of MM3.
After your 3.2.5 installation the following fixes should be applied manually to ImageInstrType records:
ArgumentAllowedValues should be 0,1,2,3,4,5 field for -OneBitImageCompression
ArgumentDefaultValue should be TRUE for --RedactBarcode
Use SQL Management Studio to be sure all the default values in the ImageInstrType table are set as desired.
Create the scanners without setting any image instruction options.
Run the BuildImageInstrForAllScanners.sql script to create all missing ScannerImageInstr rows. Be aware that any ScannerImageInstr that already exist will be backed-up to a new table ScannerImageInstr_Old and all new entries will be made based on the defaults.
Make any scanner-specific settings using the admin tool.