Use of regular expressions
Import configurations should include option to use regular expressions for fields to be indexed, including use of custom format labels
Josef
shared this idea
-
Alain Steiner
commented
Hello,
I need to read a QR code.
The QR contain a lot of info: adresses,....
I would like to extract the IBAN.
Regards
Alain -
Andrew Cooper
commented
Our company uses Docuware to archive invoices which we don't have any control over. Some of the invoices we receive are shaded in areas we need to read, and as a result the OCR is frequently unable to decipher the text correctly, or sometimes not at all. This creates extra work in checking/correcting for errors, as well as trying to locate the misread document in docuware. I set up a workaround by using the 'virtual' Docuware Printer to detect errors. For example if number is recognized as 'blank' then it is rejected because it matches two different profiles and is sent to a rejected document tray to be manually assigned.
If there were a way to apply a regex expression to a readout area, and then act on whether or not it matches that expression. Eg. The number 123456 is read as 1234S6. The regexp ^[0-9]{6}$ could be applied, and if it fails, then moved to a specific tray, or even emailed.
I noticed that you currently have regex implemented in the 'masks' used for manual entry, so it shouldn't take too much to implement this as the code is already present.
For Example:
Entry Type: Regex. Expression: <REGEXP HERE>. Action If No Match: [Move to Tray, Email Notification, Set Field, etc]
