Skip to content

Autosave

The Autosave system ensures that changes are saved automatically, minimizing the risk of data loss and reducing the need for manual saves.

Autosave Triggers

Event Description
Field change Whenever a user modifies a header field, an autosave is registered.
Grid line blur When a user finishes interacting with a line in a grid (i.e., the line loses focus), autosave is registered.

Autosave Behavior

  • Debounced execution: Autosaves are debounced with a 1000ms delay to prevent excessive saving during rapid edits. This means autosave will only run after 1 second of inactivity following a change.

  • Autosave during field updates: If the processing of a field update is still ongoing, the autosave requests are buffered and executed only after the processing is finished.

  • Dataset and row-level independence: Even though autosave is enabled for a layout, autosaves trigger independently on each dataset. Furthermore, in a Document List dataset, this independence is also applied per each document in the list. This means, each document can be saved without waiting for the other, in case of rapid updates.

  • Layout destroy: Before a layout can be destroyed (e.g. the user closes the layout), any buffered autosave is first flushed and executed, then the navigation occurs. This ensures data persistence and prevent the "layout is dirty" confirmation dialog.

  • Layout actions: Before executing any layout action (e.g. a workflow action), any buffered autosave is first flushed and executed, then the navigation occurs.