Manual Data Purge
Journey Manager (JM) The transaction engine for the platform. | System Manager / DevOps | All versions This feature is related to all versions.
Manager has an automated process in place that continuously applies data retention policies to all transaction data, including PIIPersonally Identifiable Information (PII) is information about an individual that can be used to distinguish or trace an individual‘s identity, such as name, social security number, date and place of birth, mother‘s maiden name, or biometric records; and any other information that is linked to an individual. In Europe, PII is known as personal data. data, and purges it accordingly. However, you can purge data of a selected transaction manually using UI. This will mark the transactions for immediate deletion so they will be removed from the system during the next run of the Transaction Processor service, which is usually run every 5 minutes by the Transaction Processing scheduled job.
The data is not removed immediately, so check the Repeat Interval of the Transaction Processing scheduled job configuration in your environment.
The data is not removed if the transaction is a part of a collaboration job, so you must manually purge it.
You can use this functionality to:
- Delete transaction's data as per customer's request.
- Free up server resources, such as OS file system or a database space, by delete old transactions.
To trigger a data purge manually:
- Select System > Data Retention Management.
- Click the Retention Settings tab to verify the current settings and adjust them so the manual purge removes data that needs to be removed.
- Click Apply Policy to run the Transaction Processor service, which purges data and displays a report with actual number of records been purged.
Next, learn about data retention policies.