[UXPROD-4506] UI changes to "save" button Created: 13/Oct/23  Updated: 06/Nov/23

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: Umbrella Priority: TBD
Reporter: Martina.Schildt Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: UI, crossapp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File image-2023-10-13-14-16-19-830.png    
Development Team: None
PO Rank: 0
RCA Group: TBD

 Description   

Current situation or problem:

Records have 2 buttons: CANCEL and SAVE & CLOSE. The Community expressed the need to have an additional button that would allow just to save the record, without closing it, because a user might want to save changes but still needs to continue editing.

Approach

  • All records should have an additional button, just to save a record.
  • Gill Osguthorpe has mocked up possible options. The Community agreed on option A.1 via a survey, this has additionally been discussed in App Interaction SIG:

Option A.1 is the preferred option, that means, when a new record is being created and when an existing record is being edited, the form should have two save buttons:

  1. "Save" - a secondary button to enable users to quickly save work in progress without closing the form.
  2. "Save & close" - this it the primary save button, currently used by all apps.

When an app offers additional save actions, for example to create another record on save, or to duplicate the record on save, the "Save & close" button should become a split button, with two parts:

  1. On the left is the primary action button "Save & close".
  2. On the right is a second button to open a menu which displays all the possible save actions for the record.

Requirements for the save button

  • The "Save" button should just save the data, (not close and re-open or refresh the page)
  • In edit mode the time of the last save should be shown; ideally close to the save button
  • A keyboard shortcut should be added for "save"
  • Fixed buttons should be used
  • A confirmation via a green toast / banner should be added in edit mode to confirm that the data is saved

Notes

  • The split button would be a new component.
  • There are questions around how saving work in progress should work. For example, what happens if the user tries to save without mandatory data being in place, and what happens if the user selects "Cancel" - does this cancel all the WIP saves which were made?

Generated at Fri Feb 09 00:40:26 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.