02-13-2013 10:46 AM
02-13-2013 10:53 AM
The simplest way to extract it might be to set the filtering to all character types, and then in the 'specific allowed characters' field, enter the values: 0123456789. (note the period on the end)
This way the engine will attempt to read everything, then before assigning to the keyword, it will remove all characters except for the allowed ones (the numeric digits and the decimal point).
02-14-2013 05:12 AM
It might be worth upgrading it to 16.6 (this will work with your existing OnBase version). I don't know for sure that this is something that Nuance has addressed, but if the problem still occurs in the highest available version, then I can take it up with Nuance.
02-13-2013 10:53 AM
The simplest way to extract it might be to set the filtering to all character types, and then in the 'specific allowed characters' field, enter the values: 0123456789. (note the period on the end)
This way the engine will attempt to read everything, then before assigning to the keyword, it will remove all characters except for the allowed ones (the numeric digits and the decimal point).
02-13-2013 11:58 AM
That's how I currently have it configured currently. The issue appears to be those pesky asterisks. I'm not sure why, but it makes the OCR engine return extra digits.
02-13-2013 12:24 PM
Is the issue that some/all of the asterisks are being misread as numeric digits?
02-14-2013 04:18 AM
Yes, that is correct. Most of the times it would always be an extra digit for the first number in the sequence. In this example 66,897.71. Everything is checked in Filtering except MICR data as well.
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.