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

Question

Question

Is Records Management for Forms in the product roadmap?

asked on June 24, 2015

At the moment it is not possible to set retention schedules on Laserfiche Forms data, or individual Workflow instance histories (though you can set a global expiration on Workflow data). Even if the archived Form in Laserfiche is destroyed after a certain amount of time, the Form data and image in the Forms app is still present.

Will Laserfiche be adding Records Management to Forms and Workflow at some point? Ideally, you would be able to apply some kind of retention schedule on an individual Workflow and an individual Form BP.

1 0

Answer

SELECTED ANSWER
replied on June 24, 2015

Thank you for this feedback. We currently do not have plans to tie the Records Management features you find in a Laserfiche repository to Forms/Workflow instances. Please help us evaluate this feature request by answering the following:

Is it sufficient to just have simple retention cycles (e.g. after 90 days, delete the process data)?

   If not, what features of Records Management are important to your use case?

What data of a workflow instance would you consider a record?

If a retention cycle was tied to a Forms process, do you see it being different then the archived document's retention cycle?

When a forms process is destroyed, what do you envision happening?

When a workflow instance is destroyed, what do you envision happening?

 

1 0
replied on June 24, 2015

Ed, for us being able to set simple retention cycles on a per process basis would be sufficient. This would allow us to retain data for X amount of days incase something went wrong in the Forms process and then rely on the retention schedules setup in Laserfiche for the actual documents.

When a forms process instance is destroyed, we would expect to see all data related to that submission completely deleted from the Forms database.

3 0

Replies

replied on June 25, 2015 Show version history

I think organizations will interpret the rules differently. Since we have to service organizations with levels of varying strictness around their policies, I think we would prefer to provide options.

I agree with Blake that typically the archived document is the "document of record" when it comes to records retention. However, I do think there may be metadata associated with Forms processes that doesn't always make its way in to Laserfiche with the archived Form, such as process failures. If we believe that to be true, then it is not enough to assume the archived Forms will be enough. Furthermore, we may have a process that has no Form archival in Laserfiche, so the metadata exists nowhere but the Forms database.

- I do not think it is sufficient to have a global expiration, though we should consider having that as a secondary option.

- The feature that is important is the ability to associate an Admin Console retention schedules with a specific Forms Business Process. Any forms assocaited with that BP would be on that retention schedule. Rather than automatically deleting, they would simply be flagged as ready to be destroyed - someone has to take direct action to destroy the data (just like in the Client).

- Regarding what constitutes a "record" in Workflow, I would consider an individual Workflow instance to be a record, including all of its tokens, as well as everything that you see when you open up that Workflow Instance in the Designer for troubleshooting.

- I do not see a retention attached to a Form being different than the archived document, but I do see why they need to be separately configured - you may not be storing the actual Form, just the data in the business process.

- When a Form process is destroyed, I envision that it didn't happen automatically - it just teed it up to be destroyed, and someone had to take an action. I see the entire instance being destroyed as though it never happened. It wouldn't be enough to scrub the image, since variables contain all of the valuable data. And once you scrub those variables, there's nothing left to show.

- I feel the same way about destroying a Workflow instance. Like it never existed.

1 0
replied on June 25, 2015 Show version history

Thank you for the detailed response. I'll add this feature to our backlog and bring it up with the various teams. There is currently no timeline for the implementation.

1 0
replied on May 16, 2017

Any update on this?

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

Sign in to reply to this post.