Done
Details
Assignee
Cate BoeremaCate Boerema(Deactivated)Reporter
Lisa SjögrenLisa SjögrenPriority
TBDTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Cate Boerema
Cate Boerema(Deactivated)Reporter
Lisa Sjögren
Lisa SjögrenPriority
TBDTestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created May 14, 2020 at 12:19 PM
Updated October 12, 2020 at 3:02 PM
Resolved October 12, 2020 at 3:02 PM
Steps to reproduce
Log in as a user who has the relevant permissions for using the Requests app, but no service point assigned
Click on the Requests app
Expected result
One of two things could happen:
a) the Requests app opens without problems
b) a helpful error message lets the user know that they cannot (fully) use the Requests app without first assigning themselves a service point
Actual result
The user gets a series of unhelpful error popups informing that "operation GET on resource 'expiredHolds' failed, saying: No suitable module found for path /circulation/requests-reports/hold-shelf-clearance/ for tenant". After clicking Ok on all these modals, the Request app successfully opens.
The errors are caused by this request that is made when you open the Requests app:
/circulation/requests-reports/hold-shelf-clearance/when the only request format accepted by requests-reports is
/circulation/requests-reports/hold-shelf-clearance/{servicePointId}Analysis
There are two issues here:
Since you get these errors but can still open the app, it's very ambiguous whether having an assigned service point should be a prerequisite for opening/using the Requests app.
To the typical FOLIO circulation user, these error messages are extremely unhelpful. If having an assigned service point is mandatory for using the Requests app, trying to open the Requests app without an assigned service point should result in a helpful error message like the one the same user would get trying to open the Check in app.