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

Discussion

Posted to Laserfiche Lounge

Discussion

Laserfiche Lounge

Laserfiche - "Dream" list

Updated September 21, 2021
posted on October 8, 2014

I've seen wish lists and feature requests posted for a while now.

 

Let's take it a step further.

 

What is on your Laserfiche "Dream" list?

 

By Dream list, I mean something that is probably technically unfeasible but you'd still like to see.

 

For me, I want to see a "Document Recognition and Processing" Action/Module for Workflow.

 

This action would take a document as an input, then intelligently recognize what type of document it was and automatically extract data from that document.  Outputs would be tokens for what type of document was found and tokens for all of the data extracted.

 

For example, feed in an image of an invoice into this magical action and it would analyze the image, determine it was an invoice, then extract data into tokens for Invoice number, date, payee, address, line items on the invoice, total amount, etc.  You'd need a token to handle the case failed recognition.

I would have some sort of intelligence to determine the type of document and the relative data to extract, and a way for admins to define new types when necessary.

Feed it recipes, it recognizes a recipe and extracts the ingredients, volumes, and directions.  Feed it a purchase order, it extracts items, vendor info, and accounts.  Feed it a shopping list, and it recognizes bacon.

 

So, that's my dream.  Maybe 10 years from now we will have document recognition technology like this.

 

 

So...  What's your dream?

2 0
replied on September 21, 2021

Just stumbled upon this old post and am delighted to note that since this was posted we have been able to address the invoices use case mentioned smiley

For anyone who hasn't seen this, check out our intelligent capture solution for invoices that does a lot of what's mentioned in the original post: https://www.laserfiche.com/solutions/accounting/accelerate-accounts-payable-processes-with-smart-invoice-capture/

0 0
replied on October 10, 2014 • Show version history

Oh, another thing I don't think WF can do: Remove a section of the name during the Rename Activity.  My Archive process includes a WF that will mark the document ready for archiving, plus rename the document with "MARKED FOR ARCHIVE" at the end of the document name; then at the end of the year, another WF will run and collect all those documents, plus rename them with "ARCHIVED" at the end.  But... it can't remove the previous words that are no longer needed in the name.

U P D A T E :  Feb 2/15; for some reason I can't "reply" on this post right now.  I'll try the Edit option to get this update in.  ... Update:  I did get the WF to remove what I wanted and add what I wanted all in one Rename activity, with help from Miruna Babatie off this site.  See the post titled "regular expression to remove a section of name" for all the details, but the trick was a Function called "Trim".  The formatted token looks like this:

CurrentEntry_Name, ARCHIVED

and the formatting for the "CurrentEntry_Name" token is

%(ForEachEntry_CurrentEntry_Name#@Split(MARKED FOR ARCHIVE);Trim@#)

1 0
replied on October 13, 2014

Hi Connie!

I haven't had time to work out the specifics, but I think you could do this with a regular expression.

 

I'm not so good with RegEx, but I think you could use that to format the new document name from the old document name.

0 0
replied on October 17, 2014

Can you use a Reg Expressions to "replace (this)" ... "with (this)"?

0 0
replied on January 30, 2015

well, you can do this a bit roundabout. 

Modify the original name to split on "MARKED FOR ARCHIVE" using the "Split" function in the token editor
Then use the function "replace" and replace "MARKED FOR ARCHIVE" with "ARCHIVED"
Then select "Apply Index" and then "All values separated by: "Space"

That should do it. 

Or, the other option is to make a really simple Script that takes in the name, and replaces those words for you and pass it in as a new token you use in the rename.

 

My third idea is to make a simple database that when you change an entry to include "MARKED FOR ARCHIVE" it adds the original name and Entry ID to the DB table. When you run the workflow at the end of the year, you know the entry ID, so you dont need to worry someone renamed the document for any reason (and Find Entry after retrieving information from a DB is much faster than running a search), and then rename the document to the name you have stored for it and "ARCHIVED" at the end. 

0 0
replied on October 10, 2014

My dream!  I want to see Workflow or Business Processes be able to include pop-up boxes to staff at certain steps along the way.  For example:  I have started a process where staff will add a tag to a document when it is ready for archiving (no longer a "working" document).  The process could have been simpler if the WF that acts on this tag being applied would pop up and ask the staff, "do you want a shortcut left behind?" with a Yes/No type of choice for them to make.  I've thought of so many ways I could use this in BP's, but the ability is just not there right now.

4 0
replied on October 13, 2014

Yes!  I wish for this one too!

0 0
replied on January 30, 2015

well, the tags arent saved until you close the document, so why not add a "Keep Shortcut behind" tag that you add to any of your BP's so if it is indicated, you remove the tag and leave behind the shortcut. Or just use two different tags, one for leaving a shortcut behind and invoking the workflow, the other for not leaving a shortcut behind and also invoking the workflow

0 0
replied on October 8, 2014

Mike, isn't this called ... Quick Fields? :)

 

But more seriously, are you envisioning this magical action taking place only at the beginning of a Workflow (like Quick Fields) or at any time during the process? 

2 0
View 1 previous reply
replied on October 8, 2014

Quick Fields is... well, you know about me and Quick Fields.  :)

 

Quick Fields could be set up to do that for a well-defined set of documents.

 

I'm looking for something with some intelligence.  :)  Feed it documents it has never seen before and it's smart enough to figure out what it is and how to extract data from it.

 

Of course there would be exceptions, but we can route them to a person as necessary.

 

I can see it happening any time during the process.  I have a process for procurement projects, and documents are added to a project folder along the way.  It would be nice to have those documents automatically identified as they are added.

0 0
replied on October 10, 2014

Love the Invoice idea.  I tried it in Quick Fields, but there are too many variables on invoices (every one is different) to get any good results.  You might get six invoices in the mail in one day, but each one is from a different company, so scanning in a batch of those six invoices did not work.

1 0
replied on January 29, 2015

I am using Quick Fields for invoices and am using Zone OCR and Classification. Currently I have 350 classifications extracting what I need from the invoices. It is a slow process, 2 pages per minute but I have a far better accuracy level than when page OCR was being used. 

0 0
replied on January 30, 2015

If you were at Empower, you might have seen the class in which Carl Sykes talked and showed some of the next version of Quick Fields. I believe what you are looking for will be baked into the next major release and will make setting up new sessions much quicker and simpler for the less technically minded of us.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...