Share via

3.1.4.9.2.1 Deciding to Update a Meeting Object

  • Article

When a delegator receives a Meeting Cancellation object, the client MUST follow the sequencing rules described in section 3.1.5.6 before automatically updating the Meeting object.

If any one of the following conditions is met, the client does not automatically update the Meeting object:

  • The Meeting Cancellation object is located in the Sent Items folder or the Outbox folder, as specified in [MS-OXOSFLD] section 2.2.

  • The value of the PidTagProcessed property (section 2.2.5.7) on the Meeting Cancellation object is set to TRUE.

  • The client MAY<82> skip automatic updating of the Meeting object if the value of the PidLidServerProcessed property (section 2.2.5.4) on the Meeting Cancellation object is set to TRUE and the Meeting Cancellation object's PidLidServerProcessingActions property (section 2.2.5.5) either does not exist or the cpsUpdatedCalItem bit of this property is set. If the client does not automatically update the Meeting object, it MUST NOT set the PidTagProcessed property on the Meeting Cancellation object.

If the client determines that the Meeting object is to be updated, it first tries to find the Calendar object, as specified in section 3.1.5.1. If the Meeting Cancellation object represents an exception to a recurring series, and the recurring series was found in the calendar but the exception was previously deleted from the recurring series, the client SHOULD NOT<83> re-create the Exception Attachment object and the Exception Embedded Message object, as specified in section 2.2.10.2, on the recurring Meeting object. If the Meeting object was not found at all, the client SHOULD NOT<84> re-create it.

If the Meeting Cancellation object is out-of-date, as specified in section 3.1.5.2, the client SHOULD change the value of the PidLidMeetingType property (section 2.2.6.5) on the Meeting Cancellation object to mtgOutofDate (0x00080000) but does not update the Meeting object. Similarly, if the Meeting Cancellation object is not newer than the Meeting object, as specified in section 3.1.5.3, the client does not update the Meeting object.