Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-3161

Orders - Implementing Optimistic Locking



    • New Feature
    • Status: Open (View Workflow)
    • P3
    • Resolution: Unresolved
    • None
    • None
    • None
    • Thunderjet
    • 0
    • R1
    • R1
    • R1
    • R2


      Purpose: Implementing Optimistic Locking in Orders.

      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.

      TestRail: Results


          Issue Links



                dennisbridges Dennis Bridges
                dennisbridges Dennis Bridges
                0 Vote for this issue
                6 Start watching this issue



                  TestRail: Runs

                    TestRail: Cases