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

Question

Question

Barcodes on Multiple Pages

asked on July 8, 2016

Does anyone know if there is a way to set the Page Range to the last page?  I have users saving documents that are supposed to be 1 page.  But often they have a large block of data that forces it to 2 pages.  I have 2 barcode zones set up looking for different information.  I have tried to do barcode read on all pages but when I try to use that information in the metadata it seems to pull the blank information from the first page with no barcodes and not carry over the information from the barcode on page 2.

 

 

Thanks.

 

0 0

Answer

SELECTED ANSWER
replied on July 12, 2016

That screenshot shows the process under Page Processing. If you want to keep it there, you need to use Token Accumulator like Tessa mentioned above, not Assign Token. You can use Token Accumulator on the token you're creating if you need to account for the substitution, it doesn't have to collect the barcode token.

Background info: tokens are per page and they go out of scope from one page to the next. By default, Quick Fields uses the first page's tokens in field values and document and folder names even when the process runs on multiple pages. So if tokens from other pages are needed (but you don't know ahead of time which page the value will be on), Token Accumulator is needed to collect tokens across all pages of the document.

1 0

Replies

replied on July 11, 2016

There are a handful of ways to accomplish this.

 

One option would be to put the barcode process in the "post-processing" section and have it run under a conditional like this one: 

If you try this one out, be sure to note this option for the post-processing section: 

 

Another solution would be to use the Token Accumulator process to create a multi-value token with the results of the Barcode process on every page. Then you could use the token editor to grab only the last value on the multi-value token, since that would correspond to the barcode value on the last page of the document. 

0 0
replied on July 11, 2016

I tried both of these prior to posting and neither worked. 

 

Putting it in post-processing was the same issue of pulling the blank one from page one instead of the values from page 2.

 

Token Accumulator didn't seem to work for pulling the right one because I have a substitute in there.  The barcode is 3 letters.  I have a substitute that replaces the 3 letters with a full document type.  I have tried first and last and it either pulls the 3 letter value or it pulls the blank page and tried to dump the token name in there %(DocTypeToken).

 

 

0 0
replied on July 11, 2016

Can you confirm that if you set the barcode process page range to page 2 and then run your session on one of the 2-page documents that the barcodes get extracted correctly?

0 0
replied on July 11, 2016

0 0
SELECTED ANSWER
replied on July 12, 2016

That screenshot shows the process under Page Processing. If you want to keep it there, you need to use Token Accumulator like Tessa mentioned above, not Assign Token. You can use Token Accumulator on the token you're creating if you need to account for the substitution, it doesn't have to collect the barcode token.

Background info: tokens are per page and they go out of scope from one page to the next. By default, Quick Fields uses the first page's tokens in field values and document and folder names even when the process runs on multiple pages. So if tokens from other pages are needed (but you don't know ahead of time which page the value will be on), Token Accumulator is needed to collect tokens across all pages of the document.

1 0
replied on July 12, 2016

Thank you all.  It works if I do a combination of the above answers.  Due to the substitution, the document types stays as assigning a token values.  But putting the Application ID into an accumulator and pulling the last value worked for that.

 

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

Sign in to reply to this post.