Journey Manager (JM) Previously known as Transact Manager (TM). | System Manager / DevOps | v5.1 & Higher This feature is related to v5.1 and higher.
Manager collects important information in relation to data retention management, which includes the status of any individual transaction to keep track of PII data that has been purged or is due for purging. This information can be found for each transaction in the Transaction Status tab as shown below.
This includes details about the data retention stage reached in the life cycle of this transaction. For instance, from this transaction data purging details we can tell that the PII data was purged (as indicated by Transaction Data Deleted being ticked) a few minutes after it had been scheduled to be purged (as indicated by Actual Transaction Data Purge and Scheduled Transaction Data Purge). Also, the transaction data record is due to be deleted on the 25 March 2018 (as indicated by Scheduled Transaction Record Purge).
Note that after the 25 March, this transaction along with its submission details will no longer exist. Only a transaction history record remains containing some details about the transaction.
You can check the data retention summary, which is useful for monitoring the overall performance of the data retention management and assists in diagnosing and tuning of any data retention management issues.
Manager has two modes of data retention policy, strict and relaxed, that determines the length of time transactional data is retained. The selected policy can be customized at the environment organization, or form levels.
It's recommended to use the strict policy mode, which enforces less transactional, historical and log data retention as opposed to the relaxed policy mode.
Manager uses various scheduled jobs that automatically purge transactions that have reached their maximum age.
Next, learn about data retention policies.