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

Discussion

Discussion

Enhancing RM assignment for Flexible records

posted on December 16, 2020

I was discussing this some RM consultants they other day and wanted to put this out there to see if any others agreed.

A question they raised was how Laserfiche separates the Classification of documents (application of a Template) from the application of the Retention Schedule, where in their mines the two are tied together.

As I thought about this I wondered the same as Flexible Records Management (or RM in place) would tend to lead to this thinking. That as a user assigns a template, that a RM Cutoff/Retention would be associated to it and applied automatically.

I know someone is going to say that this can be done with workflow, but then you need to build and maintain those Workflows for every new Template built. Where the thought would be that as you define your Templates, there would be a tab similar to the Security tab to associate a RM Cutoff/Retention schedule to the template so each time a document is ingested/classified, the appropriate retention would be applied without operator intervention.

I'm just thinking this would be a far more elegant solution and overcomes many of the challenges with customers understanding the relationship with metadata assignment and RM

 

 

4 0
replied on December 17, 2020

Great question Steve. We do currently have a "TRM" workflow that references a central data source, analyses the templates that have been applied to documents and the values of certain fields before moving documents to retention folders. This works well, but it took months to figure out, build and test this process. Plus the maintenance. A built-in ability to tie a template to the retention schedule would be very valuable!

1 0
replied on December 17, 2020

Thanks Olga. If we could tie Security Tags into this as well, I think we could also decrease the amount of granular security required as well for some of these deployments.

0 0
replied on December 17, 2020

I would concur with Steve, right now to leverage the metadata to drive the RM activity via workflow is difficult as it also does not let us reference tokens. Instead we are having to use a SQL lookup to reference the appropriate values via lookup.

0 0
replied on March 2, 2021

We are doing what Armando said with SQL lookup tables. FRM is very heavy on the setup, workflow and table building. The positive outcomes are not having to maintain shortcuts and records can be moved based on end user need instead of RM driving the repository structure. 

Workflow, templates and RM would talk to each other in a perfect Laserfiche world.

0 0
replied on December 16, 2020

This would be useful!

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

Sign in to reply to this post.