Unlike interaction trails, the journal shows all activities which have happened on a specific model (or collection or view) at various time slots. It can be used to quickly check the evolution of model state over a period of time - as well as the various operation details which caused the state change.



Note Also works on selected collection and view.

Note Read operations are deliberately not shown as they don't change application state (and will only contribute to investigative noise). In future versions, we may have an option to switch on this behavior.

Tip Remember that this data can be cleared out as described here