Blocked Times
Each diarybook user, that is also a service provider, can have a set of Blocked Time records. These records describe times that the user does not want to take appointments but that are normally within that user’s work hours. Blocked time records are useful if the person taking the appointment (the operator) is not the service provider user and is therefore prevented in making an appointment inside of those hours.
A blocked time can also be account-wide affecting all service providers. This can be useful for team meetings or large scale events. Only users with appropriate rights can create account-wide blocked times.
Blocked Time Records
A blocked time record consists of the following fields
| Fields |
|---|
| Reason |
| Start Date and Time |
| End Date and Time |
| User(s) affected |
Example 1
Annual Leave, User 1, 03/09/2012 00:00 - 12/09/2012 00:00
In the the example above if the operator attempts to make an appointment for User 1 between 03rd September and the 8th September inclusive the appointment will be rejected due to a conflict.
Example 2
Holiday Season, All Users, 22/12/2012 00:00 - 02/01/2013 00:00
In this example if the operator attempts to make an appointment for any user between 22nd December and the 1st of January inclusive the appointment will be rejected due to a conflict.
Blocked times do not have buffers at either end
Example 3
Meeting, User 2, 11/10/2012 10:00 - 11/10/2012 11:00
In the above example, creating an appointment for User 2 that ends at 10am will be allowed. Likewise creating an appointment that begins at 11am will be allowed.