Among a long list of calendaring improvements, 6.4 introduces calendar widgets for dashboards. These widgets offer a quick summary of a calendar without taking up much screen space.
There’s a count of events occurring for each day, and the full list is displayed when hovering. You can also click each event to open its peek popup and modify it; and those changes will be immediately reflected on the calendar. This allows you to get more work done from your dashboard — rescheduling tasks, chasing overdue invoices, etc.
You’ll also notice the small gear button at the top of the widget. If you have edit permission on the calendar, you can modify it directly from your dashboard as well.
6.4 introduces ‘countdown widgets’ for dashboards. You can use these widgets as gentle reminders of upcoming events.
For example, on a development dashboard you can display a countdown to the next milestone (an iteration or release). On a sales dashboard, you can display the time left in the current period (quarter, year).
6.4 introduces a new ‘World Clock’ widget for dashboards. The clocks support 12-hour or 24-hour display, and the closest timezone can be quickly selected from the list of major cities organized by continent and country.
These widgets are particularly useful for coordinating with international team members or sales prospects.
The 6.4 release includes ‘availability calendars’, which take the events from an existing calendar and convert them into availability windows. This is what a Virtual Attendant sees when it’s scheduling a task or looking for an available worker.
Each worker can elect one of their calendars to determine their availability, which then becomes visible on their profile. This approach is particularly helpful in situations where a worker’s schedule may change frequently between various shifts. A calendar for each shift can be created, and when the schedule changes it’s a single click to activate a new calendar.
To temporarily remove their availability entirely (e.g. vacation, leave of absence, paternity, sabbatical, code marathon), a worker can simply break the link between their availability and an existing calendar. They don’t need to modify or delete any of the existing events, which makes it much easier to resume working later on.
SLA scheduling is a common workflow that’s automated using Cerb’s Virtual Attendants. They are very flexible and capable of automating complex behaviors, but one of the major shortcomings up to this point has been the inability to schedule a due date like “+4 business hours” in the future. All relative dates were based on a 24-hour clock, so 4 hours in the future might be during the night, weekend, or a holiday. You could use the placeholder functionality to create a complex script that would skip past nights and weekends, but it wouldn’t be aware of holidays or any other exceptions.
In 6.4, you can create group-owned calendars that define different sets of working hours and holidays. For example, one calendar for paid support may expand availability to nights and weekends. Virtual Attendants can then use any of these calendars to easily schedule a due date in working hours.
In the example calendar above, December 25th is a non-working day. If a ticket came in at 5pm on the 24th and was due in “8 business hours”, one hour would be consumed through the end of business at 6pm on the 24th. The 25th would be skipped as an all-day holiday, and the remaining 7 hours would be scheduled from the opening of business at 8am on the 26th. As a result, the ticket would be due on the 26th at 3pm; 8 working hours later, but 46 hours of wall time later.
These improvements aren’t limited to SLA scheduling, but that’s one area where they’ll drastically improve how things are being done now.