Version 4.2.0a

Added ability to accept a repeated notice from the OnTime interface
Added ability to decline an already accepted single instance meeting or an instance of a repeated meeting
When initially accepting an invitation you can now set category, alarm, Mark available and Mark private in the same process
Added partial loading of groups for customers using the servlet. This means that for organisations with a substantial number of groups, the speed of working with public groups has increased.
Added ability to start the API logging from a global setting for the user.

Added ability to accept a repeated notice from the OnTime interface
Added ability to decline an already accepted single instance meeting or an instance of a repeated meeting
When initially accepting an invitation you can now set category, alarm, Mark available and Mark private in the same process
Added setting to control timespan for free time search. Default is now 3 months

When using enterprise scaling the client no longer loads the entire groups list but only favourites

The servlet no longer caches private groups. This makes working with the servlet more efficient as it does not need to reload / update as often as before.
Added a setting in the "Calendar Access Override Section" of the global settings. If you select show legends, entries will now use legend colours even if the user only has the role of View Schedule Information
Added "Info" level to logging. This will show only the absolute most essential information about the operation of the OnTime server.

For quite a few years the OnTime Groups Calendar task responsible for synchronizing updates between the users mail file and the OnTime GC Config database has been able to monitor multiple servers. For each server however the task has been limited to one thread. In 4.2.0 the server task that is installed as standard is still limited to one single thread. In the package you will however also find another task that is multithreaded for each server monitored (WindowsXX_Multi). We expect this to reduce the time from a user makes an entry in the personal calendar till this is fully visible in the group calendar. The standard number of threads for this task is 3 but can be configured from the Server Settings documents. Our plan is to make this new task the standard task in the very near future. If you like you can simply replace the existing task with the new task. We have not seen issues with this new task over the last couple of months. Should an issue however occur you can simply replace the new task with the task that was installed as standard. If you have a large number of users we would suggest that you do test this new task.

Fixed a number of minor stability issues
Fixed an issue where the users default setting for meeting duration was not respected when creating a new meeting
Fixed an issue which occurred when the user opened a room reservation. Particularly a problem in Internet Explorer 8.
Fixed an issue in the light design where the drop down menu in the top bar would not close after a selection had been made

Fixed an issue where tapping the refresh button in a one day view would change to a 3 day view