Backfill retention metadata
Populate policy and due-date metadata for existing module records that lack it.
Before you start
Compliance View opens the workspace; Create is used for new intake, Edit for review/approval and Delete for deletion. Each action also validates its record.
Follow these steps
- Check policy definitions first.
- Run the backfill action.
- Note the processed and updated counts.
- Go to a sample of records to confirm due dates and policy keys.
- Run a dry run before execution.
Fields, rules and limits
- A dry run previews eligible actions. Legal holds exclude covered records; executing retention can anonymise or delete data according to its policy. Review the selected record types and current dry-run output before execution.
Check it worked
The linked entity, saved state, dates and evidence match the intended task.
If something does not look right
If the expected result is missing, check the saved record, the current workspace and the action’s permissions. Record the exact validation message; do not repeat a state-changing action until you know whether the first attempt saved.
Questions and answers
Does a parsed document count as approved?
No. Parsing supplies suggested values. A reviewer must verify the linked entity, evidence and required fields, then use the separate approval action.
Is the generated PDF the original certificate?
No. The system PDF reflects the saved compliance record or notification. Open the original source evidence separately when checking the document supplied.