Relational tables enable efficient information storage for behavioural data not supported by the contact table. Although relational structures are more efficient, they often have increasing amounts of data which can eventually lead to a slowing down of tasks that use this data. Furthermore, regulations and best practices dictate that contact databases should not indefinitely keep expired information. In this context, the Automated Relational Data Removal tool allows you to configure rules that specify your expiration criteria.
|Access Path||> Configuration > Relational Data > Removal|
Relational Data Removal allows you to configure automatic deletion tasks using clauses to identify expired records.
The launch of the task is determined automatically by the platform. The task will be considered ready to launch one week after the last successful execution. Then, each day during less busy hours, the platform will handle the most urgent tasks. The job may not run exactly one week after the last run based on the platform's schedule, but the run will be delayed until the platform can do the processing.
Note: Tasks are limited to one per table.
Create a Task
In the Removal interface, use the Create button to configure a new task. You can edit an existing configuration by double-clicking or clicking the Edit button that appears on the task.
Choose a relational table
A popup window will open to choose the table and give a name to the purification task. The label should reflect the expiration rules for the relational table. For example, if the removal is for records created over a year ago and no longer active, use "Created over a year ago and inactive." This type of labelling facilitates the management of tasks and the validation of their operation.
After choosing the table, the add clauses component appears. Configure your clauses according to this guide: Clause Tool. Once you have configured the clauses, use the Compute button to validate the number of records targeted. If you want to view the targeted entries, you can use the Search in a relational table page to recreate the clauses and view the data.
If you are still in the creation window, click Create and continue located at the bottom right to bring up the activation button. When you're ready to activate, use the Activate button at the top right of the window. Be sure to save your changes before publishing; unsaved changes are not published and will be lost.
At the bottom of the Removal page, you will find the history of purge task launches. Review these results occasionally to validate that the tasks are running correctly and for the appropriate number of records. You can filter this list by the table in order to have the complete removal history for a specific table.