I have a Quickfields session which requires me to read data from columns on page 1 (using the accumulator) and what they call "overflow" from pages 2 (and SOMETIMES up to pages 3-4) and not from the ancillary pages. I have had to build separate sessions to accommodate the singles page or multiple pages. I would like to have this just work in one sesssion. The customer does not have the Conditional process which comes with the Classification package, and I don't think that I can sell them on purchasing the additional feature set at this time. I was wondering if someone would have an alternative?
Question
Question
Answer
Presales was able to help with this. It requires a persistent token to be created in pre-classification. This is the key, otherwise you cannot append to this token properly.
Replies
Bump
We do have Zone OCR so I am able to get the token and then accumulate them. That is kind of the issue. So, I am columns of data off page 1, sometimes also from the overflow on page 2, 3 and so on. Sometimes it might just be one page of overflow others it might be 3. So, in QF i can tell it to OCR pages 1-2 or 1-3, but nothing to say get this page only if it has a column of data. In my VAR kit i obviously have Conditional so I am able to do this, however that is expensive and not sure that I can get the customer to pay for that additional feature. I really just want a Conditional, but was wondering if anyone had an alternative. I have thought about the workflow idea, but figured also that is more work than is necessary and requires more billable time. I might just create two more sessions to accomodate 3 pages, then 4 pages for the OCR.
What you are essentially asking for then is an QF identification package without having identification, because how else are you identifying if a document has more than one page?
The only way I can think to do this is to have a session that breaks apart the document on page 1, and gets a zone OCR on the other pages and stores it as a token that you can then use workflow to loop through. However you'd also need to get some other spot on the page with Zone OCR to determine if the data you need is on that page as well as part of a workflow process.
As you can see this has the potential to become more complex with more potential failure sites, and the amount of billable hours can become more than the cost of additional QF features, especially if they decide they want more.
If you are not getting those tokens you are collecting through Zone OCR (because you don't own it) I'd actually consider doing the entire thing in workflow, because if it's a simple pattern match of an OCR'd document to get the data then you can duplicate that in workflow pretty easily with a retrieve text into multi-value token/pattern match into a multi-value token.