|
Text to go in the release notes:
|
The patron holds tables on the patron details page, circulation page, and holds management page (reserve/request.pl) now use a REST API endpoint for cancelling holds, with bulk cancellations processed as background jobs.
Previously, hold cancellations from these pages were processed synchronously through traditional page requests. When cancelling multiple holds at once, this could cause delays or timeouts on pages with many holds.
**Key improvements:**
- **Background processing**: Bulk hold cancellations are now queued as background jobs, preventing page timeouts when cancelling multiple holds
- **Consistent interface**: Selecting and cancelling holds works the same way across all patron-related holds tables (patron details, circulation, and holds management pages)
- **Better performance**: The page doesn't need to wait for all cancellations to complete before refreshing
**For staff:** When you cancel selected holds, the page may not refresh immediately. The cancellations are being processed in the background. You can check the status of the background job in Administration → Jobs.
**Technical details:**
This enhancement adds a new `/holds/cancellation_bulk` API endpoint (Bug 40550) that accepts multiple hold IDs and queues their cancellations as a background job, improving the reliability and user experience when managing large numbers of holds.
|