Span.Eco.AutoSave lets you configure a ViewModel for users who should have field-value changes saved automatically instead of using a Save button.
What Span.Eco.AutoSave does
Span.Eco.AutoSave is a ViewModel tagged value. Set it when the page should save values entered or changed in fields automatically as the client sends those changes to the server.
This is useful for an interaction model where users edit data without an explicit Save button, such as a mobile-oriented page.
Configure automatic saving
- Open the ViewModel for the page.
- Add or set the ViewModel tagged value
Span.Eco.AutoSave. - Verify that changing a field value produces the intended saved result.
- If the page no longer needs an explicit Save button, configure the page layout so that the sidebar does not expose it. See Documentation:Auto save.
What is saved automatically
Automatic saving covers values changed in fields.
For example, if a user changes a customer's phone number in a field and then continues working, Span.Eco.AutoSave saves that field-value change without requiring the user to select Save.
Actions still require saving
Do not assume that every change on an auto-save page is saved. Changes performed by an action still need saving as part of that action's behavior.
For example, an action that creates a new order line or updates several related objects must save those changes through the action flow. Setting Span.Eco.AutoSave does not replace that requirement.
Choose the interaction model deliberately
The default MDriven application interaction model includes a Save button. This lets users undo and redo changes and provides a desktop-style editing experience. Use Span.Eco.AutoSave when automatic field saving is the intended user experience; retain explicit saving when users need the normal save, undo, and redo workflow.
For a manual alternative, including a periodic save that runs only when the ViewModel is dirty, see Documentation:Auto save.