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

Question

Question

Quick Fields Document Classification Limitations

Quick Fields
Updated May 9, 2016
asked on December 7, 2015 • Show version history

We have a client that potentially has 2500 different vendor invoices they wanted to setup in separate document classes within Quick Fields.

Can Quick Fields handle that many document classes without crashing or having performance issues?

0 0

Answer

SELECTED ANSWER
replied on December 9, 2015

Thanks Miruna - I also emailed presales the same time I posted on Answers - here was there response, inline with yours:

We recommend against having one document class for each of the 2500 different invoices in a single Quick Fields session, since that would most likely slow down performance considerably.

Generally speaking, for best practices we recommend individual sessions contain around 25 document classes to maximize performance.  We do have some people running Quick Fields sessions at 100 document classes, so it is possible; however, they are experiencing slower performance.  Additionally, if you are using Quick Fields agent, you can probably fit in more document classes per session since the session’s speed is not a major concern when you schedule the sessions to run during off-hours.

I have two different recommendations on how you might go about processing those 2500 different invoices using Quick Fields.

The first suggestion is presorting the documents prior to running the session with the document classes.  You can either use workflow conditionals or another Quick Fields session to presort the documents based on vendor names into groups of folders.  These folders will group the documents alphabetically (i.e. A-D, E-H..).  Once you have the documents sorted alphabetically, you can run smaller Quick Fields sessions on the folders so you are dividing up the 2500 different document classes into smaller manageable sessions.

You might also go about this by utilizing full page OCR and pattern matching.  You can run a session to OCR the entire page and utilize pattern matching to identify the pertinent patterns for document identification such as invoice number and vendor name.  This method allows you to cut down the amount of document classes you would need to use.

Additionally, attached to this email are two white papers, one is on hardware planning and the second is on Quick Fields 9.  Both documents have information regarding Quick Fields hardware specifications that might be helpful to you.

0 0

Replies

replied on May 9, 2016

Just FYI, I was recently told by Alex Haung that the limitation to QF is 255 document classes per session. He said he was told this from the development team. 

1 0
replied on December 8, 2015

While there is no theoretical limit to the number of document classes you can have, you're likely to see performance issues when processing documents in sessions with over 50 document classes. Is there any way to triage these documents before scanning? Or maybe have Quick Fields Agent run them through a series of sessions that narrow down the document types?

0 1
SELECTED ANSWER
replied on December 9, 2015

Thanks Miruna - I also emailed presales the same time I posted on Answers - here was there response, inline with yours:

We recommend against having one document class for each of the 2500 different invoices in a single Quick Fields session, since that would most likely slow down performance considerably.

Generally speaking, for best practices we recommend individual sessions contain around 25 document classes to maximize performance.  We do have some people running Quick Fields sessions at 100 document classes, so it is possible; however, they are experiencing slower performance.  Additionally, if you are using Quick Fields agent, you can probably fit in more document classes per session since the session’s speed is not a major concern when you schedule the sessions to run during off-hours.

I have two different recommendations on how you might go about processing those 2500 different invoices using Quick Fields.

The first suggestion is presorting the documents prior to running the session with the document classes.  You can either use workflow conditionals or another Quick Fields session to presort the documents based on vendor names into groups of folders.  These folders will group the documents alphabetically (i.e. A-D, E-H..).  Once you have the documents sorted alphabetically, you can run smaller Quick Fields sessions on the folders so you are dividing up the 2500 different document classes into smaller manageable sessions.

You might also go about this by utilizing full page OCR and pattern matching.  You can run a session to OCR the entire page and utilize pattern matching to identify the pertinent patterns for document identification such as invoice number and vendor name.  This method allows you to cut down the amount of document classes you would need to use.

Additionally, attached to this email are two white papers, one is on hardware planning and the second is on Quick Fields 9.  Both documents have information regarding Quick Fields hardware specifications that might be helpful to you.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...