3.1.4.8.3 Declining a Meeting

When the attendee or a delegate of the attendee declines 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 declines 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 MUST NOT modify the Meeting object and MUST NOT send a Meeting Response object.

After creating or updating the Meeting object, the client applies the following changes to the Meeting object in the attendee's Calendar special folder:

  • If the value of the PidLidReminderSet property ([MS-OXORMDR] section 2.2.1.1) is set to TRUE, the Meeting object is not a recurring series, and the signal time has passed, set the value of the PidLidReminderSet property to FALSE.

  • Set the value of the PidLidResponseStatus property (section 2.2.1.11) to "respDeclined" (0x00000004).

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

  • If the delegate 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.

  • If the delegate is acting on behalf of the delegator, the client SHOULD set the value of the PidLidOriginalStoreEntryId property (section 2.2.4.9) to the EntryID of the delegator's message store.

The following additional actions are performed by the client:

  • If the Meeting Request object or Meeting Update object represents either a recurring series or single-instance meeting, the client removes the Meeting object from the attendee's calendar, either by moving the Meeting object to the Deleted Items folder, as specified in [MS-OXOSFLD] section 2.2, or by permanently deleting the object.

  • If the Meeting Request object or Meeting Update object represents an exception to a recurring series, the client removes the Exception Attachment object from the recurring series, as specified in section 3.1.4.6.4.

  • If the delegator or a delegate acting on behalf of the delegator declines a meeting, a tombstone SHOULD be added to the PidTagScheduleInfoAppointmentTombstone property (section 2.2.12.5) on the delegator's Delegate Information object, as specified in section 3.1.5.6.

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

When sending a Meeting Response object to the organizer, the client performs the following additional actions:

  • Set the ciRespondedDecline bit of the PidLidClientIntent property (section 2.2.2.4) of the Meeting object.

  • If the Meeting object represents an exception to a recurring series, then set the ciRespondedExceptionDecline bit of the PidLidClientIntent property of the Meeting object that represents the recurring series for the exception.

When not sending a Meeting Response object, the client performs the following additional actions:

  • Set the ciDeletedWithNoResponse bit of the PidLidClientIntent property of the Meeting object.

  • If the Meeting object represents an exception to a recurring series, then set the ciDeletedExceptionWithNoResponse bit of the PidLidClientIntent property of the Meeting object that represents the recurring series for the exception.

Show: