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

Question

Question

Pattern matching text on all pages

asked on July 22, 2022 Show version history

This is an issue that I thought was resolved by now, so I may just be missing something in my configuration. I'm trying to pull an identifier number via Pattern Matching, and it may not necessarily be on the first page. I am OCRing all pages and have Pattern Matching set to read on all pages, both within Page Processing.

Unfortunately, my Pattern Matching token is not populating the metadata field. Looking in the processing results I can see that it successfully pulled the number from Page 1, but the field is blank. What is required to run Pattern Matching on All Pages and have the token work to populate a field?

0 0

Answer

SELECTED ANSWER
replied on July 22, 2022 Show version history

It could just be that the value is being overwritten by activities on the subsequent pages (i.e., the pattern matching value is being set every time a page is processed, so it gets a value in the first one, but then that gets replaced with the blank value when it checks for the next page).

For example, you could create a token in your Pre-Classification processing to hold the value and use that to set your field value.

Then, in your pattern matching, store the pattern results to a token with a different name.

Lastly, add a Conditional in the Page Processing with an Assign Token Values under the conditional that assigns the pattern value to the main token you created.

For your condition, you could do "If Pattern Matching Token is not empty" or something along those lines, but the ultimate goal is to only change the "main" token when you actually get a value.

 

2 0
replied on July 22, 2022

Yes, that is exactly what it is. You get the last value read from the pages of a given doc.

3 0
replied on July 22, 2022

You can also check this last box in the Options dialog to have it use the first non-blank value.

3 0
replied on July 22, 2022

Thank you both! I don't have time to poke at this more today but I'll get back to it next week.

0 0
replied on July 25, 2022 Show version history

@████████ I think you have the right answer.

@████████ the goal is to use this with QF Scanning, and I haven't had luck with things in the options menu ending up in there.

Unfortunately, I don't think QF Scanning likes the new logic, either. It's great in regular QF, but in Scanning that field remains blank. Is pre-classification and conditional logic supposed to work in Scanning? 

0 0

Replies

replied on July 22, 2022

Mr. @████████, do you have any experience with this?

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

Sign in to reply to this post.