Question

quickfields first page identification token identification not recognizing all the criteria

Quick Fields Scanning

Updated March 18, 2022

asked on March 18, 2022

I have set a number of token identification for my first page identification within a class. However QF is not recognizing the criteria I have set even though criteria are being picked up by the OCR. Have I set too many criteria for my first page identification:

0 0

Answer

SELECTED ANSWER

replied on March 18, 2022

I do agree with you, but for some reason my version of QF was having trouble with "does not contain" i began using conditions are false instead and its just stuck. I am finding that QF is ignoring some of the conditions. I always check via copy, past and search in a text or word document

0 0

Replies

replied on March 18, 2022

I'm not aware of any limit to the number of conditions, but I would caution you that the more specific you make it, the more likely it is your overall condition will be evaluated as false. And that includes increasing the likelihood of failing due to an OCR error.

Also, boolean logic gets difficult to understand when there's a lot of nesting and I think your condition could be simplified a bit by using the "does not contain" operator (instead of "if any of these conditions are false"). Something like this:

If you're still having issues, including sample OCR text may help to see what condition is failing. And be sure to check the OCR text for mistakes (e.g., 0 for O, 1/i/l/I, etc.). If these mistakes are happening in a consistent way, you can use a regular expression to help accommodate them.

0 0

SELECTED ANSWER

replied on March 18, 2022

0 0

You are not allowed to follow up in this post.

Question

Question

quickfields first page identification token identification not recognizing all the criteria

Answer

Replies

Sign in to reply to this post.