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

Question

Question

Quick Fields Scanning - Creates new document for each page

asked on July 6, 2017

I have a Quick Fields session that does not need to identify documents as each PDF we are processing  is it's own document. To do this i use the 'Keep each file as a separate document' option in the universal capture configuration window.

 

When running the session in Quick Fields everything operates fine. When running the same session in Quick Fields Scanning each page of the document is split into separate documents.   I have run into this a couple of times now and looking for any input on how to get the Quick Fields Scanning app to operate the session as designed.

0 0

Answer

SELECTED ANSWER
replied on July 6, 2017

Thank you for reporting this. I can now reproduce the issue: it appears that this is caused by a bug related to the Token Accumulator process. Bug reference TFS#34192 has been filed. 

 

As a workaround, I was able to get the desired behavior in Quick Fields Scanning by adding a condition to Last Page Identification that will never be true, and then re-publishing the session. For example, I used:

Please see if that works for your session. 

0 0

Replies

replied on July 6, 2017

The 'Keep each file as a separate document' option is meant to ensure that the document is ended when the end of a file is reached, but it's not necessarily going to prevent other settings in First or Last Page identification from ending the document before the end of the file is reached. 

 

It's hard to determine what is causing the discrepancy without more information. What do your First Page Identification and Last Page Identification settings look like?

0 0
replied on July 6, 2017

There are no settings or conditions enabled for either one

0 0
replied on July 6, 2017

What about these options under Last Page Identification:

Does it look exactly as shown above? Or something different?

0 0
replied on July 6, 2017

Yes it looks exactly like the image you posted

0 0
replied on July 6, 2017

I know you said you don't have any identification conditions set, but do you have any processes at all in the First Page Identification section? Even just an 'Assign Token Value' process?

0 0
replied on July 6, 2017

There are no processes in the first page identification at all. This is what it looks like when processing in QF (1 PDF)

 

Here is the same process, session, classification, and document in QF Scanning

 

0 0
SELECTED ANSWER
replied on July 6, 2017

Thank you for reporting this. I can now reproduce the issue: it appears that this is caused by a bug related to the Token Accumulator process. Bug reference TFS#34192 has been filed. 

 

As a workaround, I was able to get the desired behavior in Quick Fields Scanning by adding a condition to Last Page Identification that will never be true, and then re-publishing the session. For example, I used:

Please see if that works for your session. 

0 0
replied on July 7, 2017

The work around works in both Quick Fields and Quick Fields Scanning. Thank you!

0 0
replied on June 25, 2020

Is is possible for Quickfields to take a 200 page PDF of W2's (all identical) and seperate them into individual docs while using pattern matching to fill in the template for each page/seperate doc? 

0 0
replied on June 25, 2020

I should clarify that each page is a W2 that looks the same with different employee information on it. I would like to separate that into individual documents and fill in a template with First name, last name, and social security number

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

Sign in to reply to this post.