Global Audit trail of changes
Please note that you need to have the following right to access this feature:
Project Audit trail access
Click on the Audit trail button in the action bar.
The audit trail tracks every change in the project. It displays the user, date, id of the change, model, instance, grid, coordinates, the property changed, and the new value.
You can order each indicator by clicking on the indicator name.
Stripped entries indicate that this change has not been saved to the database. Just click on Save Uncommitted changes in the top right of the window to save them.
Undo an action
Please note that you need to have the following right to access this feature:
Project Audit trail edition
To undo an action, open the audit trail. Then click on the Undo Action button on the right of this action. Do not forget to save the model to save this change to the database.
Warning
Changes are not deleted, just undone and an Undo event is added to the audit trail.
Audit trail of cells
You can also display audit trails only for a selected cell or range of cells.
Just select a range of cells then Right click > Audit Trail > Display audit trail.
The same popup window will appear as the global audit trail but only with information for these cells.
Retrieve original values
You can restore the original values of a range of cells by right-clicking on them, then Audit trail > Undo all changes. All changes applied to these cells will be undone.
Loading project
The project opens with the instance structure corresponding to the last version of the table of instance keys.
All the audit trail entrances are reapplied. It means that if an instance exists at a moment T, disappears in a T+1, all the relative alimentations to this instance (by direct data entry or by .csv loading) are reapplied.
It is possible that some data disappear for an instance (independently of the disappearing of the instance itself) if the version the most recent of inputs corresponding to those data :
did not contain data for an import in configuration 1.
did not contain data matching the key of the instance for an import in configurations 2.1 and 2.2.
It's necessary to be vigilant during import 2.1 using because it's done to treat all instances. Data can be deleted without notice if the .csv contains partial data for a sub-group of instances for example.
if this type of loading is used during a "load partial" for .csv which contains only instances of the loaded perimeter, concerned grids will be emptied for all the other instances out of this perimeter.