Right to Be Forgotten

 

According to the General Data Protection Regulation (GDPR) compliance, personal data must be erased immediately when it is no longer needed for the original purpose. Adhering to this regulation, ibi MDM has introduced the right to be forgotten feature to permanently delete records. Permanent deletion completely removes the record from all versions of ibi MDM.

In ibi MDM, you can mark records for permanent deletion. Some common scenarios when you can mark records for permanent deletion are as follows:

• Records that become invalid over time
• Records that are no longer used

To use the right to be forgotten feature, define the RIGHT_TO_FORGET attribute and any other custom attributes (with the string or boolean data type) in ibi™ MDM Studio. For information about creating attributes and defining the attribute values, see ibi™ MDM Studio Repository Designer User Guide.

How It works

After you specify the attributes in a repository in the Scheduler UI from the Configurator, scheduler automatically generates the job policy file. The file contains repository and attribute details. The Right To Be Forgotten scheduler job accepts a list of repository names along with the enterprise names, and locates the golden copy records from the specified repositories. The job triggers a procedure to delete records.

The records are deleted from the specified repository and the Right To be Forgotten event is generated. You can check the event details on the Event Log page. For information about the event, see the "Events Generated during Purge" section in ibi MDM User Guide.

For information about configuring the Right To Be Forgotten scheduler job, see the following sections:

• Scheduling Jobs from the Configurator
  • Job Type Common Parameters
  • Job Type Input Parameters
• Scheduling Jobs Using CronSchedules.xml (Alternative Approach)
• Scheduler Examples