Improving the MDaemon automatic appointment functionalities
This would be very useful whenever you want to manage resources such as meeting rooms.
We have configured 4 particular MDaemon accounts, each of them is a meeting room.
Their accounts options are set to "automatically accept new meeting requests".
The rooms calendars are shared, so that each user can check the room availabilities before booking.
Our users Outlook configuration is: local pst files + pop3 session for emails, outlook connector only for shared contacts and calendars.
This way, whenever a "human user" invites a room, the appointment is always accepted by the meeting room.
The bad thing about that is that conflictual appointements may occur, for various reasons such as :
- the sender did not correctly check the room calendar before booking
- he CORRECTLY checked the calendar but the mail server - local cache OC synchronization took some time, the user did not wait long enough
Therefore :
A REALLY EFFICIENT improvement would be to add an option to allow the room account to refuse
the appointment if the room is already partially or fully "busy" and send an email refusal advice.
Or at least it could accept it while sending back a warning message to the sender. Being able to edit
that refusal/warning message would be another nice option (my colleagues won't read it if it's not written in french ;) ...)
OTIMA
shared this idea
Hello,
When accounts are configured to automatically accept appointments MDaemon 13.5.0 should now decline them if there is a conflict.
Thanks,
-
OTIMA
commented
Up !
Still had to explain to my colleagues this morning why I can't setup our meeting rooms to refuse conflictual appointments, and why they have to CHECK the OC rooms calendars, and above all WAIT for the syncho to be done, before considering whether the room is busy or not... but I can't blame them, it's a bit annoying, isn't it ?
Please raise this idea priority !
-
OTIMA
commented
Hello Tony, hopefully we won't have to wait another 5 years before it's done... I'm not the one who makes decision around here, but I must admit that I sometimes hear that this missing functionnality could be the main reason, in the next 2 years, to stop using Mdaemon...
-
Tony Burtovoy
commented
I've submitted this before and it's sorely needed. The real issue is that it refuses properly when a conflicting meeting is setup inside Worldclient, but does not refuse properly when setup inside OC. Why on Earth it wasn't done correctly in OC when the feature was added to WC beats the heck out of me!?? I've been requesting this fix on and off for 5 years. Seems to be low priority. Can it be escalated please, ALT-N ?
-
Tony Burtovoy
commented
Thanks. Like I said before.. this was in the forums years ago and suffered the same fate as so many other (seeming) easy suggestions. Anyway, if its back on the radar and can actually get some real attention this time, then Hoo Rah!
-
Tony Burtovoy
commented
OK, so you tested with Worldclient. How about Outlook Connector? Shouldn't the server process the meeting in the same way regardless of where the meeting is setup? What happens in the meeting is setup in Outlook? ..when I setup meetings in Outlook, I do not get the results you are reporting.