Attempting to create a transaction with incorrect item barcode returns server error
Description
Overview:
When attempting to create a DCB transaction with
Steps to Reproduce:
Make a request to the DCB transaction API to create a transaction with an item barcode that does not match record referred to by the ID
Example from the integration environment:
POST https://edge-ecs-testing-special-integration.int.aws.folio.org/dcbService/transactions/910a4eaf-63a2-4c98-8186-50e9adfbcf29{"item":{"id":"555eeea5-77a7-4dae-8f45-7e35e0833f3b","barcode":"67837673"},"patron":{"id":"bfc225b4-48ac-4576-be09-6137c2802a6c","barcode":"483693762","group":"undergrad"},"pickup":{"servicePointId":"9d1b77e8-f02e-4b7f-b296-3f2042ddac54","servicePointName":"DCB","libraryCode":""},"role":"LENDER"}
Expected Results:
Validation error citing that the barcode does not match the intended item
Actual Results: Received response:
500 Internal Server Error
HTTP 500 Internal Server Error.
If the issue persists, please report it to EBSCO Connect.
(Likely generated by the proxy utilised in EBSCO environments to mask the underlying error)
Overview:
When attempting to create a DCB transaction with
Steps to Reproduce:
Make a request to the DCB transaction API to create a transaction with an item barcode that does not match record referred to by the ID
Example from the integration environment:
POST https://edge-ecs-testing-special-integration.int.aws.folio.org/dcbService/transactions/910a4eaf-63a2-4c98-8186-50e9adfbcf29 { "item":{ "id":"555eeea5-77a7-4dae-8f45-7e35e0833f3b", "barcode":"67837673" }, "patron":{ "id":"bfc225b4-48ac-4576-be09-6137c2802a6c", "barcode":"483693762", "group":"undergrad" }, "pickup":{ "servicePointId":"9d1b77e8-f02e-4b7f-b296-3f2042ddac54", "servicePointName":"DCB", "libraryCode":"" }, "role":"LENDER" }
Expected Results:
Validation error citing that the barcode does not match the intended item
Actual Results:
Received response:
500 Internal Server Error HTTP 500 Internal Server Error. If the issue persists, please report it to EBSCO Connect.
(Likely generated by the proxy utilised in EBSCO environments to mask the underlying error)
Interested parties: @Gurleen Kaur1 @Tim Auger @Kalibek Turgumbayev @Radhakrishnan Gopalakrishnan @Steve Ellis