Details
Assignee
Roman BarannykRoman BarannykReporter
Alexander KurashAlexander KurashPriority
P1Story Points
1Sprint
Development Team
VegaTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Roman Barannyk
Roman BarannykReporter
Alexander Kurash
Alexander KurashPriority
Story Points
1
Sprint
Development Team
Vega
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created March 21, 2025 at 1:21 PM
Updated 2 days ago
Overview: After following workflow steps to create a secure mediated cross-tenant request, when trying to check out the item to the secure patron, an "access denied" error occurs
Steps to Reproduce:
Log into some FOLIO ECS Eureka bugfest as ecs_admin
In the Secure tenant, place and confirm a Mediated request
Switch tenant affiliation to Lending tenant and select a service point other than the Interim service point
Check Item in via Lending tenant using Check in app.
Item sent In transit to “Interim service point”
Change your affiliation back to Secure
Navigate to the Mediated requests app and ensure Service point is set to Interim.
Using the Mediated requests activities dropdown on the left, select Confirm item arrival.
Scan or manually enter item barcode information into box and click Enter.
Review the details of the loan that should be displayed in a list below the item barcode entry field.
Ensure the Mediated request status has updated to “Open - Item arrived”
Navigate to the Mediated requests app
Using the Mediated requests activities dropdown on the left, select “Send item in transit”.
Scan or manually enter Item barcode click Enter
Ensure the Mediated request status has updated to “Open - In transit to be checked out”.
In the Secure tenant, use the Check in app. to check the Item in at the designated Pickup service point
Use the Check out app. to check the Item out to the patron upon either pickup or delivery
Expected Results: The item is checked out
Actual Results: Item not checked out: Access Denied error recieved
Additional Information:
I did not have time to troubleshoot this at all. I was trying to make a recording of a successful secure circulation workflow when this came up. I've attached the recording and screenshot error.
Interested parties: