DCM Audit can generate a lot of data over time. Some of the data should be kept for a longer time to follow up compliance trends and other reports while some other data is more useful only short term.
DCM application comes with predefined Auto Flush records that should be used for data clean-up. By default, these records are inactive, but we recommend activating data clean up routines during the first year of DCM usage.
Default Auto Flush Records
| # | Tablename | Matchfield | Age in seconds | Active |
|---|---|---|---|---|
| 1 | x_jugr_dcm_audit_results | sys_created_on | 31,536,000 | false |
| 2 | x_jugr_dcm_m2m_uam_ar | sys_created_on | 2,592,000 | false |
| 3 | x_jugr_dcm_m2m_uam_ar | sys_created_on | 2,592,000 | false |
| 4 | x_jugr_dcm_audit_instance | sys_created_on | 94,608,000 | false |
| 5 | x_jugr_dcm_unique_audit_message | sys_updated_on | 31,536,000 | false |
- Audit Results (x_jugr_dcm_audit_results) are used for trends on an Audited Record level. These records should be deleted after a year, but can be deleted sooner if the number of Audit Results gets very high.
- A general rule of thumb is that the number of Audit Results should be kept below 10 million.
- UAMs Related to Audit Results (x_jugr_dcm_m2m_uam_ar) are used to relate Unique Audit Messages to Audited Records to show more detailed trends on deviations and showing Unique Audit Messages in the Audit Results view.
- Auto Flush records include two rules for these m2m records for historical reasons.
- Currently, activating just the one that doesn’t have any conditions is enough.
- If the total count on this table gets very high (more than 10M), then we recommend deleting these sooner.
- The second “UAMs Related to Audit Results” Auto flush record will delete relations to non-compliant Unique Audit Messages also
- This rule is irrelevant when the rule without conditions is already active.
- Audit Instance (x_jugr_dcm_audit_instance) records will delete all related audit results and m2m records to UAMs also, so this is the easiest way to clean up old data, but the number of Audit Instances doesn’t usually get that high and enables reporting long-term trends if these are not deleted at all
- We recommend deleting “UAMs Related to Audit Results” and “Audit Results” before deleting the Audit Instances.
- Only delete these if you are sure you don’t need data compliance trends over a year-long period.
- Unique Audit Messages (x_jugr_dcm_unique_audit_message) records that have not been updated for a long time. DCM Audit keeps updating the unique audit messages, as long as they are still valid. This auto-flush rule deletes expired and fixed messages that have not been updated in a while (age in seconds).
Days in seconds
| Seconds | Days |
|---|---|
| 31 536 000 | 365 |
| 15 552 000 | 180 |
| 7 776 000 | 90 |
| 2 592 000 | 30 |