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

Question

Question

Last Page Identification - Page Process

asked on October 13, 2016

Hello!  I'm pretty sure I already know the answer, BUT if someone knows of a way to do this (or a feature request... :-))

I found 2 questions/answers that got me close (links below).  I have first page working as well as last page.  What I would really like to happen is to grab the dollar amount that will only be available on the last page - identified by the last page condition.  Sometimes the info will be on page one, but other times it could be page 2, 3, 4, etc.

I highlighted the Total Due info, but it looks grey!  It is located on page 2.

https://answers.laserfiche.com/questions/78666/Quick-Fields--FirstLast-Page-Identification

https://answers.laserfiche.com/questions/76500/Quick-Fields-QuestionFeature-Request

 

Thanks!

Toyia

1 0

Answer

SELECTED ANSWER
replied on October 13, 2016 Show version history

Hi, 

Due to the way Quick Fields processes documents one page at a time, it doesn't know how many pages your document will have until the Post-Processing stage. So to require that a process runs only on the last page regardless of how many pages there are, you'll need to do the following:

First, set Post-Processing to "After a document is processed, but before it is sent to the repository", like shown here:

Then, in the Post-Processing section, create a Conditional process with a condition like this:

Now, any processes you add under this Conditional process will run only on the last page. You can use the tokens from these processes in the document's fields just like you would any other token. 

1 0

Replies

replied on October 13, 2016

Fantastic that there is a way to do this!  I've got this in place, but I'm getting an error:

[0222-BP0] - for

It seems that this could be a missing component for QF???  I'm thinking this is a fairly standard token so I'm a bit confused.  I'll keep checking on my end...

 

Thanks!

0 0
replied on October 13, 2016 Show version history

Which process or step are you getting this warning for? Are you using the %(Page) token in any other place except in the condition picker for that Conditional process?

0 0
replied on October 13, 2016

I'm only getting the error for the post-process "page" token and that is the only place I'm using it.  Thanks!

0 0
replied on October 14, 2016

I assume you're scanning TIFFs or some other kind of image? (rather than electronic documents which don't necessarily have image pages)

What exact version of Quick Fields are you using?

0 0
replied on October 16, 2016

I'll try to give you this answer, as well as anticipated questions:-)

QF is version:

Currently I'm using LF Capture Engine to bring in the documents, but I will need to switch it to Universal Capture as the images are done either imported from Outlook (PDF) or scanned from a multifunction device and will also be PDF.  We will set up a single "style" of process using universal capture to import those PDFs from a monitored folder.

We do use QF Agent once we have completed testing (version 9.0)

Laserfiche Client is:

 

I think that's everything for now!

Thanks!

0 0
replied on October 18, 2016

Tessa - I did some additional testing and don't seem to be getting that error any longer.  If you find/think of something to check, let me know.

 

One new question and this should be easy, but I can only find info on how to set it up if I have positive and negative currency.  The way I'm setting it up is a 2nd doc class and the values will "always" be credits or negative amounts.  This vendor lists it like this though:

I need to know how to force it to be a negative.  They aren't picky - a "-" or "()" are fine.

 

Thanks!

0 0
replied on October 19, 2016

Hi,

Glad to hear the original issue was resolved. 

Sorry to be a pain, but could you please ask the 'positive and negative currency' question in a new, separate post? This helps keep things organized both for those answering questions and for those searching for answers. 

Thanks!

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

Sign in to reply to this post.