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

Question

Question

9/10 hybrid

Workflow Laserfiche Version 9 Business Processes
Updated April 6, 2016
asked on April 6, 2016

Good morning,

 

My legal team is currently looking into adding the DocID of a document into the footer of certain files with the use of a workflow or business process. They want to use this as a form of version control because they don't like the current versioning that Laserfiche offers. Any help would be greatly appreciated.

 

Thank you!

-Evan 

0 0

Answer

SELECTED ANSWER
replied on April 6, 2016

The Workflow itself should be the easy part, though you'll need to figure out what starting event is appropriate.  If it's an electronic document you'll need a library to manipulate that type of document.  Otherwise you can apply a stamp or something.

0 0

Replies

replied on April 6, 2016

This sounds possible, though I'm not sure how it solves your problem.  How far have you gotten?  Which part are you stuck on?

0 0
replied on April 6, 2016

To be honest, I don't think it will solve the current problem with versioning, but it's something that our CLO requested that I figure out how to do. I'm not terribly good with workflows, so I haven't really gotten anywhere with it. I was actually curious if it was even possible to begin with.

0 0
SELECTED ANSWER
replied on April 6, 2016

The Workflow itself should be the easy part, though you'll need to figure out what starting event is appropriate.  If it's an electronic document you'll need a library to manipulate that type of document.  Otherwise you can apply a stamp or something.

0 0
replied on April 6, 2016

I'm sort of confused. The document ID does not change between versions with Laserfiche versioning, so a footer wouldn't really help.

On the other hand, if you prefer to use different documents for different versions, why not use link groups to indicate the order?

What is the problem with the versioning system that a footer would solve?

 

0 0
replied on April 6, 2016

I tried explaining that to them as well, but this is what they still want to be incorporated. From what I've gathered, they don't want hard versions in Laserfiche being made everytime they make an update to a document to allow the approval process to occur. But it seems that whenever they make a change, instead of the document going to 1.1 (which would be a sub version while the document is being passed around), it immediately goes to the next "hard" version of 2.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...