Related Topics • HOWTO: Bypassing Borrowing and Doc Del EMail Notifications • PROBLEM: Double-clicking Does Not Notify Customers by Phone • Email Copies does not work for all email functions • PROBLEM: Email not sent! Error: 503 Need RCPT (Recipient) (0) • HOWTO: Setting up ILLiad to print Borrowing Cancellation Notifications

Other Support Options • Contact Atlas Systems Phone Numbers, Support Options, Online Help, and more. • Listserv Pose a question to other users.

Page Tools Print this page E-mail this page

Feedback How helpful was this article? 5 Best 4 3 2 1Worst 0 N/A Suggestions:

SUMMARY

To setup overdues in ILLiad, there are several keys that apply. All of the overdue days only apply to which template is used when sending overdues. Overdues are only sent when a staff member goes to the client and clicks the button to send the emails (for Borrowing) or print the files (for Lending). The following keys need to be set for Borrowing:

OverdueGraceDays: This key should be set to the number of days after the due date before overdues should start being sent. For example, to have the first overdue notice apply after the book is 2 days overdue, the OverdueGraceDays should be set to 2.

NOTE: If the OverdueGraceDays value is set to a negative number, the OverDue1 E-mail notices will begin going out the specified number of days before the Due Date as a reminder notice. The OverdueNoticeOneDays value should then be set to 0, however, to make sure that reminders are only sent before the item is due and overdue notices are sent after. As an example, if the Due Date of an item is 12/1/YYYY, the OverdueGraceDays value is set to -5, and the OverdueNoticeOneDays value is set to 0, the OverDue1 notice would begin going out on 11/26 and the Overdue level 2 notices would begin on 12/1. In such cases, the text of the E-mail template used by the OverDue1 notice should be rephrased to be a reminder rather and an Overdue notification.

OverdueNoticeOneDays: This key is the number of days after the due date when the second overdue should be active. For example, if the second overdue should be sent after 9 days, then the OverdueNoticeOneDays would be set to 9.

OverdueNoticeTwoDays: This key is the number of days after the due date when the third overdue should be active. For example, if the third overdue should be sent after 16 days, then the OverdueNoticeOneDays would be set to 16.

BlockOnThirdOverdue: This is a Yes/No key to give the option of not blocking borrowing customers when their items are in the third category of overdues. By default, this key is set to Yes.

For the previous examples, overdues would be in three categories. Items that were 2-9 days overdue would be in the first overdue category. Items that were 9-16 days overdue would be in the second overdue category. And items that were over16 days overdue would be in the third overdue category. Overdues would still only be sent whenever the overdue button is clicked.