Question

Quickfields - Storage Path of Unidentified Documents

Quick Fields

Updated November 6, 2015

asked on October 29, 2015 • Show version history

Hello, my Quickfields Agent uses a Quickfields session that take entries from different subfolders. Once processed the new documents are storaged in the same subfolders they belong.

Mi question is: ¿how can i setup the "unidentified documents" to be storaged in the same subfolders each one belongs?

0 0

Replies

replied on October 29, 2015

You'll want to create a new document class that catches all the documents that would otherwise be unidentified, and then set that document class to store to the correct location.

0 0

replied on October 30, 2015

Yes, that's it.

Please show me how can i create a new document class that catches all this kind of documents.

Thank you.

0 0

replied on October 30, 2015 • Show version history

I'm assuming you're using Quick Fields with the Document Classification Add-On. You just need to add a new document class, and then set the 'Store Documents in' path for this new document class to the same path as your existing document class.

Put this document class at the bottom of your Session Configuration tree, as shown here.

If you don't add any identification conditions, then any documents that aren't identified as the first document class will be caught by this new one.

0 0

replied on November 4, 2015

Thank you, we'll try that and let you know.

Regards.

0 0

replied on November 5, 2015

I´m using Quick Fields with the Document Classification Add-On to send all Unidentified documents to a document class, but i can´t find the way to add an identification condition that will not catch pages from a identified document
(from page number 2 to the end of the document).

0 0

View 2 previous replies

replied on November 5, 2015

Can you provide more details about how your documents are identified? Are you using the 'Keep each file as a separate document' option? What are your conditions for First Page ID and/or Last Page ID?

0 0

replied on November 6, 2015 • Show version history

Hi, I work with Alvaro,

We are using as the condition to identify documents a barcode wich value must start with "DOD" and that is the only condition to identify documents. Now we want to catch the FIRST DOCUMENT (from my stack of scan documents) as an Unidentified Document when the barcode is not present or Laserfiche couldn´t read it, so we created the "Unidentified Documents" class and it works fine to catch that first document, it´s just that it´s also catching pages (from the second to the last page) from another IDENTIFIED DOCUMENTS, leaving me with documents of one page (first page with barcode) and Unidentified Documents (attaching all pages with no barcodes between every first page).

Ejemplo.PNG (5.69 KB)

| Download

0 0

replied on November 6, 2015

I see. So is there any aspect of your document pages that you can use so create an identification condition that succeeds for pages 2-end of your documents, but does not succeed for any of the pages of the documents that should be unidentified?

0 0

replied on November 6, 2015 • Show version history

The only aspect these pages have (to be identified as pages from an identified document) is coming after a first page, identified with a valid barcode (starts with DOD).

0 0

replied on November 6, 2015 • Show version history

I'm not sure I understand exactly how your scanned pages are organized.

Here's my thinking: so let's say a human were sorting these documents by looking at them one by one. They look at the first page, and it has a valid bar code so they know it should be the first page of a new document. Then, they look at the next page. How do they know if this next page belongs as the second page of the current document, or if it's something else that should be unidentified?

0 0

replied on November 6, 2015

For reference, you may want to check out the How Documents Are Identified help page, if you haven't already.

0 0

replied on November 6, 2015 • Show version history

The Document Identification part is covered, all we want to do is send Unidentified Documents to the same location (subfolder) where they came from, with their name changed to <<Unidentified - "Original Document Name">>.

0 0

replied on November 6, 2015

The complication here is that in order to use Quick Fields to send documents to a location that depends on the document's original location, you'll need to sort them (using identification) into a document class so that you can use the capture engine tokens to set the path.

In Tools -> Options, under 'Current Session' -> "Unidentified Documents", there are options that allow you to set a hard-coded path, but it seems that in your case, you need to use tokens to set the path.

If you want to avoid creating a document class that identifies these documents, and all you want to do is rename the documents, then an alternative strategy might involve using another Quick Fields session or a Workflow that identifies any documents that were not processed by the original session and renames them.

0 0

You are not allowed to follow up in this post.

Question

Question

Quickfields - Storage Path of Unidentified Documents

Replies

Sign in to reply to this post.