[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: |
|
| 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
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:
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:
Requirements for the save button
Notes
|