Bug 26072 - Add ability to *not* force holds to be placed via the REST API even if AllowHoldPolicyOverride is enabled
Summary: Add ability to *not* force holds to be placed via the REST API even if AllowH...
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: REST API (show other bugs)
Version: Main
Hardware: All All
: P5 - low minor
Assignee: Kyle M Hall (khall)
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-27 18:16 UTC by Kyle M Hall (khall)
Modified: 2021-06-14 21:28 UTC (History)
0 users

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Attachments
Bug 26072: Add ability to *not* force holds to be placed via the REST API even if AllowHoldPolicyOverride is enabled (3.30 KB, patch)
2020-07-27 18:17 UTC, Kyle M Hall (khall) 		Details | Diff | Splinter Review
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kyle M Hall (khall) 2020-07-27 18:16:23 UTC 
There are use cases where we need to be able to place holds via the API, but not place holds that are in violation of the current holds policy. If AllowHoldPolicyOverride is enabled, holds placed via the API will succeed regardless of violations of the current hold rules.
Comment 1 Kyle M Hall (khall) 2020-07-27 18:17:54 UTC 
Created attachment 107445 [details] [review]
Bug 26072: Add ability to *not* force holds to be placed via the REST API even if AllowHoldPolicyOverride is enabled

There are use cases where we need to be able to place holds via the API, but not place holds that are in violation of the current holds policy. If AllowHoldPolicyOverride is enabled, holds placed via the API will succeed regardless of violations of the current hold rules.

Test Plan:
1) prove t/db_dependent/api/v1/holds.t