cbmi/django-cilantro — Issue #31: UX of altering saved reports
Author: bruth
Created: 2011-10-18 20:46:47+00:00
State: open

So there are two schools of thought here:

- **document-based** - every change made to a saved report is recorded, but not immediately applied to the original report
- **pro** - a user can revert to the report's pristine state in case they are unsatisfied with their changes
- **con** - this requires an explicit action by the user to persist and unsaved changed made to the report
- **WYSIWYG** - any changes to the state of the currently active saved report will be applied and saved immediately.
- **pro** - this, of course, does not require any explicit action by the user to save changes.
- **con** - if a user performs a hefty destructive action that significantly alters the report's state (e.g. remove all data columns), there is no way to revert the change.

Ultimately, the latter experience is preferred, but only if there is a way to _undo_ changes actions.