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

Question

Question

QF scanning shows blank value for variables

asked on October 7 Show version history

Hi all,

I created a template in QF that uses pattern matching tokens to save scanned documents. When I run it in Quick Fields, I have no issue. I published the session to the QF server so I can use it in the QF Scanning application. When I run it in there, all I see are variables names like %(dept name), %(file contents) etc. They're the names of the variables I'm using in the pattern matching step inside Page Processing. I can see the session in the LF QF admin console and it's not showing any errors. Could someone provide insight as to what I'm missing?

if it helps, I'm using QF Scanning version 11.0.2303.30125
 

0 0

Replies

replied on October 9

QF Scanning has a Messages Pane, do you see any errors there? Messages Pane can be enabled in View -> Messages Pane

0 0
replied on October 16

Hi,

Sorry for the delayed response. Currently, I've run into the issue where it publishes the session but within the session, the Documents Classes tab is blank. My account has full admin access.

On the Quick Fields app, I go and click Publish Session

Once I hit publish, this is what happens:


In the database, the session gets created but the [QuickFields].[dbo].[documentclass_link] doesn't have anything.

I even created a new database called QuickFields2.



Could you provide insight as to what I'm doing wrong?
 

0 0
replied on October 16

Just for an update:
I reinstalled the QF app on my computer and activated it with the license key.
I reinstalled the QF server part and activated it with the server license key.

It's still not publishing with the Document Class

0 0
replied on October 16 Show version history

Update 2: 

I went here and realized I may have copied a process. I was able to get to work.

 

Do you know if there are plans for Quick Fields to be updated?

0 0
replied on October 17

We don't have an exact plan for Quick Fields release. I think the bug you mentioned is this bug (ID 320640). I add this post in the bug. So if there is a fix we will reply on this post

1 0
replied on October 17

I see. Thanks!!

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

Sign in to reply to this post.