I tested this and it looks good to me. Here's my signoff branch:
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/mmorgan/lp1178802-signoff
I tested the following scenarios:
-Set a ceiling date in the past and the rolling due date applied at checkout
-Set a ceiling date in the future and the hard due date applied
-Set a ceiling date of today and the hard due date applied
All above scenarios were tested with Always apply set to TRUE as well as Always apply set to FALSE
Also tested Hard Due Date Values as follows:
Set a Hard Due Date Value with a ceiling date of today and an active date of today
Ran the hard due date updater and the ceiling date was updated to today
At checkout the hard due date applied, making the due date today.
I tested this and it looks good to me. Here's my signoff branch:
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ mmorgan/ lp1178802- signoff
I tested the following scenarios:
-Set a ceiling date in the past and the rolling due date applied at checkout
-Set a ceiling date in the future and the hard due date applied
-Set a ceiling date of today and the hard due date applied
All above scenarios were tested with Always apply set to TRUE as well as Always apply set to FALSE
Also tested Hard Due Date Values as follows:
Set a Hard Due Date Value with a ceiling date of today and an active date of today
Ran the hard due date updater and the ceiling date was updated to today
At checkout the hard due date applied, making the due date today.