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

Question

Question

When does Quickfields populate template fields?

asked on October 6, 2016 Show version history

I've setup a barcode read of a QR code in pre-processing.  I've also setup an assign token process from that initial barcode read.

In First Page Processing I'm reading the header information on that QR code to determine if it is a delivery ticket.

If the read of the QR code returns nothing, it makes that document the second (or third) page of the document identified as the delivery ticket.  But it does not populate the template for that multi-page document.

If I insert a conditional process in Page Processing to query the content of the original barcode read, the session will populate the template information with the token values from the first page.  (Note:  When I reprocess the QR code it again returns nothing.)

What I'm trying to figure out (among other things) is:   when in the session does the token information from the initial barcode read get written to the template?

10-6-16 QF QR session.PNG
10-6-16 QF QR session2.PNG
10-6-16 QF QR session3.PNG
0 0

Answer

SELECTED ANSWER
replied on October 11, 2016 Show version history

Even if there is a barcode on the 2nd page, if Quick Fields failed to find the barcode then you'll still see the issue I described wherein the most recently-read barcode value is empty. 

 

Here's what I suspect is happening:

So let's say you scanned in the first page of a document, and Quick Fields ran your pre-classification barcode process and found the barcode, so now the value of %(barcode) is what you expect it to be, and a new document is created based on your Token ID condition.

However, now the second page is scanned in, and the pre-classification barcode process is run again. This time, for whatever reason, Quick Fields does not find a barcode, so now the value of %(barcode) is empty. Because of this, it does not get identified as the first page, so it appends this page to the previous page, as expected. 

Now let's say this is a two page document, so at this point the document is complete. When the document is complete, the field values are set using the current token values, so the value for %(barcode) would be nothing because it didn't find any barcode data on page 2. 

 

Here's my proposed solution:

So you'll need to save the barcode data from the document's first page and then put that in the field of the final document. To do this, you can create an Assign Token Value process in Page Processing that saves the value of the %(barcode) token, and set the Assign Token Value's Page Range to only run on page 1. Then you can use this new token in your fields and I believe you will get the behavior you're expecting. 

0 0

Replies

replied on October 6, 2016

Hi Michelle!

Tokens from Pre-Classification processes (in addition to those from First Page Identification and Page Processing processes) are resolved in fields after the document is scanned and processed. So you can see these in the Document Manager before storing. What other things are you trying to figure out?

0 0
replied on October 7, 2016

Pieter, What I'm trying to figure out is why the template fields in Document Manager only get the token information when I enable the page processing function to re-process the barcode. 

The image of the filled in template fields above is AFTER the reprocess of the barcode runs.  If I disable this process (same as the one I disabled in the first page processing) I get nothing in the template fields in Document Manager. 

I am sure it's something in my placement of the process in my document classification, but it's not making sense right now.

0 0
replied on October 7, 2016

Are you creating a new token or modifying your previous token in the Copy of Assign Token Reprocess process?

0 0
replied on October 7, 2016

Yes I am creating a new token in the Copy of Assign Token Reprocess process.  But, I do not have that token applied to the template under the Delivery Ticket document class.  I only have the tokens associated with the initial bar code read in the template fields on the Delivery Ticket document class.

 

0 0
replied on October 7, 2016

Is this also happening when the initial barcode read is successful?

0 0
replied on October 7, 2016

Meaning are the fields being assigned to the template correctly when the initial barcode read is successful?  If that is what you are asking, then yes.

On all the other documents where the barcode read was successful, it creates the new document and populates the template and moves to the next document. 

Funny thing is that both the pages the are currently not having their barcode read are able to be read when they are scanned separately. 

0 0
replied on October 7, 2016 Show version history

OK so that Pre-Classification Barcode process only runs once on the identified document. Once you've done First Page Identification on that first page and identified the second page of the failed barcode read as a Delivery Ticket, the document goes to Page Processing. The barcode read in Pre-Classification will only run on the originally specified page; it won't run again on your "new" first page.

In your conditional "Copy of Check Barcode Read", you could use your Assign Token process to modify your barcode token that you use in the template. Otherwise the token will be blank since that initial barcode read failed.

replied on October 7, 2016

Is the barcode on all pages of the document, or just the first page? Pre-Classification processing runs on every page, so I'm wondering if the issue stems from the most recently-read barcode value being from a page without the barcode on it. 

0 0
replied on October 11, 2016

Tessa,  yes right now all the pages have barcodes on them but there will be intervening pages between the barcoded pages moving forward that I would want as pages 2,3,4, etc of that first barcoded page.

 

0 0
SELECTED ANSWER
replied on October 11, 2016 Show version history

Even if there is a barcode on the 2nd page, if Quick Fields failed to find the barcode then you'll still see the issue I described wherein the most recently-read barcode value is empty. 

 

Here's what I suspect is happening:

So let's say you scanned in the first page of a document, and Quick Fields ran your pre-classification barcode process and found the barcode, so now the value of %(barcode) is what you expect it to be, and a new document is created based on your Token ID condition.

However, now the second page is scanned in, and the pre-classification barcode process is run again. This time, for whatever reason, Quick Fields does not find a barcode, so now the value of %(barcode) is empty. Because of this, it does not get identified as the first page, so it appends this page to the previous page, as expected. 

Now let's say this is a two page document, so at this point the document is complete. When the document is complete, the field values are set using the current token values, so the value for %(barcode) would be nothing because it didn't find any barcode data on page 2. 

 

Here's my proposed solution:

So you'll need to save the barcode data from the document's first page and then put that in the field of the final document. To do this, you can create an Assign Token Value process in Page Processing that saves the value of the %(barcode) token, and set the Assign Token Value's Page Range to only run on page 1. Then you can use this new token in your fields and I believe you will get the behavior you're expecting. 

0 0
replied on October 12, 2016

Tessa, I follow your logic on how the Pre-Classification reads and processes pages one and two.  I will try your solution by limiting the Assign Token Value process to page 1.

I guess where it's still confusing me is when, on page two, it hits the %(barcode) = empty and then runs the Page Processing to re-process the barcode.  When I look at the Processing Pane in Quickfields I don't see any values for the barcode re-process, but when the document is complete it shows the values for the page one barcode in the template for the document.

That's where I lose the understanding of how the barcodes are processed and when the values in the Assigned tokens are replaced by the next barcode read.

0 0
replied on October 14, 2016

I believe what you're noticing, and understandably confused by, is that there are some cases where a token will retain the previous page's value when the next one is blank. However, I'd consider this an 'undefined' scenario - it won't necessarily work the same way with all scenarios and processes. In general, best practice is to be deliberate about what page(s) you want the information from. 

0 0
replied on October 17, 2016

Tessa,  I am the queen of finding the 'undefined' scenarios!  I will be very deliberate about handling of token information to populate my template with this and future processes.  I will refer to your October 11, 2016 post as the best practice for this.  Thank you for working with me through this scenario.

1 0
replied on April 17, 2017

Hi Tessa,

I'm really struggling with this process and am running out of hair to pull out so would appreciate some clarification on your solution for this issue please.  I've got a similar question to Michelle in that I have a barcode that is only ever on the first page of a (up to 56-page) document.  I get a successful barcode read off the sample page of the first page from the document, but even trying your recommended approach where the assign token value is only referencing the first page, I still can't populate the template field with the barcode value.

I've only got three processes:  the barcode process, the assign token value, and OCR at the end.  I've tried adding conditional processes, moving the processes between Pre-Classification, First Page, and Page Processing, but I can't get anything to work.

Where do I need to have the barcode and assign token processes in the configuration in order for it to retain the extracted barcode details please?

Thanks very much,

Mike

0 0
replied on April 18, 2017

Hi Mike, 

Is your sample page where you get a successful read exactly the same as the first page of the document you scan when you test the template field values? In height/width, DPI, etc?

0 0
replied on April 18, 2017

Hi Tessa,

Yes, I downloaded the Laserfiche page from the first page of the document and used that as the sample Tif.  It is as per your issue identification for Michelle, it seems to read the barcode on the first page successfully, but overwrite the result so that it doesn't populate the template field after reading the subsequent pages - I'm also a Kofax technician so have a different understanding of scanning and extraction functionality which may be why I'm struggling with how to get it to work in Quickfields.

Thanks!

Mike

0 0
replied on April 18, 2017

Okay. The simplest test case is to run the barcode process in Page Processing and set the process to run only on the first page:

Can you confirm whether this works or not?

0 0
replied on April 18, 2017

Here's the result of the test against the sample image of the first page, both the Barcode and the Assign Token Value processes return the correct results:

 

But here's what I get when I scan the full PDF into Quickfields:

Neither the Barcode process nor the Assign Token Value (both set for Page 1 only - there are 17 pages in this document) return the barcode value.  For the Document Content setting I've got "Generate images for each page" enabled in the PDF settings.  I'm most likely missing something simple, but I'm not familiar enough with Quickfields to know what I'm doing wrong.

Thanks!

0 0
replied on April 18, 2017

In your example since you are running barcode only on the first page and you are running it in Page Processing, you don't need the assign token value.  

Can you show a screenshot of the fields configuration i.e. the view that shows up in the right pane after you click on the document class in the left pane?

0 0
replied on April 18, 2017

Thanks for your patience Tessa - and sorry for highjacking your post Michelle!

Here's the configuration settings with the first page from the document as the sample image for the barcode testing:

And here's the result when scanning in the document:

0 0
replied on April 18, 2017

Hmm. It seems like there must be some difference between the image it gets when you scan and the image you're using as the sample. Can you try replacing the sample using this 'scan' option:

Also take a look at Document Content settings again. Which options besides "Generate images for each page" are checked?

0 0
replied on April 18, 2017

Hi Tessa,

It's something to do with the document being a PDF.  Quickfields shows that it's "Generating Images" in the status bar along the bottom of the window as the PDF document is being scanned in, but it's not seeing the barcode.  If I create the document as a tif then scan it in as a tif file, the barcode scan works fine and the template fields are populated correctly.  I can't see any instructions regarding the barcode functionality not working with PDFs, is this a restriction of the process or is there some other setting required please?  The source documents are always going to be PDFs so that's what I'm trying to work with.

Your response has just come in, to answer your Document Content settings question: I've seletect "Keep each file as a separate document", "Generate images for each page", "Extract the text ..." and "Include PDF form field values ...", and "Convert the PDF annotation...".

Thanks,

Mike

0 0
replied on April 18, 2017

It should work for PDFs. Even with all the information provided, I haven't been able to reproduce your issue. At this point I'd recommend opening a support case so we can troubleshoot further. 

0 0
replied on April 18, 2017

Will do.  I've just tested your suggestion of generating a new scan of the PDF for the sample image and the barcode no longer reads.  I'll raise it with Support.

Thanks again for all your help!

0 0
replied on April 19, 2017

Mike, no worries about post hijacking!  I am glad to know about how a PDF would process differently than the TIFFs I'm using in my scans.  And I'm usually the one with the odd cases, so it's nice to know I'm not the only one!  Would like to know the results, so if you or Tessa could share the support case in the post that would be great.

0 0
replied on April 19, 2017

Thanks Michelle, will do.

0 0
replied on April 19, 2017

Hi ladies,

In the end it turned out to be a client issue and after uninstalling and reinstalling both Quickfields and the Laserfiche Client the scanning started to work as expected.

Cheers!

Mike

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

Sign in to reply to this post.