Ordering functionality that FOLIO needs to stay competitive (UXPROD-3440)

[UXPROD-3161] Orders - Implementing Optimistic Locking Created: 07/Jul/21  Updated: 14/Jun/22

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Ordering functionality that FOLIO needs to stay competitive

Type: New Feature Priority: P3
Reporter: Dennis Bridges Assignee: Dennis Bridges
Resolution: Unresolved Votes: 0
Labels: tech-debt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
is cloned by UXPROD-3163 Part 2 - Finance - Implementing Optim... Open
Defines
defines UXPROD-3058 Optimistic Locking In Progress
Relates
relates to MODORDERS-536 Update mod-orders to support optimist... Open
Epic Link: Ordering functionality that FOLIO needs to stay competitive
Development Team: Thunderjet
PO Rank: 0
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: GBV (MVP Sum 2020): R1
Rank: U of AL (MVP Oct 2020): R2

 Description   

Purpose: Implementing Optimistic Locking in Orders.

Description:
Implementation of Optimistic Locking FOLIO wide was ranked very high by the libraries. The implementation in the orders app will follow examples set by the inventory module.

Usecases: (Use cases collected by the community)

Not frequent: 2 users editing the same record at the same time

  1. User A and User B editing the same record at the same time – orders and orders lines

More frequent: 1 user and system trying to act on the same record, either individual records or batch

Two automated processes acting on the same record

Technical documentation:
GitHub: https://github.com/folio-org/raml-module-builder/blob/master/README.md#optimistic-locking

 NOTE 1: without additional changes, this could break data import. When an import needs to update a record, it should use that record's _version value.

NOTE 2: When a 409 is returned, it could be because the record edited by the user had a conflict, or because the change triggered other changes that ended up conflicting, possibly in another module (for instance when opening an order). So UI should not always treat these issues in the same way.


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