Question

Slow Quick Fields Store Speed

Version 10 Laserfiche Quick Fields

Updated July 10, 2020

asked on July 1, 2020

Hello,

Hope your all safe and well?

I have recently created a Quick Field Session that has helped streamline our processes a bit more, but at the same time it has become a bit of a bottle neck.

Below is part of the configuration.

I have made the process where, when the user scans and stores the document within the Laserfiche Client a Workflow will run and add a page to front of the document with specific text. Because it is an electronic image, it means Quick Fields can identify the correct document 99.9% of the time.

It works fine until we reach the storing stage where it has to do the Post-Processing. Each document will hang for about 10 seconds before storing the pages, so obviously it is working through the IF process, but should it be this slow? (I understand it is a resource intensive process, but it took about 30 minutes to store 203 documents, when previous sessions would store 200 documents in a minute or 2.)

The PC spec is the following:

I'm starting to think I should use workflow to do the Post-Processing stage instead as I would imagine that would be more efficient.

Any thoughts or suggestions?

Cheers

Rob

0 0

Replies

replied on July 2, 2020

If you disable the processes in Post-processing, do documents get sent to the repository faster? What conditions do you have in your Conditional process?

Sending documents is less likely to be impacted by CPU and memory on the machine. The load on the network connection or Laserfiche server is more likely to be a factor.

0 0

replied on July 3, 2020

Good morning!

Yes when I disable the processes in the Post-processing, the documents get stored to the repository a lot quicker (less then a second depending on the size of the document).

The condition that is running in the Post-Processing has the following criteria:

If successful it will do the following:

Now the reason I have two Page removals is because the documents get sent down with a Coversheet, which provides details on where to file the physical document in the file room, but when scanned we add a Control sheet to the front to ensure high accuracy on the page identification, once processed by Quick Fields the electronic document will lose both the control sheet and Coversheet passed on the above processes.

I have identified the cause now, it is the page removal activity based on page size. But if I for example have 2 page removal processes where I say remove Page 1 and Page 2 it doesn't work the way I would expected as I end up with the Coversheet page still attached.

Is there a way to say "Remove Page 1,2"?

0 0

replied on July 6, 2020

Hi Robert-

It's been a little while, but the last time I had to do something like this I believe I set both Page Removals to remove Page 1. After the first page is removed, what used to be page 2 is now page 1, so you want to remove the new page 1.

2 0

replied on July 10, 2020

Cheers for the response! I've worked out a way of doing it... I just had to think outside the box a bit and use some other Quick Fields features that I haven't really used before.

Thats the problem when you get stuck in your ways! Cheers everyone :)

1 0

You are not allowed to follow up in this post.

Question

Question

Slow Quick Fields Store Speed

Replies

Sign in to reply to this post.