Deletes and the audit log
Deleting asset records by accident is expensive, so destructive actions ask for confirmation and leave a trail.
What deleting asks for
Section titled “What deleting asks for”| What | Confirmation |
|---|---|
| Item | A reason, and typing the item code |
| Type | A reason. Only types with no items can be deleted. |
| Document, comment, user | An optional reason |
Deleting an item removes its own documents and comments, unassigns the parts that were installed in it, and cancels its pending handover. Deleting a type removes its type and variant documents and takes it out of other types’ component lists.
Audit log
Section titled “Audit log”Every delete is written to the Audit log (/audit) with who, when, why and a snapshot of what was removed. Admins can restore from the snapshot:
- An item comes back with its documents and comments, and its former parts are reinstalled if they’re still free.
- A type comes back with its documents and its place in other types’ component lists.
A restore is refused if it would conflict with something created since, for example when the item code or type prefix is now taken, or the item’s type no longer exists. Restores are logged too.