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

Question

Question

Token page range

asked on July 17, 2015

We use barcodes as separator sheets (plus some inconsequential value). I have Quick Fields looking for this in the First Page Identification step. 

There are also a couple more barcodes that could be applied based on the type of document (confidential, restricted, etc). This secondary barcode would always be in the same spot and there would not be two secondary barcodes, because that's just silly. 

Under the Page Processing step, I am looking for this secondary barcode (if it exists), then I have a couple Conditional processes to see what secondary barcode was applied. If we have a winner, I'm setting an aptly named token (confidential and restricted, respectively) to true

This QF session passes these processed documents off to a fancy Workflow for additional magic, whereas the tokens act as parameters.

I'm confused about the page range section of the Assign token step. Does the Page Range apply to all pages of a separated document or the entire batch? If they are just referring to the pages in a split document, does it really matter if I select a certain page (like page 1) for the token vs all pages? And if the Page Range is referring to the entire batch, then, darn. 

0 0

Answer

SELECTED ANSWER
replied on July 20, 2015

Tokens have scope. In other words each page has its own set of token values. So any processes that rely on the results of previous tokens on the page should match the page range. In your case, Assign Token Values should match barcode's page range.

1 0

Replies

replied on July 20, 2015

The Page processing section applies to the identified document. Quick Fields does not keep track of the original batch.

Depending on where the secondary barcode is, Page 1 vs All pages does make a difference. If the barcode is on the first page, then selecting all pages will unnecessarily attempt process the rest of the pages in the document as well. If the barcode is somewhere other than page 1, selecting page 1 will not generate the value you expect.

0 0
replied on July 20, 2015

The page range for the secondary barcode makes sense, it would always be on the first page like the primary barcode; however, the token page range is less clear. Why is this important?

config.PNG
token properties.PNG
config.PNG (3.28 KB)
0 0
SELECTED ANSWER
replied on July 20, 2015

Tokens have scope. In other words each page has its own set of token values. So any processes that rely on the results of previous tokens on the page should match the page range. In your case, Assign Token Values should match barcode's page range.

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

Sign in to reply to this post.