Improved Catastrophic Error Messaging

Priority

Environment

None

Template

None

Description

As a librarian
I want a valid reason for why I cannot access the eholdings app

Background

Currently when eholdings app is down, regardless of the reason, the UI displays an error message that the KB is not configured properly.

Requirement

When eholdings app is down then display the most applicable error message.

Acceptance criteria

Given I am on the eholdings app

When the error is not due to API credential configuration OR eholdings app not being installed
AND it is due to an exceeded API limit [Error 429]
Then display an error message - [Unable to complete operation. HoldingsIQ API limit has been exceeded. Please contact your EBSCO Holdings IQ support contact.]

Given I am on the eholdings app
When the error is due to Holdings API being down
Then display an error message - [eholdings app is unavailable at this time. If the problem persist please contact your FOLIO system administrator or visit EBSCO Connect [link to https://connect.ebsco.com].]

Development Team

Spitfire

Release

None

Story Points

Sprint

Checklist

hide

TestRail: Results

Activity

Show:

Denys Bohdan August 18, 2020 at 12:46 PM

Hi , here's a recording of how these errors look. I recorded a local test environment and used mocks to emulate errors from back-end

https://epam-my.sharepoint.com/:v:/p/denys_bohdan/EWU93L8r8ttHrHmmM_BkKgQBDCrHfgIeOQgfiUjwfBnsPA?e=YufFDb

Denys Bohdan August 6, 2020 at 8:05 AM

I'll implement this in scope of this story

Khalilah Gambrell August 5, 2020 at 7:37 PM

- to confirm is this a spike or will you implement with this story?

Sobha Duvvuri May 7, 2020 at 2:50 AM
Edited

In my opinion this should be a backend ticket - Adding this and more use-cases to this backend ticket - https://folio-org.atlassian.net/browse/MODKBEKBJ-442
Once the backend ticket is complete, then this UI ticket should be modified to display the error provided by MODKBEKBJ appropriately in toast messages.

Done

Details

Assignee

Reporter

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created January 10, 2020 at 9:51 AM
Updated September 16, 2020 at 6:30 PM
Resolved August 20, 2020 at 2:52 PM
TestRail: Cases
TestRail: Runs