Data Retention Policy Mode

   Journey Manager (JM) The transaction engine for the platform.  |    System Manager / DevOps  |  All versions This feature is related to all versions.

Manager can be installed using either strict or relaxed data retention policy mode. This determines the default values of the global data retention management configuration, which are used throughout an entire Manager server or an environment consisting of several server nodes. We recommend using the strict mode in production environments, while the relaxed mode in development and testing environments.

To check the data retention policy mode of your environment:

1. Select System > System Info.
2. Scroll down to the Build Properties section and look for data.retention.policy, as shown below:

   

We recommend using the strict mode to constrain the potential amount of data retained within Manager by restricting the maximum age of transaction's data to be stored. It prevents problems related to long data retention, such as:

• Database growth
• Performance degradation
• Prolonged storage of sensitive 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

Both the strict and relaxed modes apply the global default settings to data retention configuration, however, you can override some of its values at the organization or form levels. The order in which data retention settings are applied is shown below:

• Global data retention configuration
• Organization's data retention configuration
• Form's data retention configuration

The default settings can be individually configured with a value that can't exceed the maximum value defined for each property.

When you configure the data retention policy in Manager, you need to consider the following:

• Optimal conversion rate – a user must be given an adequate time to return to and complete a transaction.
• System efficiency – a lean database makes Journey Manager more responsive.
• Privacy – 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 must be retained for the shortest possible time to minimize any potential security risks.

Manager is designed to keep data only for as long as it is required within the transaction life cycle. It is recommended to use the strictest possible data retention management policy to avoid excessive data base growth and potential problems during any recurring Manager upgrades.

However, often it is a balancing act between maintaining a lean, well performing and responsive system, while providing an adequate time frame for users to return to and complete their submitted forms. After sufficient time, given to users to complete their transactions, has elapsed, all incomplete transactions must be automatically abandoned.

You should ensure that Manager is correctly configured in a way that PII data is automatically purged from the transactions soon after the user has submitted their form to minimize any potential security risk. Therefore, we recommend using the strict data retention policy for any production Manager instances.

In some cases, you may want to change the data retention policy mode of your environment to test your data retention procedures. Switching relaxed to strict has no impact, but it all depends on how much you reduced retention days by. For example, if you want to have 180 days to start with and plan go back to 30 days after that, we recommend reducing days to 150, 120, 90, 60 and then 30. Keep at least 1 day between these changes to allow the Transaction Processing scheduled job to purge records in small batches.

Strict vs Relaxed Mode

There are differences between the strict and relaxed modes for the various data types. Let's look at each of them in more detail.

Saved Transactions

This setting determines how long to keep user saved transactions before they are abandoned by Manager and become finished transactions. The Manager environment setting is initially set to the default, but you can change it to any value that doesn't exceed the maximum. Organization and form level settings can be used to override the environment settings. However, they cannot exceed the maximum value.

• Strict mode: default is 30 days, maximum is 180 days
• Relaxed mode: default is 30 days, maximum is 2 years

Finished Transactions with PII Data

This setting determines how long to keep data entered by the user before it is deleted. The Manager environment setting is initially set to the default, but you can change it to any value that doesn’t exceed the maximum. Organization and form level settings can be used to override the environment settings. However, they cannot exceed the maximum value.

• Strict mode: default is 7 days, maximum is 30 days
• Relaxed mode: default is 7 days, maximum is 2 years

Finished Transactions

This setting determines how long to keep finished transactions before they are deleted. Finished transactions include transactions that have been marked as abandoned or completed. The Manager environment setting is initially set to the default, but you can change it to any value that doesn’t exceed the maximum. Organization and form level settings can be used to override the environment settings. However, they cannot exceed the maximum value.

• Strict mode: default is 90 days, maximum is 2 years
• Relaxed mode: default is 90 days, maximum is 5 years

Finished Collaboration Jobs

This setting determines how long to keep finished collaboration jobs before they are deleted. The Manager environment setting is initially set to the default, but you can change it to any value that doesn’t exceed the maximum . Organization and form level settings can be used to override the environment settings. However, they cannot exceed the maximum value.

• Strict mode: default is 90 days, maximum is 2 years
• Relaxed mode: default is 90 days, maximum is 2 years

Submission Data Extracts

This setting determines how long to keep submission data extracts before they are deleted. You can't override this setting, unless it's Manager version prior to 17.10 and it's in the relaxed mode.

• Strict mode: default is 7 days, maximum is 30 days
• Relaxed mode: default is 7 days, maximum is 2 years

Submission Properties

The setting determines how long to keep submission properties before they are deleted. You can't override this setting, unless it's Manager version prior to 17.10 and it's in the relaxed mode.

• Strict mode: default is 7 days, maximum is 30 days
• Relaxed mode: default is 7 days, maximum is 2 years

Next, learn about data retention schedule.