Comment 83 for bug 1198465

I put the latest branch through some of my test cases. I'm still seeing trouble with getting the "Lost Checkin Generates New Overdues" OU setting to behave properly. When I check in a lost item that should generate new fines, those fines are not being generated.

In addition to testing on master with the negative balance branch loaded, I ran the same test through a 2.7ish system with the same dataset just to verify what pre-existing behavior was.

Here's the use case. Relevant OU settings:

Void overdue fines when item is marked lost - true
Restore overdues on lost item return – true
Generate new overdues on lost item return - true
Prohibit negative balance (default) - unset

I was testing on a transaction that had accrued $1.75 in overdue fines before being marked as lost. $1.70 had accrued before it was marked as lost and another $.05 was added. The item was marked lost on April 13, 2012 before the negative balance branch was loaded. All of those fines were voided using the old method, and a $22 lost fee was added to the record.

I added a cash payment of $10 for the transaction, leaving $12 of the lost fee. I then check the item back in on 4/26/15.

I am left with a balance of -8.20. The system the earlier overdue fines (1.75) and added one more overdue fine with a date of 4/27, totaling $1.80 that was deducted from the $10 that was paid.

Alternatively, when I follow the same set of steps on the same record on the 2.7ish system, I am left with a balance -7.00.
In this case, the $1.75 in previous overdue fines where unvoided, and new fines are generated from April 14, 2012 (the day after it was originally marked lost) through May 9, 2012, at which time we hit the $3 max fine threshold and stop accruing fines.

Let me know if you need any more details!