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

Question

Question

Automate Extraction of data from documents saved in LF Respository

Quick Fields
Updated August 8, 2017
asked on August 2, 2017

Dear all,

 

I will like to trigger Quickfield agent automatically i.e. through a workflow when an entry is created in LF repository. We don't want to schedule a session every two minutes over 20 different paths in order not to impact on the bandwidth.

 

Any ideas are most welcomed?

 

Regards,

Vimal

 

 

 

 

 

0 0

Answer

SELECTED ANSWER
replied on August 2, 2017

I mean, the Quick Fields Agent has to launch Quick Fields and shut it down after each document process. There's a time cost involved and launching and shutting down applications. It's in milliseconds, but it does add up.

Quick Fields Agent has limits on the number of sessions running at a given time. Sessions whose scheduled time comes up and can't find an available slot to run are queued and run in order as a slot becomes available. Queued instances of the same session are compacted into one run when a slot become available (for ex, if a session schedule comes up at 10:37:00 and there isn't a slot available, it gets queued. The next run comes up at 11:37:15 and there still isn't a slot available, it won't queue a second run since it's the same session and it's already in the queue).

When the session runs, it picks up all the documents in the target folder, not individual ones.

If processing those documents takes longer than 15 seconds, the next run will get queued.

 

1 0

Replies

replied on August 2, 2017 • Show version history

This is not currently supported. Quick Fields can't take an entry ID as a starting parameter for unattended runs. It would also be more inefficient to start up and tear down the application for every document.

Can you elaborate on the bandwidth concerns you have?

1 0
replied on August 2, 2017

Can you please elaborate on the 'startup and tear down the application for every document?'

The capture and extraction of a set of documents (e.g utility bill, National ID card) need to be done within 15 seconds across 20 different branches scattered over different locations . My concern is that if I schedule Quickfield Agent to run every 15 seconds for 20 different locations, I am assuming that it might result in a considerable overhead over the network.

0 0
SELECTED ANSWER
replied on August 2, 2017

I mean, the Quick Fields Agent has to launch Quick Fields and shut it down after each document process. There's a time cost involved and launching and shutting down applications. It's in milliseconds, but it does add up.

Quick Fields Agent has limits on the number of sessions running at a given time. Sessions whose scheduled time comes up and can't find an available slot to run are queued and run in order as a slot becomes available. Queued instances of the same session are compacted into one run when a slot become available (for ex, if a session schedule comes up at 10:37:00 and there isn't a slot available, it gets queued. The next run comes up at 11:37:15 and there still isn't a slot available, it won't queue a second run since it's the same session and it's already in the queue).

When the session runs, it picks up all the documents in the target folder, not individual ones.

If processing those documents takes longer than 15 seconds, the next run will get queued.

 

1 0
replied on August 8, 2017

Thank you Miruna. It seems that we are not able to schedule QF Agent in 'seconds' intervals. Minimum interval seems to be minute.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...