Share via

3.1.4.7.1 Sending a Meeting Request

  • Article

To inform attendees of an event, the organizer or delegate of the organizer sends a meeting request. To send the meeting request, the client creates a new Meeting Request object by using the RopCreateMessage ROP ([MS-OXCROPS] section 2.2.6.2), sets the Meeting Request object properties as follows, and then sends the Meeting Request object by using the RopSubmitMessage ROP ([MS-OXCROPS] section 2.2.7.1).

The client copies all properties specified in section 2.2.1 from the Meeting object to the Meeting Request object, adds all required properties as specified in section 2.2.6, and then sets the following on the Meeting Request object:

  • The value of the PidLidAppointmentSequence property (section 2.2.1.1) to zero.

  • The asfReceived and asfMeeting bits on the PidLidAppointmentStateFlags property (section 2.2.1.10).

  • The value of the PidLidResponseStatus property (section 2.2.1.11) to "respNotResponded" (0x00000005).

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

  • The value of the PidLidBusyStatus property to "olTentative" (0x00000001).

  • The value of the PidLidFExceptionalAttendees property (section 2.2.2.3) to FALSE.

  • The value of the PidLidFExceptionalBody property (section 2.2.10.2.6) to FALSE.

  • The value of the PidLidIsRecurring property (section 2.2.1.13).

  • The value of the PidLidRecurring property (section 2.2.1.12).

  • The value of the PidLidCalendarType property (section 2.2.6.11), if the Meeting Request object represents a recurring series.

  • The value of the PidLidWhere property (section 2.2.5.3) equal to the value of the PidLidLocation property (section 2.2.1.4) from the Meeting object.

  • The value of the PidLidAttendeeCriticalChange property (section 2.2.5.2) to the current date and time in UTC.

  • The value of the PidLidMeetingType property (section 2.2.6.5) to "mtgRequest" (0x00000001).

  • The value of the PidLidAllAttendeesString property (section 2.2.1.16).

  • The value of the PidLidToAttendeesString property (section 2.2.1.17).

  • The value of the PidLidCcAttendeesString property (section 2.2.1.18).

  • The value of the PidTagStartDate property (section 2.2.1.30).

  • The value of the PidTagEndDate property (section 2.2.1.31).

  • The value of the PidNameMeetingDoNotForward property (section 2.2.1.55).

  • The PidTagProcessed property (section 2.2.5.7) is not set.

The following optional steps SHOULD also be taken:

  • If the user has not modified the value of the PidLidReminderDelta property ([MS-OXORMDR] section 2.2.1.3) on the Meeting Request object from its default value (as defined by the client), the value of this property SHOULD be set to 0x5AE980E1.

  • The client SHOULD prepend downlevel text to the message body, as specified in 2.2.6.12.

After successfully sending a Meeting Request object, the client modifies the Meeting object in the organizer's Calendar folder in the following ways:

  • Set the value of the PidLidFInvited property (section 2.2.4.4) to TRUE.

  • Set the value of the PidLidToAttendeesString property equal to the value that was set on the Meeting Request object.

  • Set the value of the PidLidCcAttendeesString property equal to the value that was set on the Meeting Request object.

  • Set the value of PidLidOwnerCriticalChange property (section 2.2.1.34) equal to the value that was set on the Meeting Request object.