We currently have a client that is setup with QF Agent and we use a schedule of 15 minutes to check a folder for new documents. I was wondering if it is possible to call a QF Agent session via workflow or a script to start the session when a document is created instead of on a schedule. Any help is appreciated, thank you in advance!
Question
Question
Replies
Hi Alex,
As far as I know it's not possible to invoke a QF session in any way, you can schedule it with the Agent but that's pretty much it. This kind of makes sense in a way, as if you could invoke a QF session from workflow, nobody would ever bother purchasing the Agent. Not sure if the Agent supports input however...interested to see other responses on this.
You can however do this the other way around, and invoke a workflow from a scheduled QF session, could you perhaps re-jig this process to use that method?
Cheers!
I thought I saw that QF agent creates a MS task for the scheduled time that workflow can then call. So you would still need QF agent, but you can then use WF and some scripting to call the scheduled job. This way instead of running it every 1 hour, we could schedule it to run every 5 hours, but then WF could run it when a certain condition is met.
What is the concern with running the Quick Fields session once an hour?
Hi Miruna, are there any plans to be able to call QF from WF? I know it has come up a lot over the years but still doesn't seem to be an option.
My use-case is:
- Users in accounting upload invoices that need to be paid via Forms
- These go into a Forms queue
- One vendor sends invoices in packets of 50-200 that need to be split
- Store in LF
- Split via QF and grab a little metadata
- WF then sends to Forms as tasks so they're all in the same queue
- The queue is used to organized work that needs to be done in the ERP (paying vendors)
That step processing with QF would be nice if I could do in real time vs. waiting for a schedule. Or worse, kicking off a schedule when the file is still being stored and having pages generated (haven't tested that situation yet but I will).
No. The architecture of Quick Fields does not mesh well with Workflow, so there would have to be significant changes. Quick Fields does cannot have document IDs injected into Capture Engine, nor can it run multiple copies of a session at the same time (which it would be likely to happen since Workflow can run multiple instances of the same time).
"Real-time" is definitely not possible since Quick Fields processing can be time consuming and Workflow is asynchronous. So you wouldn't want to do this processing while a user is waiting on the form page.
In your scenario, is step 2.3 trying to rebuild a queue of invoices corresponding to the packet they came from or is there just one big queue for all incoming documents?
Makes sense. Thank you for the info.
The final Forms bit is so that all of their invoice processing comes from a single queue in Forms.
- Main process is general AP, invoices from around the business that need to be approved and paid.
- Freight and Material invoices get paid with no approval required and come in as PDFs. Using a separate Forms process to upload those and add them to the queue. This way they only have to work from a single queue. Plus, it ensures that we get them converted to TIF and collect key metadata. (I use Forms for document upload and indexing a fair amount.)
- A single vendor sends these large packets that need to be split apart, which currently they're doing manually via Acrobat Standard. This way we can make their lives easier by splitting them, getting some basic metadata (our PO number) and putting them into the same "to be paid" AP queue in Forms.
Hi Pieter,
Not sure if this helps, but we've integrated Laserfiche with Abbyy for pretty much this exact use case (which you can call from WF).
Cheers!
So what is missing that would be solved by Workflow calling Quick Fields? Or what does Abby do different in this situation?
Batch comes in, gets processed by Quick Fields Agent and put back into the repository as individual docs, Workflow detects the creation of these docs and starts a "to be paid" Forms process for each as they come in. What am I not seeing?
Just the time delay. After the batch invoice is uploaded there will be a delay before the QF session runs since it's running on a schedule as opposed to on-demand.
I assume we're talking about self-hosted here and not cloud? Because if we're in cloud you could use capture profiles, which CAN be kicked off directly from a workflow.
Thanks Tessa, yes that's right, I'm assuming this is self hosted.
In cloud, capture profiles on the whole is pretty good, the element it's missing in comparison to QF is the ability to split documents. Not sure if this is on the roadmap/radar yet? Cheers!