Skip to end of metadata
Go to start of metadata

This article describes the Delete data management policy action. There are different ways to delete conversations from the system and manage data retention, for more information, refer to Data retention.

A delete data retention policy allows defining a set of filters to find conversations which have to be deleted from the system.

Once the policy is executed on conversations that match the filtering criteria, the conversations will be deleted from the storage along with all related metadata from the database.

The system also allows deleting specific files only by defining the file extensions. When one or more file extensions are defined, other remaining files and the database record will not be deleted, only the files with the defined extensions. If you define the file extension of the only media file for the conversations, the system will not execute the deletion action.

Conversations deleted by a delete data management policy are not recoverable and cannot be undone.

To set up a deleting data management policy, follow the steps below:

Step 1 - Follow the generic policy creation steps described on the following page: Data retention policies

Step 2 - Select Delete as the action.

Step 3 - Optionally define the file extensions under File Extension(s), to delete specific files only related to the selected conversations. When you define a file extension filter, other remaining files and the database record will not be deleted, only the files with the defined extensions. Multiple extensions can be defined separated by commas (,) as follows:

To delete *.vf files only, define: vf

To delete *.vf and *.vmf files only, define: vf,vmf

Step 4 - Select your filters to specify which conversations should be deleted by this policy.

Step 5 - Click on the Check Effect button to verify the number of conversations affected by the policy. In this way, you can avoid misconfiguration and unwanted deletion of conversations.

Step 6 - Click on the Save button to save the policy configuration. Once the policy is saved it is effective and will be executed according to the policy execution schedule.

 

  • No labels