Restrict Form Autosave

By default the web client saves modified forms silently when you navigate away. This module patches the form controller so leaving a dirty record opens a dialog asking whether to save the changes. The same confirmation applies when paging between records. It helps every backend user avoid accidental saves.

1. 1

   Detect unsaved changes

   When the user tries to leave a form the controller checks whether the record is dirty. Clean records leave normally.

   • beforeLeave hook
   • Only dirty records prompt
2. 2

   Show the save dialog

   A confirmation dialog asks whether to save your changes. The user chooses to save, discard or stay.

   • Save
   • Discard
   • Stay on form
3. 3

   Guard record paging

   Using the pager to move to another record triggers the same check. Navigation is cancelled if the user does not confirm.

   • onPagerUpdate override
   • Cancel keeps current record
4. 4

   Applies everywhere

   Because it patches the shared form controller it applies to all form views without configuration. No menus or settings are added.

   • No configuration
   • Web client asset only

Back to version applications