History and versions
Nothing writes a board without leaving a version behind — a person’s save, a sweep, an import or a restore.
Versions
Section titled “Versions”- One per editing session. Saves by the same person, from the same source, within ten minutes, fold into one version.
- Each says where it came from: a person, a scan, an import or a restore, and what changed since the version before.
- A write that changed nothing files nothing. A sweep that saw the same hosts again adds no version.
| Action | Needs | What it does |
|---|---|---|
| Browse versions | View | Newest first, up to 200 |
| Open one | View | The board as it stood |
| Compare | View | Against the version before, another version, or the board now |
| Name the board now | Edit | A named version is never folded, never purged |
| Restore | Edit | Puts the board back as it stood |
Restoring
Section titled “Restoring”A restore is a write, not a rewind: it becomes a version of its own, so it can be undone the same way. It puts back the devices, connections, zones, notes and documents exactly as they were in that version, and leaves the rest of the board — import records, for instance — as it is now. If somebody saved in the meantime, you are told before anything is overwritten.
The change log
Section titled “The change log”Beside the versions, the board keeps a log of which elements each write changed and how — worked out by Infrality from before and after, never trusted from the client. Select a device to see its own history: who changed what about it, and when.
How long
Section titled “How long”Unnamed versions are kept for 90 days, except each board’s newest. When a board reaches 200 unnamed versions, sweeps’ versions go first. Named versions stay until you unname them. The change log is kept for 90 days.