Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
ACQ Sprint 141
-
2
-
Thunderjet
-
Morning Glory (R2 2022)
-
TBD
Description
Purpose:
UI for optimistic locking.
User story statement(s):
As a user,
I want to have a clear message when a 409 error occurs when saving the record
so that I can load the latest version.
Requirements:
- Apply to the following edit record screens: fiscal year, ledger, group, fund, budget. Is it possible to do something similar for fund type and expense class in settings ?
- If user hits Save and a conflict is detected then display Conflict detection banner.
- Clicking View latest version link displays AS IF the user hit Save & close and it was successful AND display update record in a new window/tab
- If possible have focus go to pane header
- If user hits Cancel or X on the Edit form then show Are you sure modal?
- When user hits Save & close, make sure focus returns or remains on the conflict detection banner.
Scenarios:
Given the user A is editing a record
AND user B has just edited and saved the same record
Thus user A is not editing the latest version
When user A hits Save on that record
Then display the conflict detection banner right below the paneheader
Given the user A is editing a record
AND user B has just edited and saved the same record
Thus user A is not editing the latest version
When user A hits Cancel or x on that record
Then display the standard "Are you sure?" modal used to alert the user to unsaved changes before they navigate away from the edit screen
(And if User A keeps editing and then presses Save, then display the conflict detection banner)
Given conflict detection banner displays on a record
When user A clicks on View latest version
Then display in a new tab in View mode (not Edit mode), with the most recent edits that have been saved
Given conflict detection banner displays on record
When user A hits Cancel or X
Then discard User A's edits and return to a View version of the record
Given conflict detection banner displays on the record
When user A hits Save again
Then shift focus to the conflict detection modal
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-3163 Part 2 - Finance - Implementing Optimistic Locking
-
- Open
-
-
UXPROD-3663 Part 1 - Finance - Implementing Optimistic Locking
-
- Closed
-
-
UXPROD-3666 Improve support for parallel processing
-
- In Refinement
-
- has to be done after
-
MODFISTO-303 Enable optimistic locking
-
- Closed
-
-
MODFISTO-304 Lock budgets to update totals
-
- Closed
-
- is cloned by
-
STSMACOM-668 ControlledVocab - optimistic locking
-
- Closed
-
-
UISACQCOMP-104 Create common component OptimisticLockingBanner
-
- Closed
-