[FOLIO-3200] #2 [Backend development] Implement: prevent conflict once detected. Enable "failOnConflict" Created: 13/Jun/21  Updated: 29/Dec/23  Resolved: 29/Dec/23

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Story Priority: P3
Reporter: Khalilah Gambrell Assignee: Unassigned
Resolution: Done Votes: 0
Labels: optimistic_locking
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
is cloned by FOLIO-3201 #3 [Frontend development] Implement: ... Closed
Sprint:
Development Team: None

 Description   

Requirement

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 Karate API 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

Potential scenarios for Two automated processes acting on the same record

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

Generated at Thu Feb 08 23:26:21 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.