Reverse / Rewind Edit Histories
Cradle has a change history mechanism that can be enabled for one or more item type(s) in the project’s schema using the Project Setup tool. There are several options for change histories, but once enabled, the mechanism will record details of all edits to items of these types. Cradle can record up to 2 billion edits to each instance of each item in the database. For each edit, the mechanism records:
- The user who performed the edit
- The date and time of the edit
- The reason for the change
- Details of the change, a set of:
- Which attribute was changed
- The old value of the attribute before the change
- The new value of the attribute after the change
The history of edits to an item can be shown:
You can now rewind edit histories so you can restore an item back to a state before a particular change or you can reverse a single edit in an item’s change history.
Reversing an edit is an exact undo operation. It reverses the change to every attribute that was modified by the edit. Rewinding a set of edits is analogous to performing a cumulative undo of all edits from the most recent edit back to, and including, the edit that you select.
To reverse an edit, select either Reverse/Rewind History in the above dialogue or choose History → Reverse/Rewind History:
The Rewind operation essentially reverses all edits working backwards from the most recent back to (and including) the selected edit. Its end result is to restore the item to the state that it was in before the selected edit occurred.
The access rights in Cradle projects can be set so as to allow several different users to modify a set of items (albeit not at the same time). When this occurs, the owner of the item receives an alert notifying them that someone else has changed one of his/her items. This new facility allows such edits to be reversed, as an undo operation. Indeed, if the undo operation is itself an error, then the undo, or series of undo operations, can themselves be reversed. |
