A change request is being used as the starting point for a second, nearly identical change. The administrator adjusts a few fields and needs a separate record created, with the form then showing that newly created record so the remaining fields can be completed. Which save action does this?
- AInsert, which creates a new record from the current values and then returns the user to the previous list.
- BInsert and Stay, which creates a new record from the current values and keeps that new record on the form. Correct
- CSave, which commits the current values to the record already open and keeps that record on the form.
- DUpdate, which commits the current values to the record already open and returns the user to the list.
Why A is wrong: It creates the required second record, which makes it a close call, but the form leaves that record immediately, so the administrator has to find and reopen it to continue.
Why B is correct: Insert and Stay writes the on-screen values into a brand new record and then displays that new record, so the remaining fields can be completed without navigating back to it.
Why C is wrong: Save keeps a form on screen, but it overwrites the original change request with the adjusted values instead of producing a second record, losing the record that was meant to stay intact.
Why D is wrong: Update is the routine action for saving edits, so it is easy to reach for, yet it also writes back to the original record and creates nothing new.