Uploaded image for project: 'FOLIO'
  1. FOLIO
  2. FOLIO-2027

Data Problems from Front-End Record Caching

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • P3
    • Resolution: Unresolved
    • None
    • None
    • Core: Platform

    Description

      Background: This was reported by bjoern_ubl and annikadomin

      Steps to repro:

      1. Working with two browser sessions simulating the simultaneous work of several colleagues in one system
      2. User A opens a holding view page, User B opens the same holding view page
      3. User A edits this holding (e.g. location)
      4. User A updates the record
      5. User B clicks shortly afterwards on edit

      Actual behavior: User B does not get the latest version of the record, because the form is filled with information from the state of his/her view page.

      Expected behavior: The edit form should load the latest data from the database not from the view cache. Even though it may be unlikely that two colleagues are working on a record at the same time, this behavior leads to an incomprehensible inconsistency of the data. This is unacceptable for productive use.

      Additional info: This behavior was already reported at a UAT for Vendors App months ago and should be discussed urgently in the community! This issue should not be underestimated.

      TestRail: Results

        Attachments

          Issue Links

            relates to

            Task - A task that needs to be done. FOLIO-2028 SPIKE: how to handle update conflicts?

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-1752 Prevent update conflicts (via optimistic locking): platform support for detection

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-2796 Prevent update conflicts when doing manual edits (User A and User B)

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-2797 Prevent update conflicts (1 user and system trying to act on the same record)

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-2798 Prevent update conflicts (two automated processes acting on the same record)

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests MODINVSTOR-656 enable "detection-only" OL for instances, holdings and titles

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Activity

              People

                jakub Jakub Skoczen
                cboerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases