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

Question

Question

Quick Fields Retaining Field Values

asked on May 18, 2020

Currently, I have a QF session using Laserfiche Capture Engine.  It is pulling in documents that already have field values.  When a document is unidentified by Quick Fields, QF is storing back into the repository but strips away all the field information.  Is there a way or workaround to allow it to retain or have that field data reassigned back to the document?  Thank you!

0 0

Replies

replied on June 5, 2020

Hi Shelby, 

Because we are working with unidentified document, there is no straight way to achieve this. I am proposing two workarounds below; for both options you will need to navigate to the menu to Configure the current scan source and under Document Content check the box “Keep each entry as a separate document. This will retrieve the field values from the source document when using Capture Engine.

  1. This following option is a good fit if all processed documents have the same metadata template. After the documents have been processed, we can assign the unidentified documents a Document Class in Quick Field from the Revision pane. This can be quickly achieved by selecting the complete section of Unidentified Documents (if all of them should be of the same class) and selecting the option of Assign Document Class. A dialog menu should appear that will let you decide which class you want to assign to the unidentified documents and other options, you can read more about these options in our Administration Guide. Note that by selecting this option of Assign Document Class, the unidentified documents will all be assigned the properties of the chosen document class, such as naming conventions, storage location in the repo, and etc. If the metadata templates coincide, then the documents will be stored with the field value that they originally had.

 

  1. Should the first workaround proposed not fit the specific business needs, you can also try to create default settings for unidentified documents where these unidentified documents can be set to store in a specific location in the repository. In these settings you will be able to select the template to apply to the documents. You can then have Workflow copy over the metadata from the original entry into these new Unidentified Documents and delete the previous entry to avoid having the document twice. You can then configure Workflow to move them if necessary to a specific location in the repository.  
1 0
replied on June 12, 2020

Thanks Maria for the reply!  We're using Quick Fields Agent so the first option wouldn't work. 

The second option is interesting though!  Yes, I've already taken a look at those settings for Unidentified Documents and can set a specific template and location in the repository.  My question is how would you then match the Unidentified Document with the original entry since it doesn't keep any sort of metadata?  Thank you so much!

0 0
replied on June 17, 2020

Maria, any update on this?  Thanks!

0 0
replied on August 7, 2020

Maria, any update on this?  Thank you!

0 0
replied on October 2, 2020 Show version history

I happened to run into a similar situation yesterday, and found a workaround that's working for me. I will note that this only works if your documents are not coming in in a batch, which makes sense logically, since if you just have one stack of papers, and your only identification is on the first page, how do you know whether a given page is the first page of a new unidentified document, vs the second page of an identified one?

If your documents are coming in as individual documents, however, this is the workaround I found:

1. Obviously first set your scan source to "Keep each file as a separate document".

2. In each document class with identification conditions, use your first page identification as normal, but also add a last page identification, that will never match (I used a Token Identification of "creation date does not equal creation date"). Since QF will always cut off the document at the end of the actual incoming document, this means once a first page is identified, the rest of the pages of that document will skip identification completely (always identify as that doc), which is what we want.

3. Create an "Unidentified" document class. In its first page identification, add the same "always false" identification, so this document class will never be identified normally.

4. Add a handler to the "Document unidentified" script event, with just one line:

e.ReassignDocument("Unidentified");

That way, QF will only send truly unidentified pages to that doc class. It'll still break when a new document comes in, though. (Again, what we want.)

Then you can set field values, use tokens in the document name, keep the existing tokens when using LFCE, etc., on that document. (My use case was using Universal Capture, where I just needed to keep the incoming document's original name as a field for processing - but I confirmed it does also work with LFCE.)

0 0
replied on June 8, 2020

Thanks Maria for the reply!  We're using Quick Fields Agent so the first option wouldn't work. 

The second option is interesting though!  Yes, I've already taken a look at those settings for Unidentified Documents and can set a specific template and location in the repository.  My question is how would you then match the Unidentified Document with the original entry since it doesn't keep any sort of metadata?  Thank you so much!

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

Sign in to reply to this post.