Saving changes Flows

Keep changes from editing until confirmation of saving.

11 checks · 3 content groups

Checklist contents

Review progress

Step by step in flow

Track status, feedback, and next actions every step of the way.

Shows which parts can be fixedUse an explicit editing style or a direct representation of the fields that the user is allowed to change.

Try interacting

Do not ask to save without changesIf there is no difference with the saved data, keep the save button inactive and explain the status with context.

Try interacting

Recognize when changes need to be savedAfter the user edits, make it clear that the save button is active and there is still a way to undo the changes.

Try interacting

Shows the saving processNotifies that it is being saved, avoids repeated sending and keeps the user's edited content during the waiting time.

Try interacting

Confirm the saved versionAnnounce the results and return the button to the appropriate state so the user knows the current data has been captured.

Try interacting

Start the task

Compare information and presentation in context of use.

Indicates information that can be editedDistinguish the view and correct it if any, keeping the current value easy to check.The save button needs to reflect whether there has been a change or not; Do not notify saved before the system confirms.Example After renaming, the “Save changes” button turns on; While sending, write "Saving...".Mark changes as not yet keptIf you auto-save or need to press the button and state when the information is different from the saved copy.Check where it needs to be repairedSpecify invalid fields and keep the entered contents.

Feedback and results

Try the operation, change the status and continue working.

Response is savingPrevent duplicate requests and do not block unrelated interface sections.Report success or real errorAfter success, indicates data has been kept; When there is an error, keep the content to try again.Make a decision before abandoning the changeIf you leave the page with unsaved data, continue to edit, save or delete it on purpose.

Progress is saved automatically in this browser.

GUIDANCE

How to review

Indicates information that can be edited

The save button needs to reflect whether there has been a change or not; Do not notify saved before the system confirms.

EXAMPLES

Usage examples

Indicates information that can be edited

After renaming, the “Save changes” button turns on; While sending, write "Saving...".

Saving changes Flows

Step by step in flow

Start the task

Feedback and results

How to review

Indicates information that can be edited

Usage examples

Indicates information that can be edited

Find a checklist

No checklists found