Export (0) Print
Expand All

3.1.4.9.1.2 Cancelling a Recurring Series

After a Meeting Cancellation object is sent to all attendees for a recurring series that has exceptions, the client sends a Meeting Cancellation object for each exception whose start date and time (according to the PidLidAppointmentStartWhole property (section 2.2.1.5) on the Exception Embedded Message object, as specified in section 2.2.10.2) has not yet passed. The Meeting Cancellation object for each exception conforms to the specifications in section 2.2.8.

If the series has deleted exceptions, the client SHOULD NOT<79> send a Meeting Cancellation object for each deleted exception for which the start date and time (according to the DeletedInstanceDates field of the PidLidAppointmentRecur property (section 2.2.1.44) of the Meeting object) have not yet passed.

After a Meeting Cancellation object is sent to a partial attendee list, as specified in section 3.1.4.9.1.1, the client SHOULD<80> send a meeting cancellation for each exception whose start date and time has not yet passed to every attendee of the exception that is also in the partial attendee list. If sending a meeting cancellation for an exception, the client sets the recipExceptionalDeleted bit of the PidTagRecipientFlags property (section 2.2.4.10.1) for each removed attendee.

Show:
© 2014 Microsoft