Audit, history, rollback
How every change stays traceable: revisions, reading the history, rolling back to an old state, and what happens to files and relations along the way.
Topics in this subject area
- 1.What is audited
Which models have a history, which operations create a revision, and which revision types exist.
- 2.What a revision records
Number, time, person, IP address, browser, and that each database has its own revision log.
- 3.Reading the history
How
POST /{id}/historyreturns revisions page by page, which permissions you need, and why deleted objects have a history too. - 4.Rolling back to an old state
A rollback creates a new revision with the old content. What comes back (own fields, single references) and what does not (lists, deleted objects).
- 5.Rollback for files
How the file content is copied back during a rollback, and why the current state is saved first.
- 6.Audit is not the same as system fields
The difference between
_createdOnon the object and the revision history. - 7.Data protection and retention
Which personal data the audit contains and how long revisions are kept.