Asset Deletion 1

Introduction

Assets are deleted based on asset version management in a 3 step deletion process.

• mark-deletion: First, the assets will be marked, which is indicated with a trash icon on the asset.

• do-deletion: Next, the asset will be deleted in the Oracle Database.

• storage-deletion: At last, the files will be deleted from the censhare file system

This article is a short description of this process.

Important hints

The Asset Version Management rules can be found and configured in 'censhare-Admin/Master data/Asset Versions'.
The command configuration for the 3 steps asset deletion process can be found in 'censhare-Admin/Configuration/Modules/ Asset Deletion'.

1. mark-deletion

The command configuration for mark-deletion can be found in 'censhare-Admin/Configuration/Modules/Asset Deletion/Mark Asset Version for Deletion (automatic)'.
mark-deletion, is by default running on the server at:
<cron pattern="0 4 * * *"/>
Mark Assets Version for Deletion. Makes the trash symbol appear next to the asset versions as configured in version management in censhare Admin Client.

2. do-deletion

The command configuration for do-deletion can be found in 'censhare-Admin/Configuration/Modules/Asset Deletion/Delete Assets (automatic)'.
do-deletion, is by default running on the server at:
<cron pattern="30 3 * * *"/>
Delete Assets only from the database and write the file-path into the storage_deletion_queue.

Hint: Due to the default used cron pattern there's an intended 24h window between mark-deletion and do-deletion (as shown in cron pattern here).

3. storage-deletion

The command configuration for do-deletion can be found in 'censhare-Admin/Configuration/Modules/Asset Deletion/Delete Files (automatic).
storage-deletion, is by default running on the server at:
<cron pattern="0 5 * * *"/>
Delete the files, based on the entries in the storage_deletion_queue, from the file system.