How do I enforce document retention policies?
Configure a retention policy, assign it to the intended documents, and verify the native retention state and disposition behavior. FormKiQ Web supports assignment rules and reconciliation, but v4.3.8 browser rules do not immediately cover every direct API change. Validate backend assignment for each ingestion path when retention must apply before any later reconciliation.
Define the policy and assignment
Set the policy's date source, retention period, and any disposition date. Decide which document types, folders, or exact attribute values select it. Configure the required policy entity/process resources if the workspace has not been prepared.
Preview assignment against existing content before reconciliation. Documents already carrying a different policy should be reviewed rather than silently reassigned. Test intake from Web, direct APIs, gateways, and migration tooling separately.
Verify retention and disposition
Inspect the document's Governance panel and native state/dates after assignment. A custom retentionDate attribute is not proof that a native retention policy is enforced. Test conflicts and legal holds as well as ordinary expiry.
Workspace disposition can use soft deletion or permanent deletion. Review trash retention and the effect on existing deleted content before changing settings. Test a short policy only with disposable documents. FormKiQ retention, S3 Object Lock, backups, and regulatory policy approval are separate layers.
Edition and configuration
Retention and governance require the relevant commercial backend services and permissions. Confirm the installed backend/Web versions and assignment behavior for every ingestion client.