Hello, If the organizer (author) of an event cancel the event, it is expected to have the event canceled for everybody else. Has the manager tried to change the event's owner before removing himself from the event?
If you want to use the Calendar API, you could also write an application that would use 2 Legged OAuth<http://code.google.com/apis/gdata/docs/auth/oauth.html#2LeggedOAuth>mechanism to "impersonate" the co-worker and create an event on his calendar; using this, the event will be created on the co-worker's calendar and set him as the owner of the event. Best, Alain On Tue, Jun 28, 2011 at 7:23 AM, teledon <[email protected]> wrote: > I need a manager to be able to schedule a specific task (appointment) > in one or more of their worker's calendars, using the invite function > on the manager's calendar. This could be a request for the worker to > do a specific task, or a request from the manager for a group of > workers to meet together at some time specified by the manager. The > key here, is that the manager does not want his calendar to be > included in the task or meeting event that he is setting. > > I want to use the invite function, because it immediately puts the > tentative appointment on the invited workers calendars, notifies the > worker(s) of the manager's scheduling request by email (SMS would also > be nice), and also gives the worker(s) the option to accept, decline, > or reschedule the event. > > Unfortunately, the current invite function always includes the manager > or appointment originator in the event. This always puts the requested > event on the request originator's calendar as well as all of the > invitees. Surprisingly, the originator can remove themselves from the > invitee list in their own calendar, but this action immediately > removes the task or appointment from ALL of the invitees calendars, > even though other invitees are still shown on the invitee list. > > Personally, I think this behavior is a mistake. If the meeting > originator wants to take themselves off of the meeting list but leave > others on it, they should be able to do that without killing the > appointment for everyone. Once the manager has told one or more > workers what to do and when to do it, the manager doesn't need to have > a calendar event on his calendar that doesn't involve himself. > > If the worker(s) agree to the task or meeting, they can accept the > invite as normal, and the manager will get a notification of the > acceptance via email.. If the worker disagrees with the managers > request, they can use the invite email process to reject the task, and > the manager can negotiate this by inviting another event on the > affected worker's calendars. It is assumed that the manager can see > the worker's calendars, so he can pick another time when the required > worker(s) are available. > > In any case, I want to understand how to use the calendar APIs to kill > the action that removes all the invitees, if the originator takes > themselves off the invite list. If the originator does take himself > off the list, all the other invitees should still see a tentative > event on their calendar, which they can elect to accept or reject, as > in any invitation scenario.. > > -- > You received this message because you are subscribed to the Google > Groups "Google Calendar Data API" group. > To post to this group, send email to > [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://code.google.com/apis/calendar/community/forum.html > -- Alain Vongsouvanh -- You received this message because you are subscribed to the Google Groups "Google Calendar Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://code.google.com/apis/calendar/community/forum.html
