In the system preferences it is possible to nominate a $ value limit using a couple of confurable settings: maxoutstanding ang noissuescgarge A further system preference (IssuingInProcess) can be set to prevent / not prevent issues in a single session from being blocked if that threshold is reached. For example: Koha Patrons have $5 limit on their account. Patrons often borrow more than that in one transaction/session. So a transaction/session may be carried out to completion even if the amount owed goes over $5. They will however be blocked from any new borrowing until that debt is reduced below $5. If the IssuingInProcess is set to <Prevent> it, illogically, doesn't prevent - and vice versa. It is working backwards.
Yep at some point the description was changed It is still right in the database | IssuingInProcess | 1 | NULL | If ON, disables fines if the patron is issuing item that accumulate debt | YesNo | Yes = On ... but now Prevent = On So if switch prevent on, it does the checks about being in process and lets the issue proceed if it is in process. So it is backwards. Easiest fix is to fix the circulation.pref file, so the description matches reality. Patch forthcoming
Created attachment 9547 [details] [review] Bug 8082: Fixing circulation.pref to match reality for IssuingInProcess
.pref file text now matches reality if ( C4::Context->preference("IssuingInProcess") ) {
Created attachment 9866 [details] [review] Bug 8082: Fixing circulation.pref to match reality for IssuingInProcess Signed-off-by: Liz Rea <wizzyrea@gmail.com> passes tests, changes are as advertised.
Reverses language on the syspref file. Marking Passed QA.
Pushed to 3.8.x, will be in 3.8.2