1) dont have a navigation menu on an edit page
2) use a non-persistent object to enter the data, and only copy that to the persistent object in the save flow. That way you never have to worry about the dirty state of an object.
I provided the option in the other forum question, but I myself have been searching for that widget for some time.
Looks like the development team had chose to discontinue.
You could also develop a similar Javascript action or widget which could track
- Browser refresh
- Navigate from one page to another
- Browser close action etc
However, if you are saving the state of the object when the editing is in progress for showing some dependent reference selector then it will be difficult to revert with leave action widget or similar thing. In that case you could follow Lennart’s suggestion. The only problem however is, implementing the same pattern across the application and probably having duplicate NPE’s with same schema.