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

Question

Question

Why does deleted template data in QF session still shows up in client?

Quick Fields Laserfiche
Updated March 2, 2015
asked on February 24, 2015

Good Afternoon,

We have a client that is using QuickFields to scan document separated by batch header sheets. Part of the process is to look for an optical mark in a certain location and if it is true to place a three character code in a template field. They QA all the scans and remove any optical mark misreads that may have occured. Once they have QAed the scans they send them into the DB. Today they noticed that sometimes when they delete the 3 character code from the template field in QF and send the document into the DB that the three character code comes back when they look at it in the client.

John

0 0

Answer

SELECTED ANSWER
replied on February 26, 2015

John,

We're investigating this issue and would like to get confirmation from you regarding the cause. If you disable the post-processing activities (rotate and OCR) from that document class, save the session, and then scan a new document, are you able to then clear out the field value while the document is in the revision pane and store the document successfully with the field showing as blank in the repository?

If so, then that's what we're seeing. The issue occurs when there are post processing activities being done. We will update your support case and this thread when it's addressed.

Regards

1 0

Replies

replied on February 25, 2015

Please apply the latest hotfix.

1 0
replied on February 25, 2015 • Show version history

Please open a support case and provide a copy of the Quick Fields session and a briefcase containing the template being used and some sample documents to test with.

Also, the version of Quick Fields displayed in Help > About now reads 9.0.1.481? And the issue still occurs with newly scanned documents (not just documents that may have been in the revision pane already from a prior scan job before the latest Quick Fields patch from KB 1013497 had been applied?

1 0
replied on February 24, 2015 • Show version history

Administrator edit: screenshot of Quick Fields 9.0.0.460 "About" dialog was removed because it contained the serial number and activation key.

0 0
replied on February 24, 2015

Is Quick Fields creating a new document or replacing the existing one? In the latter case, is the document class set to overwrite the metadata when merging documents?

0 0
replied on February 25, 2015

We are creating a new document not replacing.

0 0
replied on February 25, 2015 • Show version history

 

https://vimeo.com/120586834

 

Here is a video of it happening.  Password is: lfsupport

 

0 0
replied on February 25, 2015

0 0
replied on February 25, 2015

The hotfix was applied and it did not correct the issue. Below is a sample of a document that have SCI and YCQ in the automation field in QF.  They were deleted and ended up showing back up in the client.

0 0
replied on February 25, 2015

Here are a few screenshots from my QF session.

0 0
replied on February 25, 2015

Correct the version is 9.0.1.481 and these are newly created documents not ones saved.

 

John

0 0
replied on March 2, 2015

Alex,
 

Thanks for the reply, I am running the test with them this morning if possible. I will update as soon as I can.

 

John

0 0
replied on March 2, 2015

Alex you are 100% correct. If I remove the OCR and Rotate from the Post Processing the problem does not happen. Only happens when something is in the post processing. I have moved them into the page processing area until the SCR can be addressed and a hotfix can be generated. This will slow down scanning but will keep incorrect data from making it into the DB.

Thanks to everyone that helped with...

John

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

Sign in to reply to this post.

Details
Related Posts
Loading ...