The Booking Interval Rule lets the administrator specify that the time between some (or all) bookings must be at least a particular time. This can be used to enforce gaps between all bookings, or to prevent projects that overheat a resource from following each other too closely. The rule can also ensure that Users do not leave small gaps in the schedule.
Property |
Description |
Reject or warn when exceeded |
Decide whether to reject the booking or just post a warning. |
Retry approved bookings |
An indication to be sent to the user of whether to retry sending the booking as a Request (only applicable when the booking received is Approved). |
Interval Type |
Choose whether to 1) Require Large Separation 2) Eliminate Small Gaps |
Required Interval |
Time between bookings for separation, or the minimum gap if eliminating small gaps. |
Message to show |
The message to be displayed to the user if the booking is rejected or a warning is issued. |
Preceding Bookings |
The Preceding Bookings and Following Bookings work in exactly the same way as Applies To, read the chapter on Choosing Which Bookings A Rule Applies To for more information on how the sub tabs work. The only difference is, it is setting up bookings to proceed the booking and bookings to follow the booking rather than those it applies to and those it doesn't. |
Following Bookings |
The algorithm used for the prevention of small gaps is that any booking that results in a gap smaller than the one declared will be rejected unless the gap before or after it is zero. That is, if the minimum gap is 45 minutes, then it is considered legal to put a 60 minute booking into a 90 minute slot so long as it starts when the previous booking ends, or it ends when the following booking starts.