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

Discussion

Discussion

Quickfields - Populate a field value based on OCR results

posted on June 17, 2019

I am working on a Quickfields session to populate a template automatically.

I want to populate template fields based on OCR data.

When I create this using the dev license I configure it with the following tools from the toolbox.

Conditional

IF OCRDATA contains "something"

Set Token Value

Set a value of "selection"

From there I put the token value into the field. Done.

In production, the tool Conditional is missing. I guess it is sold separately. Am I doing this wrong and using the wrong tool?

I feel like every time I create a QF session, there is all these critical parts you have to buy to make it actually work.

If the Conditional is required to simply populate a template value, based on OCR data, then which packages is it sold in?

0 0
replied on June 28, 2019

Do they have Pattern Match and Substitution?  If so, look at those to check if the OCR contains your text and replace it if it does.

0 0
replied on June 28, 2019

Thank you Bert, I am going to check when I next get access! I know they have Pattern Matching, but that alone is no good since it only strips unwanted text. If I pattern match with many OR statements and I can use substitution with many OR statements that might be the key.

I already ran this by Laserfiche though and they think the conditional is required too. It is sold as part of a huge package though and is expensive.

0 0
replied on July 10, 2019

I found that I can use the or character "|" in the Replace field to look for values found in the OCR data, but I can only have one result, so no matter what it finds it will always select the same option from the list in the metadata. This would never be of any use.

In order to use OCR data to determine the value to select in the metadata I need an activity that works like this. Or if this does not exist as a visual activity, I need to be able to write code directly like I can in workflow. This seems like a common QF need though, since without this ability you could never select metadata based on what is found in OCR.

switch(expression) {
  case x:
    Select This;
    break;
  case y:
    Select That;
    break;
  default:
    //ignore
}

 

0 0
replied on June 27, 2019

Yes, it seems all this version of QF can do is dump OCR data into a field. It can not do anything more complex, like choose a value from a list based on what the OCR data contains.

0 0
replied on June 28, 2019

Sorry I think I missed understood your question and gave you a very simple answer that you probably already know!

 

What about the pattern match function or enabling a workflow after the Quickfields session has ran? You could set the workflow to retrieve the text, have a pattern match with multi-token values enabled and run a query based off each value?

0 0
replied on June 28, 2019

WF will be too problematic in this case, it removes that scanners ability to use the revision pane. We also happen to need to reference an entire page of text, over 4k characters, since they put the key indicator in different locations within many paragraphs. It is not a very clean process, which is why they are turning to QF for a solution.

0 0
replied on June 27, 2019 Show version history

On Quickfields you can use OmniPage Zone OCR and set the area where want to capture information.

 

 

On the template where you have the fields, click the token button >  and select the token OmniPage Zone OCR, and the token you have created, so below it's called "OCR Invoice No"

 

 

That will then input what ever characters it identifies in that field.

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

Sign in to reply to this post.