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

Question

Question

Quick Fields: Run document classifications only when condition is met

asked on October 24, 2022

I have a packet with a barcode on the first page.  If the barcode contains data, I want to run the document classifications (barcode data saved to token collectors and repeated for each doc class from token retrievers).  However, if the bar code has has no data I want to either prompt the user to enter the data manually or I want to abort the process.  Is there a way to do this?

 

0 0

Replies

replied on October 24, 2022

Your setup doesn't quite make sense to me because it sounds like not every page is expected to have a barcode on it. Do you mind giving us more details on what you're scanning?

You can specify in the identification condition that the barcode cannot be blank, but if a page does not meet the identification criteria, it will be handled by the document class specifications (either appended to the current doc or sent to the next document class to attempt identification or treated as an unidentified page). There is no way to prompt the user for review at scan time. Nor is there a way to stop scanning when a condition is not satisfied.

0 0
replied on October 24, 2022

It's a packet with multiple documents in one PDF.  The first page has a QR code with the employee number and some other metadata.  The first doc class in the QF session reads the bar code on the first page and stores the metadata in token collectors.  The following pages are then identified with OCR as different doc classes, but retain the metadata using token retrievers.  Since we scan one packet at a time, I want to be certain that there is metadata in the token collectors before running the subsequent doc classes.

0 0
replied on October 24, 2022

You might be able to do something using two separate Quick Fields sessions.  The first session would simply check for the barcode information and, if present, set that information as fields and automatically store that "packet" in a temporary folder.  If the barcode information was missing, the document would be unidentified and stay in the session until a user filled it in manually and stored them.

The second session would pick up documents from the temporary folder and break them up, using the fields containing the barcode information.

0 0
replied on October 25, 2022

Jacob, thanks for the suggestion.  That might be a good work-around since QF doesn't support nested doc classifications.  It would be nice, however, if there was a way to conditionally branch to the other doc classes after checking the bar code for a value.  I don't know if that could be a feature request to LF or not, but it would be a useful feature.

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

Sign in to reply to this post.