Handle error when trying to delete an access status type that no longer exists

Description

  1. Open Settings > Access Status Types in two browser tabs

  2. Delete one Access Type in one browser tab, don't refresh the second

  3. In second browser try to delete the same Access Type

Actual behavior: Confirmation Modal is opened, no error message is shown

Expected behavior: Confirmation Modal is closed, error message "This access status type has already been deleted." is shown.

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

relates to

Checklist

hide

TestRail: Results

Activity

Show:

Denys Bohdan March 26, 2020 at 6:26 PM

sure, we'll add this message to translations and show it

Khalilah Gambrell March 26, 2020 at 3:24 PM

. your assumption for first point is correct. Regarding second point, is it possible to display this message "This access status type has already been deleted."?

Denys Bohdan March 26, 2020 at 2:35 PM

there are two types of errors that should be handled in UI:

  1. when an access type is already in use. I assume that we should hide 'delete' button in this case judging by the screenshot in https://folio-org.atlassian.net/browse/UIEH-828, but when it was implemented this part of backend hadn't been done yet

  2. when two people are trying to delete one access type at the same time. when first person deletes in the second one will receive an error saying that this access type doesn't exist.

My question is - is my assumption in the first point correct? In this case I'll create a user story for handling of the first type of error and the second type of error will be covered by this ticket.

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Spitfire

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created March 20, 2020 at 5:06 PM
Updated May 15, 2020 at 11:14 AM
Resolved May 15, 2020 at 11:14 AM
TestRail: Cases
TestRail: Runs