You are viewing limited content. For full access, please sign in.

Question

Question

Blank fields when quick fields session run

asked on March 11, 2020 Show version history

Hi All

 

I have created a QF session which has a ZoneOCR and pattern matching to populate the metadata.

My issue is that in some cases, there are fields which do not populate with the expected data and sometimes not all data is populated. e.g half the account number gets populated (the account number varies in length).

 

Question:

1. is there a feature in quick fields and/or workflow which will work as a case statement:

Case when Account_field is blank 

          Then re-look at the OCR text and populate the expected metadata

          Else Account_field

END

 

Basically i need all fields to be populated with the correct data and i can confirm that my QF session works correctly because when i re-scan the same document all fields populate .

Please assist?

 

0 0

Replies

replied on March 11, 2020 Show version history

Hi Ben, 

Are you saying that sometimes you will scan a document and the fields are blank, and then you scan exactly the same document again (without changing anything about the session) and then the fields are populated correctly?  If so, it sounds like the variation is likely due to slight variation in the image received from the scanner each time you scan, in which case adding logic for Quick Fields re-OCR the same image (or re-run pattern matching against the existing OCR results) wouldn't help.

Are you re-scanning the document by selecting it and clicking the re-scan button in the top toolbar?

0 0
replied on March 12, 2020 Show version history

Hi Tessa,

i re-scan the the same batch. 

Aside for having blank fields, in some instances when the document is scanned the brackets ( and )

are converted to / and \ sometimes ID is converted |O

 

I need to find a way to say if the field is blank then re-run the OCR and populate the field.

Is there a way to do this?

 

 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.