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

Question

Question

Quick Fields - validating Agent-run sessions in the QF Scanning client

asked on March 7, 2019

We've got a Quick Fields session that is published to the QF Server, and also runs periodically via the QF Agent.

It uses a template that has required fields, and attempts to populate them using captured tokens. It stores the documents that find all required fields, but if any fields fail, we get the usual 'unstored documents' as per below screenshot:

 

We then want to be able to have the users go into the Quick Fields Scanning client, and see these unstored diocuments in there. When they click 'unstored documents' though, it doesn't show any docs from sessions that have been run by the Agent, only docs from sessions run by the user.

Is there a way to show 'unstored documents' from an Agent session to a user in the Quick Fields scanning client?

Thanks.

0 0

Answer

SELECTED ANSWER
replied on March 8, 2019

Hi Duncan, 

Thanks for your post. Currently only unstored documents from sessions run by a user can be validated in Quick Fields Scanning, as you observed. However, I have submitted your request for the team to look info for a future release. 

One alternative strategy we often recommend in situations like this is to perform the validation in the Laserfiche client. To do this, have Quick Fields use a different template with almost exactly the same fields except without making any fields required or constrained, and store to a "Pending Validation" folder. Because the fields are not required or constrained, your documents should not be blocked from storing to Laserfiche. Then you can use a workflow to apply the final template to the documents and move them to their final destination folder as soon as they have all the metadata they need. 

1 0
replied on March 8, 2019

Hi Tessa, thanks for that. Yes your workaround is exactly what we're currently doing.

 

We also thought of having a separate QF session, run in the scanning client by the user, that picks up the 'exception' files (with missing fields) from Laserfiche so they can validate them in there. Will let the client decide which approach they prefer.

1 0

Replies

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

Sign in to reply to this post.