-
Type: New Feature
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: ADDONS_7.10, ADDONS_9.10
-
Component/s: Retention
-
Tags:
We want a simple retention service for the platform.
A Retention Rule Facet
Schema:
- Retention Period
- Cut-off rule expression
- Cut-off Action
- Disposal Action
A Retention Enablement Facet
Schema:
- Retention status (Live, Cutoff, Expired, Legal Hold)
- Retention Start Date (a.k.a cut-off date)
- Retention End Date (a.k. Disposal Date)
- Events History ,list of complex (event name, date)*
- Cutoff Processed(Boolean)
- Disposal processed(boolean)
- LinkedRule
A directory for Cut-off Actions
A directory for Disposal Actions
A directory for list of events
A Jave Nuxeo Service with the following API
- fireEvent (eventId,docId)
- setRetentionStartDate (docId,date)
- setRetentionEndDate(docId,date)
- startLegalHold(docId)
- stopLegalHold(docId)
- enableRetentionOnDoc(docId)
- setRententionRuleOnDoc(ruleId,docId)
- createOrUpdateRetentionRule(retention Period, cut-off rule expresson, cutoff action, disposal action)
A RetentionProcessor interface with methods
- processCutoff (doc) and
- processDisposal (doc)
- startLegalHold()
- stopLegalHold()
The extension: “RetentionProcessorFactory”
that allows to define a custom RetentionProcessor (there should be only one, as having several seems overkill)
A default RetentionProcess class that removes ability to write a doc when starting cutoff and that sends document to trash when disposed.