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

Question

Question

Trigger for Retention when the Event is "two most recent"

asked on February 10, 2020

Any ideas on how you could create a trigger for starting retention when the Event is something like, Period covered by two most recent audits?

We are revising our Records Retention Schedule and one of the classification groups is for auditing by external parties, such as government grants where the government audits our handling of the grant funds.

The classification comments explain that the intent is to keep the two most recent audits on any topic.  

I'm considering removing this Event option from the revision recommendations and just keep these audits for eleven years simply because I cannot figure out how to trigger the retention start date on these odd ball items that could be stored anywhere (in topic folders).  We have too many of these types of audits to have someone just keep an eye out for them!

My retention triggers are mostly set upon documents dropping into folders:  Workflow copies the retention from the folder onto all records dropped into them.

I have triggers for Events on folders for Active/Inactive, where if the project is Active, retention (on the records within) is on hold until the folder field for Active/Inactive is switched to Inactive.

ANY IDEAS?

0 0

Replies

replied on February 10, 2020

I'm looking at this folder structure with an Event control on the folder pointed out with the red arrow, but not sure if this is the ONLY way (or best way!!) to do this in Laserfiche:

 

Of course, everything depends on the individuals bringing these records in.  I also considered whether I should have a separate template for these.  That is certainly doable, however, again, getting people to remember to pick this template on these very occasional records is where I see this falling down.

Unfortunately, the terminology is also not consistent.  Some of these records use "audit", some "annual review", some "executive report", etc.; so, setting Workflow up to watch for these may not ensure compliance any better.  I do already have workflow watching for trigger words such as "compliance" in the document names in the hopes of catching some of these.

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

Sign in to reply to this post.