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

Question

Question

Workflow Testing/Modeling Space in Production Environment

asked on March 12, 2014

What working environment do end users create, in a Laserfiche production repository, to develop and test workflows? This is a single repository environment.

If data is copied from production into folders in this environment, how do you safe guard against any workflow action on original data in production?

It has been suggested that when data is copied in Laserfiche, a new Laserfiche ID is assigned to the copy. Consequently, workflow actions performed on this copied data can't affect the original data.

Any comments/experience on this issue would be appreciated.

Mike

0 0

Answer

SELECTED ANSWER
replied on March 12, 2014 Show version history

Hi Michael,

 

If you want to test out workflows within a single repository you could create an additional folder structure to use for testing.  For example, you could create a root level folder called 'Test Environment' that has a copy of the rest of the repository's folder structure inside of it.

 

Then you would set up security so that only administrators and Laserfiche products (like Workflow, Forms, Quick Fields) can see and access the 'Test Environment' folder and its contents. That way the users won't be bothered by seeing a bunch of extra folders.

 

When it comes to testing out a workflow, you'll need to make sure that it is only operating within that 'Test Environment' folder structure, which can be done by including the 'Entry Path starts with...' condition within your starting rule.

 

You are also correct that copying a document in the repository will give it a new and unique Entry ID, because it is a separate entry.

 

Other users may have more ideas for you, but if this answered your question, please mark it as a user approved answer!

0 0

Replies

replied on March 12, 2014

Thank you for the comprehensive answer.

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

Sign in to reply to this post.