Share via

3.1.4.8.1 Accepting a Meeting

  • Article

When the attendee or a delegate of the attendee accepts a Meeting Request object, the client ensures that the Meeting object has been created in the attendee's Calendar special folder, as specified in section 3.1.4.7.2.2. Similarly, when the attendee or delegate of the attendee accepts a Meeting Update object, the client ensures that the Meeting object has been updated in the attendee's Calendar special folder, as specified in section 3.1.4.7.4.2, unless the Meeting Update object is out-of-date, as specified in section 3.1.5.2, in which case the client does not modify the Meeting object or send a Meeting Response object.

After creating or updating the Meeting object, all changes made to the Meeting object in the attendee's Calendar special folder MUST be atomic; for example, by creating a copy of the object, applying the changes to the copy, and then deleting the original Meeting object. The client MUST make the following changes to the Meeting object:

  • Set the value of the PidLidBusyStatus property (section 2.2.1.2) equal to the value of the PidLidIntendedBusyStatus property (section 2.2.6.4) from the Meeting Request object.

  • Set the value of the PidLidResponseStatus property (section 2.2.1.11) to "respAccepted" (0x00000003).

  • Set the value of the PidLidAppointmentReplyTime property (section 2.2.4.3) to the current date and time.

  • If it is the delegate that is responding, set the value of the PidLidAppointmentReplyName property (section 2.2.4.5) equal to the value of the PidTagMailboxOwnerName property ([MS-OXCSTOR] section 2.2.2.1) from the message store. If the delegate is not the one who is responding, the PidLidAppointmentReplyName property is not set.

The client can prompt a user to send a Meeting Response object back to the organizer, as specified in 3.1.4.8.4.

When sending a Meeting Response object to the organizer, the client performs the additional step of setting the ciRespondedAccept bit of the PidLidClientIntent property (section 2.2.2.4) of the Meeting object.