Share via

3.1.4.7.4.1 Skipping Automatic Updating of the Meeting Object

  • Article

When a delegator receives a Meeting Update object, the client follows the sequencing rules described in section 3.1.5.6 before deciding to automatically update the Meeting object.

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

  • The Meeting Update object is located in the Sent Items folder, as specified in [MS-OXOSFLD] section 2.2, 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 Update object is set to TRUE.

  • The Meeting Update object is intended for the delegator and a tombstone exists, as specified in section 2.2.12.5, indicating that another user has already declined the meeting.

The client MAY<58> skip automatic updating of the Meeting object if the value of the PidLidServerProcessed property (section 2.2.5.4) on the Meeting Update object is set to TRUE, and the PidLidServerProcessingActions property (section 2.2.5.5) either does not exist or has the cpsUpdatedCalItem bit of this property is set. If the client skips automatic updating of the Meeting object, it MUST NOT set the PidTagProcessed property on the Meeting Update object.