Editorial draft available to read. Factual and language review is pending. Examples are illustrative.
Decision and scope
A change history should explain business changes through an actor, timestamp and record version. Identify the field, previous value, new value and relevant reason. Do not replace useful explanations with technical event codes that only the implementation team can interpret. Keep the history separate from the current editable value.
Illustrative example
Illustrative example: a delivery date moves from Monday to Thursday after supplier confirmation. The history links the approved request and distinguishes a human edit from an automated synchronization. The current screen displays Thursday while the history preserves the earlier commitment and the basis for changing it.
Acceptance check
Test concurrent edits, bulk operations and deactivated user accounts. Keep the actor identifiable without recording secrets in logs. Accept the history when someone uninvolved in the change can reconstruct what happened and which decision justified the resulting state.
Key takeaways
- Accept the history when someone uninvolved in the change can reconstruct what happened and which decision justified the resulting state.