Data Lifecycle

This section explains how records move from draft to approval, how updates are handled, and when deletion is allowed or blocked.

Lifecycle states for controlled records

Many workflow-enabled records follow the same status path:

• CAPTURED (draft)
• PENDING_AUTH_L3, PENDING_AUTH_L2, PENDING_AUTH_L1 (approval stages)
• AUTHORIZED (approved and active)
• REJECTED (returned for correction)
• DENIED (permanently blocked)

Update and amendment behavior

The update path depends on current record status:

• Draft and rejected records can be edited directly.
• Authorized records in sensitive areas use amendment workflow instead of direct overwrite.
• Amendment approval uses maker-checker separation (a user cannot approve or reject their own amendment).

This pattern is actively used in domains such as customer, agent, and COB configuration updates.

Deletion and deactivation rules

remoteEaze uses controlled deletion rules for business records.

Common behavior includes:

• soft-delete markers (deletedAt) instead of irreversible removal
• audit-stamped updates when records are deactivated or deleted
• integrity checks that can block deletion even when soft-delete is used

Concrete examples:

• Authorized customer and agent records cannot be deleted directly.
• Denied customer, agent, and custom-field records are blocked from deletion.
• Authorized custom fields require amendment flow instead of direct delete.
• Agent deletion is blocked when the agent still has onboarded customers.
• Branch, department, cost-centre, and reference-data deletion can be blocked when active records still depend on them.

Documents and report history

Lifecycle controls also apply to uploaded documents and generated reports:

• Uploads create lifecycle history entries (start, completion, download access, and deletion).
• Uploaded files move through review states before they become ready for use.
• Generated report files are stored with expiry windows for retention control.