Tested in Alfresco 4.2.3 and RM 2.2
As you know, Alfresco has an events driven Retention and Disposition process, as part of the optional Records Management (RM) module.
There is a job executed that checks for the eligibility of any file to have a retention/disposition action automatically applied to it. If the action is manually applied before the job has a chance to run, there’s no harm done. But this job comes along behind and cleans up any missed files that are eligible for an action.
The actions that are available to be automatically executed are Retain, Cutoff, Destroy, Transfer and Accession.
The actions, however, that are actually configured to auto-occur out of the box are Cutoff and Retain. This means that if you want a file destroyed as soon as (or at least within 5 minutes in an out of the box configuration) it has become eligible for destruction, you have to do a little bit of configuration. Continue reading Changing the Automatically Applied Disposition Actions in Alfresco Records Management