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

Question

Question

Quick Fields Scanning workspace parameters

Quick Fields Version 11
Updated January 11, 2023
asked on January 11, 2023

I am working on a new deployment of QF Scanning that will be used at a dozen or so offices spanning the US and Europe. In this case, they are using USB-attached scanners, so my plan is to create a single shared session/document class and then set up a workspace on each scan station to ensure the physical scanner works properly (from other projects, this has been the smoothest way to get everything working with USB-attached scanners).

Here's the wrinkle: I need to set a field value for the branch that's doing the scanning without the user having to set it every time. And I would really prefer to use the single session as opposed to uploading one copy for each branch just to set that one field. Is there any way to pass a parameter via workspace? Something like modifying the XML to set a default value for a particular field.

It doesn't look possible but figure it's worth asking. Thank you.

0 0

Replies

replied on January 11, 2023 • Show version history

This might work for you, even if it's not exactly what you're asking for:

  • Add the built-in token "Machine Name" to the metadata in QF
  • If you already have the machines in a lookup table, add a "lookup" process in your classification stage to look up which site the machine name is in and add metadata accordingly.
  • If you do not already have the machines in a lookup table, after the documents are imported to your LF repo, you could potentially run a workflow where you hardcode the site to machine name relationships (multi-value token "Site X" with values "machine name 1, machine name 2") and do a lookup that way instead. For example: if token machine name x is in multi-token site x, then current document site metadata = site x.
3 0
replied on January 11, 2023

Unfortunately, I'm pretty sure there's no way to use the workspace to do that. 

One workaround might be to use two sessions that run in sequence: the first does all the heavy lifting and moves the documents to a a local location where a second session would set that field and store the document.  You could use QF Agent or the scanner operator to run the second session, depending on timeline and licensing and such.

0 0
replied on January 11, 2023

Thanks, guys. Unfortunately, I don't think either option will work.

Jacob: I need the branch to figure out which LF folder to store into so I can't think of a way to use the path for it.

Kevin: I actually thought about that since our machine names start with the branch number. Unfortunately, equipment gets moved between branches and when that happens, the name doesn't get updated. So not really something we can rely on.

I do have location information in AD that I could get for the account running the session via lookup table, but the user doesn't seem to be available as a token. I only see %(Username) that only gets set after storing into Laserfiche (I need to get the branch in the session as one of the criteria for a lookup; Jacob's two-step approach could theoretically work with this, but we want to display lookup results to the scanner operators as a check to minimize errors).

@████████ you have any experience with a situation like this?

0 0
replied on January 11, 2023

If you can look up the machine name in AD, you can also look up the current IP, which should give you the site with 100% accuracy (assuming you have different site subnets). Should be easy to regex that.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...