4.2 Time Flagged Object
Kendall Keil has a message in his Inbox with the subject "Contoso Project", and he wants to be sure to remember to follow up on that message starting on 2008/02/11, and he needs to be done by 2008/02/12. He uses the default request string designated by the client, which is "Follow up". He flags the item on 2008/02/11 22:16:28.177 (UTC). The following is a description of what a client might do to accomplish Kendall's intentions and the responses a server might return.
As before, the client first retrieves a handle to the Message object by sending a RopOpenMessage ROP request ([MS-OXCROPS] section 2.2.6.1).
Besides a handle, the server returns the following relevant data in the RopOpenMessage ROP response ([MS-OXCROPS] section 2.2.6.1).
Property |
Property ID |
Property type |
Value |
---|---|---|---|
PidTagNormalizedSubject ([MS-OXCMSG] section 2.2.1.10) |
0x0E1D |
0x001F (PtypString ([MS-OXCDATA] section 2.11.1)) |
"Contoso Project" |
To retrieve the state of the Message object, the client sends a RopGetPropertiesSpecific ROP request ([MS-OXCROPS] section 2.2.8.3).
Property |
Property ID |
Property type |
---|---|---|
PidTagMessageDeliveryTime ([MS-OXOMSG] section 2.2.3.9) |
0x0E06 |
0x0040 (PtypTime ([MS-OXCDATA] section 2.11.1)) |
The client receives a ROP response buffer from the server with the requested values.
Property |
Property ID |
Property type |
Value |
---|---|---|---|
PidTagMessageDeliveryTime |
0x0E06 |
0x0040 |
2008/02/11 22:41:24.765 |
To set the properties for the time flag, the client sends a RopSetProperties ROP request ([MS-OXCROPS] section 2.2.8.6) with the values that are specified in the following table.
Property |
Property ID |
Property type |
Value |
---|---|---|---|
PidTagFlagStatus (section 2.2.1.1) |
0x1090 |
0x0003 (PtypInteger32 ([MS-OXCDATA] section 2.11.1)) |
0x00000002 |
PidTagFollowupIcon (section 2.2.1.2) |
0x1095 |
0x0003 |
0x00000006 |
PidTagReplyRequested (section 2.2.1.4) |
0x0C17 |
0x000B (PtypBoolean ([MS-OXCDATA] section 2.11.1)) |
0x01 (TRUE) |
PidTagResponseRequested (section 2.2.1.5) |
0x0063 |
0x000B |
0x01 (TRUE) |
PidTagToDoItemFlags (section 2.2.1.6) |
0x0E2B |
0x0003 |
0x00000001 |
PidLidFlagRequest (section 2.2.1.9) |
0x802A |
0x001F |
"Follow up" |
PidLidFlagString (section 2.2.1.10) |
0x83C0 |
0x0003 |
0x00000003 |
PidLidValidFlagStringProof (section 2.2.1.11) |
0x83CA |
0x0040 |
2008/02/11 22:41:24.765 |
PidLidToDoTitle (section 2.2.1.12) |
0x8018 |
0x001F |
"Contoso Project" |
PidLidToDoOrdinalDate (section 2.2.1.13) |
0x830D |
0x0040 |
2008/02/11 22:16:28.177 |
PidLidToDoSubOrdinal (section 2.2.1.14) |
0x830E |
0x001F |
"5555555" |
PidLidTaskStartDate ([MS-OXOTASK] section 2.2.2.2.4) |
0x8143 |
0x0040 |
2008/02/11 00:00:00.000 |
PidLidTaskDueDate ([MS-OXOTASK] section 2.2.2.2.5) |
0x8144 |
0x0040 |
2008/02/12 00:00:00.000 |
PidLidCommonStart ([MS-OXCMSG] section 2.2.1.18) |
0x81BC |
0x0040 |
2008/02/11 08:00:00.000 |
PidLidCommonEnd ([MS-OXCMSG] section 2.2.1.19) |
0x81BB |
0x0040 |
2008/02/12 08:00:00.000 |
Finally, to persist the Message object on the server, the client sends a RopSaveChangesMessage ROP request ([MS-OXCROPS] section 2.2.6.3) followed by a RopRelease ROP request ([MS-OXCROPS] section 2.2.15.3) to release the object.