The destruction business logic is part of release 24.1 and revised in version 25.4

Introduction

A new collection of standard metadata fields has been introduced in https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4040359937 to allow for the destruction of an object as part of its lifecycle by changing the https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4082958355 to ultimately the value Destructed. In version 25.4, the fields for automatic destruction have been revised for improved clarity and functionality.

Destruction

Destruction has the following implications

The https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4082958355 changes to the value Destructed
Generates an Event of type UPDATE.DESTRUCTION
Automatic destruction is available if the https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4064378938 is Data. Hence, if it is one of the https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4064772158, all its child representations will be logically deleted but the data object itself is not deleted. The effect is only the metadata remains whereas the storage will be reclaimed when permanently deleting the representations after the recycling grace period.
Automatic destruction is not available if the https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4064378938 is flat data

Planning for Destruction

If the metadata field Governance.AutomaticDestruction.ExpectedDate is filled out with a particular date, then the system will automatically perform the destruction at the given date with the effect described in the previous section. See https://mediahaven.atlassian.net/wiki/spaces/CS/pages/5076418561/Metadata+25.4#Governance for the full reference of the new metadata fields.

The Governance.AutomaticDestruction.ExpectedDate field can be:

Set manually by the user,
Populated via a custom plugin, or
Calculated automatically by the standard functionality.

Standard case: Destruct

If Governance.DestructAction is set to Destruct, the system can automatically calculate the ExpectedDate based on Governance.RetentionReferenceDate and Governance.RetentionPeriod:

Governance.AutomaticDestruction.ExpectedDate = Governance.RetentionReferenceDate +
Governance.RetentionPeriod.Unit * Governance.RetentionPeriod.Term

This calculation only occurs if all of the following conditions are met:

Governance.ArchiveNomination = Destruct
Governance.RetentionReferenceDate is filled in
Governance.RetentionPeriod is filled in

Once the calculated ExpectedDate is reached, destruction is automatically executed. After execution, the actual date is stored in Governance.AutomaticDestruction.EffectiveDate.

Note that Governance.DestructAction can only be set to Destruct if the module plugin GOVERNANCE_DESTRUCT_OBJECTS is active. In release 25.3, its legacy module DOSSIER_DESTRUCTION can also be used.

Destruct after approval

If Governance.DestructAction is set to DestructAfterApproval, destruction is still executed automatically once a Governance.AutomaticDestruction.ExpectedDate is present.
However, in this mode the standard functionality does not calculate or populate the ExpectedDate.

A custom plugin can be used to introduce an approval step: after setting Governance.ProposedDestructionDate and once approval is granted, the plugin sets or calculates the ExpectedDate. From that moment onward, destruction follows the same automatic execution flow as in the standard case.