Invoicing functionality that FOLIO needs to stay competitive
(UXPROD-3439)
|
|
| Status: | Open |
| Project: | mod-invoice |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Invoicing functionality that FOLIO needs to stay competitive |
| Type: | Story | Priority: | P3 |
| Reporter: | Damien | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | acq-dev-grooming | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||
| Sprint: | |||||||||||||||||
| Development Team: | Thunderjet | ||||||||||||||||
| Epic Link: | Invoicing functionality that FOLIO needs to stay competitive | ||||||||||||||||
| Description |
|
Overview Optimistic Locking is a technical solution provided by RMB and other frameworks to resolve update conflicts. See
All acquisition apps are currently vulnerable to update conflicts. What this means in practice is that if 2 users are updating the same record at the same time, one of them might lose its modifications and will receive no warning. Additionally, all derived modifications are vulnerable too: if an edit triggers another edit in another module, these modifications can be lost too without a warning. Modules using other modules that have optimistic locking enabled need to check for the 409 status code, and react appropriately, for instance by minimizing risks of update conflicts, or trying the update sequence again, or report an explicit error to the user (or all 3). This means all layers require modifications. Spike Objectives
Spike Decisions
|
| Comments |
| Comment by Damien [ 02/Sep/21 ] |
|
See also this recent PO meeting notes: Optimistic Locking - Detecting and Resolving Conflicts Requirements |