Can Quickfields remove pages based on text found within a zone?
Hi Chad,
You could configure Quick Fields to do this. Try setting up a separate document class for the pages you want removed, such as "Removing Pages," and placing it as the first document class that is evaluated in your session. In First Page Identification you can configure a Zone OCR process, Token Identification, or other method of identifying the text on the page. Then Last Page Identification can be used to limit documents in that class to a single page. In this way, Quick Fields will separate out every page that contains the text you specify one by one and all other pages to be classified as you would like. You can then configure Quick Fields to send the documents in the Removing Pages class into a repository folder that Workflow monitors to delete them for you.
Depending on where these pages are located within the other documents being processed, the solution described above may work as is or may require some modification. If, for example, a page to be removed is in the middle of a document's pages, rather than between documents, you'll run into issues with documents being broken apart and pages being sent to Unidentified Documents. In this case separate out the Removing Pages document class into its own session. This session should be run before your standard session to remove the desired pages but leave all others as one complete set that can be processed afterward.
Thanks Kelsey! I should be able to test this soon.
This seems to be working well, it creates an unclassified entry for each packet and I can configure the store options for unclassified docs. Is there a way to set QF to retain the metadata from the original document when scanning from the repository?
If you're using the Laserfiche Capture Engine to pull documents from the repository for processing in Quick Fields, you can have Quick Fields save the processed documents back as new versions of themselves and retain the existing metadata and document history. To do this, apply the Name and Path tokens to the document class's Name and Path options. This will save the document back in the same place that it was taken from, with the same name.
Then go into the Document Class Options, under Document Merging. From there, you'll want to select "Merge the documents" and to use the template from whichever application would be appropriate in the scenario - either Laserfiche or Quick Fields.
Hey Chad,
How did this work out for you? Whether you have the answer you needed or you still need help, just let us know!
This ended up doing the trick, I did need to specify where to save the file but instead I created a workflow to monitor for QF updates and then route the file. Thanks!