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

#3 [Frontend development] Implement: prevent conflict once detected. Enable "failOnConflict"

    XMLWordPrintable

    Details

    • Template:
    • Development Team:
      None

      Description

      Requirement

      • #3 [Frontend development] Implement: prevent conflict once detected. Enable "failOnConflict"
      • Teams follows documentation available: https://github.com/folio-org/raml-module-builder#optimistic-locking
      • Dependency version updates required?
      • Implement the following UX messaging:
        • Conflict detection indication (success)
        • Conflict detection indication (error)

      Acceptance criteria

      Given I click Save on a record
      When an indicator displays that another person is editing the same record
      Then ???

      Given I take an action on a record
      When an indicator displays that another person is editing the same record
      Then ???

      Given I take an action on a record
      When an indicator displays that a system is editing the same record
      Then ???

      Given a system is updating a record
      When another system is updating the same record
      Then ???

      Given an automated process is updating a record
      When another automated system is updating the same record
      Then

      Given I take an action on a record OR edit a record
      When an Optimistic locking error occurs
      Then ???

      Definition of done

      • Implement E2E tests
      • Verify that key use cases are addressed
      • [NOTE: POs should review below scenarios and edit based on workflows.]

      Potential multiple users are editing the same record at the same time scenarios for testing

      User A Action User B Action User C Action One of these Users hits Save outcome
      Edits a field on record Deletes a field on same record Edits a field on same record TBD
      Edits a field on record Take a non-delete action on same record N/A TBD
      Edits a field on record Moves a record Edits a field on record 1 TBD
      Edits a field on record Deletes a same record N/A TBD
      Edits a field on record Takes an action on same record N/A TBD
      Edits a field on record Takes an action on a dependent field on same record N/A TBD
      Takes an action on record Takes an action on same record N/A TBD

      Potential scenarios for 1 user and system trying to act on the same record, either individual records or batch

      User A Action System B Action System C Action First User/System to Save Outcome
      Edits a field on record Edits same record Edits same record TBD
      Edits a field on record Takes an action on same record N/A TBD
      Takes an action on record Edits same record N/A TBD

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Unassigned Unassigned
                Reporter:
                kgambrell Khalilah Gambrell
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases