Details
-
Bug
-
Status: Closed (View Workflow)
-
P1
-
Resolution: Cannot Reproduce
-
None
-
None
-
EPAM-Veg Sprint 135
-
2
-
Vega
-
Lotus (R1 2022) Bug Fix
-
Legitimate regression
Description
Overview:
When attempting to place an item hold via mod-patron item hold API, user is unable to create a recall request when the circulation rules and policies are configured to effect that result (only recalls allowed, not holds, in request policy). Works fine with the instance hold API.
Steps to Reproduce:
- Log into folio-snapshot(-2) and configure a request policy that only permits recalls
- Create a circulation rule that uses that policy
- Check an item out to which that rule will apply
- Using Postman or another API client, attempt to place an item hold via mod-patron API (eg. /patron/account/b4cee18d-f862-4ef1-95a5-879fdd619603/item/459afaba-5b39-468d-9072-eb1685e0ddf4/hold)
Expected Results:
An item-level Recall is placed on the indicated item.
Actual Results:
Receive the following error:
{ "errors": [ { "message": "Hold requests are not allowed for this patron and item combination", "parameters": [ { "key": "requestType", "value": "Hold" } ] } ] }
Additional Information:
URL:
Interested parties:
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-3409 Vega - Lotus Enhancements/Bugfixes/Tech Debt
-
- Closed
-
- relates to
-
CIRC-1456 Unable to Place Recalls via Instance Hold Endpoint (/circulation/requests/instances) When Item is Checked out with a Fixed Due Date Schedule
-
- Closed
-