Better manage Dirty State in Navigation Context

When an Exception is thrown by a Listener marking the TX as Rollback only we end up with a DocumentModel in a Dirty state : it contains un commited changes.

This is good as long as we stay on the initial screen that generated the save tentative. But if we navigate to a new screen (i.e. new tab) we should automatically refetch the DocumentModel from the repository to avoid displaying un commited data in the UI.