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

Discussion

Discussion

Quick Fields unidentified - feature request for variables for Unidentified document naming

posted on September 26, 2014 Show version history

The short and sweet (i.e. TL;DR):

 I'd like to see the possibility of having some sort of "session variable" we can populate the Quick Fields unidentified document name. (Fields would be nice too, but I don't want to ask for too much!).

 

In the old days of Quickfield, this was never an issue. Before we had last page identifiers if we had a 100 page document and identified a 5 page document on page 1, then identified a different document on page 37, all of the pages in between were tacked onto the 5 page document. 

But now with last page identification, we have a lot more separate unidentified documents that are produced and split off from any single incoming document.

However, a new problem has come up with this in the last few projects I've worked on and there's no easy solution for:

How do you keep the unidentified documents seperate - i.e "input scan 1" from "input scan 2"?

As an example, I'm currently working on an issue with filing away a large number of documents when converting a HR dept from paper to electronic. They've given us their top 50 documents that we are identifying to file away in the proper folder, but that really only accounts for about 50% of the documents. 

The process the customer wants to do is this:

  • Take all documents in the customer folder, scan those in as a packet, label the packet with the employee's name/ID number/Location manually in Laserfiche, then have Quick Fields pull out all the identified documents they can. They do not want to spend hours putting in slip sheets, they'd rather split them up in laserfiche later. 

 

So this is where the unidentified issue comes forth - currently I lose that metadata if the unidentified document is in between two identified documents. 

 

I'd like to see the possibility of using a session token (such as the original name of the input document) as a token to name the document. This way I can leverage workflow to recover that original information. I think this would also be handy if you run into a situation where page 1 of a scan might be a header section that contains basic metadata about all of the other pages inside a scan, but you can't pass that information down to the unidentified sections of that scan. 

0 0
replied on September 26, 2014

Ok, I mentioned there's no easy workaround, but I think I have figured out a kludge I can use for some things in this situation:

 

Most of the documents I'm scanning have a certain amount of pages. So I'm not identifying a last page by actually looking at data on it but rather saying "form xyz is 4 pages always".

 

So what I'm going to attempt to do is use a field to label the form as usual, but also pass a field to workflow that says "# of pages". I'll then need to use a script to move any pages over this number to a new document. (I need to use a script because the move pages activity in Laserfiche doesn't accept tokens!). This way I can keep all the metadata assigned to this document before we tried to break it apart in both fields. 

 

***I *think* i might even be able to do this with pages where I'm actually identifying something on the page as well - I think I can create a current page number token inside quickfields but I haven't explored that fully yet. We'll see. 

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

Sign in to reply to this post.