4.2.2.1 Creating the Meeting
To create the Meeting object, the client uses the RopCreateMessage ROP ([MS-OXCROPS] section 2.2.6.2). The server returns a success code and a handle to a Message object.
The client then uses the RopSetProperties ROP ([MS-OXCROPS] section 2.2.8.6) to transmit Mr. John's data to the server. An example of the data that might be sent by the client is shown in the following table.
|
Property |
Property ID |
Property type |
Value |
|---|---|---|---|
|
PidTagNormalizedSubject ([MS-OXCMSG] section 2.2.1.10) |
0x0E1D |
0x001F (PtypString ([MS-OXCDATA] section 2.11.1.2)) |
Weekly meeting |
|
PidLidBusyStatus (section 2.2.1.2) |
0x81B6 |
0x0003 (PtypInteger32 ([MS-OXCDATA] section 2.11.1) |
0x00000002 (2) |
|
PidLidAppointmentColor ([MS-OXPROPS] section 2.9) |
0x82CA |
0x0003 (PtypInteger32) |
0x00000000 (0) |
|
PidLidLocation (section 2.2.1.4) |
0x8009 |
0x001F (PtypString) |
Your Office |
|
PidLidRecurring (section 2.2.1.12) |
0x81FD |
0x000B (PtypBoolean ([MS-OXCDATA] section 2.11.1)) |
0x01 (TRUE) |
|
PidLidAppointmentStartWhole (section 2.2.1.5) |
0x81B2 |
0x0040 (PtypTime ([MS-OXCDATA] section 2.11.1)) |
0x01C878A5984A4400 (2008/02/26 18:30:00.000) |
|
PidLidAppointmentEndWhole (section 2.2.1.6) |
0x81AC |
0x0040 (PtypTime) |
0x01C878A9C92C7800 (2008/02/26 19:00:00.000) |
|
PidLidAppointmentDuration (section 2.2.1.7) |
0x81A9 |
0x0003 (PtypInteger32) |
0x0000001E (30) |
|
PidLidAppointmentAuxiliaryFlags (section 2.2.1.3) |
0x82D2 |
0x0003 (PtypInteger32) |
0x00000000 (0) |
|
PidLidAppointmentSubType (section 2.2.1.9) |
0x8120 |
0x000B (PtypBoolean) |
0x00 (FALSE) |
|
PidLidAppointmentStateFlags (section 2.2.1.10) |
0x81B3 |
0x0003 (PtypInteger32) |
0x00000001 (1) |
|
PidLidResponseStatus (section 2.2.1.11) |
0x8122 |
0x0003 (PtypInteger32) |
respOrganized (0x00000001) |
|
PidLidAppointmentNotAllowPropose (section 2.2.1.26) |
0x82D5 |
0x000B (PtypBoolean) |
0x00 (FALSE) |
|
PidLidFInvited (section 2.2.4.4) |
0x81DA |
0x000B (PtypBoolean) |
0x00 (FALSE) |
|
PidLidRecurrenceType (section 2.2.1.45) |
0x81FE |
0x0003 (PtypInteger32) |
0x00000002 (2) |
|
PidLidRecurrencePattern (section 2.2.1.46) |
0x81FC |
0x001F (PtypString) |
Every Tuesday from 10:30 A.M. to 11:00 A.M. |
|
PidLidTimeZoneDescription (section 2.2.1.40) |
0x8213 |
0x001F (PtypString) |
(GMT-08:00) Pacific Time (U.S. & Canada) |
|
PidLidClipStart (section 2.2.1.14) |
0x81BA |
0x0040 (PtypTime) |
0x01C8784D95BC0000 (2008/02/26 08:00:00.000) |
|
PidLidClipEnd (section 2.2.1.15) |
0x81B9 |
0x0040 (PtypTime) |
0x0CB2E57949B47A00 (4500/08/31 23:59:00.000) |
|
PidLidToAttendeesString (section 2.2.1.17) |
0x82D9 |
0x001F (PtypString) |
desaylor |
|
PidLidAppointmentSequence (section 2.2.1.1) |
0x81AF |
0x0003 (PtypInteger32) |
0x00000000 (0) |
|
PidLidAutoFillLocation (section 2.2.4.8) |
0x82E8 |
0x000B (PtypBoolean) |
0x00 (FALSE) |
|
PidLidReminderDelta ([MS-OXORMDR] section 2.2.1.3) |
0x81FF |
0x0003 (PtypInteger32) |
0x0000000F (15) |
|
PidLidReminderTime ([MS-OXORMDR] section 2.2.1.4) |
0x8005 |
0x0040 (PtypTime) |
0x01C878A5984A4400 (2008/02/26 18:30:00.000) |
|
PidLidReminderSignalTime ([MS-OXORMDR] section 2.2.1.2) |
0x8006 |
0x0040 (PtypTime) |
0x01C878A37FD92A00 (2008/02/26 18:15:00.000) |
|
PidLidCommonStart ([MS-OXCMSG] section 2.2.1.18) |
0x81BC |
0x0040 (PtypTime) |
0x01C878A5984A4400 (2008/02/26 18:30:00.000) |
|
PidLidCommonEnd ([MS-OXCMSG] section 2.2.1.19) |
0x81BB |
0x0040 (PtypTime) |
0x01C878A9C92C7800 (2008/02/26 19:00:00.000) |
|
PidLidReminderSet ([MS-OXORMDR] section 2.2.1.1) |
0x8004 |
0x000B (PtypBoolean) |
0x01 (TRUE) |
|
PidLidSideEffects ([MS-OXCMSG] section 2.2.1.16) |
0x8002 |
0x0003 (PtypInteger32) |
0x00000171 (369) |
|
PidLidMeetingType (section 2.2.6.5) |
0x8314 |
0x0003 (PtypInteger32) |
0x00000001 (1) |
|
PidTagMessageClass ([MS-OXCMSG] section 2.2.1.3) |
0x001A |
0x001F (PtypString) |
IPM.Appointment |
|
PidTagResponseRequested ([MS-OXPROPS] section 2.930 |
0x0063 |
0x000B (PtypBoolean) |
0x01 (TRUE) |
|
PidTagIconIndex (section 2.2.1.49) |
0x1080 |
0x0003 (PtypInteger32) |
0x00000403 (1027) |
|
PidLidTimeZoneStruct (section 2.2.1.39) |
0x8214 |
0x0102 (PtypBinary ([MS-OXCDATA] section 2.11.1)) |
See paragraph marked *1 following this table. |
|
PidLidAppointmentTimeZoneDefinitionRecur (section 2.2.1.41) |
0x83AA |
0x0102 (PtypBinary) |
See paragraph marked *2 following this table. |
|
PidLidAppointmentTimeZoneDefinitionStartDisplay (section 2.2.1.42) |
0x83A8 |
0x0102 (PtypBinary) |
See paragraph marked *3 following this table. |
|
PidLidAppointmentTimeZoneDefinitionEndDisplay (section 2.2.1.43) |
0x83A9 |
0x0102 (PtypBinary) |
See paragraph marked *3 following this table. |
|
PidLidGlobalObjectId (section 2.2.1.27) |
0x81E0 |
0x0102 (PtypBinary) |
See paragraph marked *4 following this table. |
|
PidLidCleanGlobalObjectId (section 2.2.1.28) |
0x81B8 |
0x0102 (PtypBinary) |
See paragraph marked *4 following this table. |
|
PidLidAppointmentRecur (section 2.2.1.44) |
0x81AD |
0x0102 (PtypBinary) |
See paragraph marked *5 following this table. |
|
Best body properties |
A body stream, the text of which was written by Mr. John, that indicates to Mr. Saylor the purpose of the meeting. For more information, see [MS-OXBBODY]. |
||
*1 For an example of the PidLidTimeZoneStruct property BLOB, see section 4.1.5. The value for this Meeting object is as follows:
-
cb: 48 lpb: E001000000000000C4FFFFFF000000000B00000001000200000000000000000000000300000002000200000000000000
*2 The date values for the PidLidAppointmentTimeZoneDefinitionRecur property for this appointment are both set in the same time zone. For an example of the time zone definition property BLOB, see section 4.1.4. The only difference between this BLOB and that in the PidLidAppointmentTimeZoneDefinitionStartDisplay and PidLidAppointmentTimeZoneDefinitionEndDisplay properties is that the TZRULE_FLAG_RECUR_CURRENT_TZREG flag is set in this BLOB. The value for this Meeting object is as follows:
-
cb: 184 lpb: 0201300002001500500061006300690066006900630020005300740061006E0064006100720064002000540069006D006500020002013E000000D6070000000000000000000000000000E001000000000000C4FFFFFF00000A000000050002000000000000000000040000000100020000000000000002013E000300D7070000000000000000000000000000E001000000000000C4FFFFFF00000B0000000100020000000000000000000300000002000200000000000000
*3 The start and end dates for this appointment are both set in the same time zone. The value for this Meeting object is as follows:
-
cb: 184 lpb: 0201300002001500500061006300690066006900630020005300740061006E0064006100720064002000540069006D006500020002013E000000D6070000000000000000000000000000E001000000000000C4FFFFFF00000A000000050002000000000000000000040000000100020000000000000002013E000200D7070000000000000000000000000000E001000000000000C4FFFFFF00000B0000000100020000000000000000000300000002000200000000000000
*4 This Meeting object is a recurring series, so the values of the PidLidGlobalObjectId property and the PidLidCleanGlobalObjectId property are the same. For an example of the Global Object ID BLOB, see section 4.1.2. The value for this Meeting object is as follows:
-
cb: 56 lpb: 040000008200E00074C5B7101A82E00800000000406FD661E473C8010000000000000000100000002A5844B3A444F74A9C246C60886F116B
*5 Section 4.1.1.2 shows an example of the recurrence BLOB for a weekly recurring meeting. The value for this Meeting object is as follows:
-
cb: 80 lpb: 043004300B2001000000C0210000010000000000000004000000232000000A0000000000000000000000000000002088C30CDF80E95A0630000009300000760200009402000000000000000000000000
The client uses the RopModifyRecipients ROP ([MS-OXCROPS] section 2.2.6.5) to add Dennis Saylor to the Meeting object, including the extra properties listed in the following table.
|
Property |
Property ID |
Property type |
Value |
|---|---|---|---|
|
PidTagRecipientFlags (section 2.2.4.10.1) |
0x5FFD |
0x0003 (PtypInteger32) |
0x00000201 (513) |
|
PidTagRecipientTrackStatus (section 2.2.4.10.2) |
0x5FFF |
0x0003 (PtypInteger32) |
0x00000000 (0) |
After setting all property values, the client can use the RopSaveChangesMessage ROP ([MS-OXCROPS] section 2.2.6.3) to commit the properties on the server. Without these properties, the newly created object will not be persisted. The server returns a success code that indicates that the data has been accepted.