Export (0) Print
Expand All

6 Appendix A: Product Behavior

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs.

  • Microsoft Exchange Server 2003

  • Microsoft Exchange Server 2007

  • Microsoft Exchange Server 2010

  • Microsoft Exchange Server 2013

  • Microsoft Exchange Server 2016

  • Microsoft Office Outlook 2003

  • Microsoft Office Outlook 2007

  • Microsoft Outlook 2010

  • Microsoft Outlook 2013

  • Microsoft Outlook 2016

Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms SHOULD or SHOULD NOT implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that the product does not follow the prescription.

<1> Section 2.2.1.1: Office Outlook 2003 does provide a way for the user to set the value of the PidTagFlagStatus property (section 2.2.1.1) on a Task object.

<2> Section 2.2.1.2: Office Outlook 2003 does provide a way for the user to set the value of the PidTagFollowupIcon property (section 2.2.1.2) on a Task object.

<3> Section 2.2.1.3: Office Outlook 2003 does provide a way for the user to set the value of the PidTagFlagCompleteTime property (section 2.2.1.3) on a Task object.

<4> Section 2.2.1.4: Office Outlook 2003 does provide a way for the user to set the value of the PidTagReplyRequested ([MS-OXOMSG] section 2.2.1.45) and PidTagResponseRequested ([MS-OXOMSG] section 2.2.1.46) properties on a Task object.

<5> Section 2.2.1.4: In Office Outlook 2007, when swapping the contents of the primary flag storage location and secondary flag storage location, the PidTagReplyRequested ([MS-OXOMSG] section 2.2.1.45) and PidTagResponseRequested ([MS-OXOMSG] section 2.2.1.46) properties do not get updated to the correct value according to the new flagging state of the primary flag storage location.

<6> Section 2.2.1.6: Exchange 2003 and Office Outlook 2003 do not read or write the PidTagToDoItemFlags property (section 2.2.1.6).

<7> Section 2.2.1.7: Exchange 2003 and Office Outlook 2003 do not support sender flags.

<8> Section 2.2.1.12: Office Outlook 2007 substitutes the concatenated values of PidTagSubjectPrefix ([MS-OXCMSG] section 2.2.1.9) and PidTagNormalizedSubject ([MS-OXCMSG] section 2.2.1.10) when displaying a Message object without a value in the PidLidToDoTitle property.

<9> Section 2.2.1.13: Exchange 2003 and Office Outlook 2003 do not read or write the PidLidToDoOrdinalDate property.

<10> Section 2.2.2.1: Office Outlook 2003 does not set the PidLidTaskStatus property (section 2.2.2.1).

<11> Section 2.2.2.2: Office Outlook 2003 does not set the PidLidTaskComplete property (section 2.2.2.2).

<12> Section 2.2.2.3: Office Outlook 2003 does not set the PidLidPercentComplete property (section 2.2.2.3).

<13> Section 3.1.4.1: The default Outlook user interface does not permit users to flag Appointment objects, Journal objects, or Note objects, but it is possible to manipulate the UI in nonstandard ways in order to set flag-related properties on such objects. Flagging Appointment objects, Journal objects, or Note objects will result in undefined behavior.

<14> Section 3.1.4.1.1: Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, Office Outlook 2007, Microsoft Outlook 2010, Outlook 2013, and Outlook 2016 do not support color flags.

<15> Section 3.1.4.1.2: Except for receiving a recipient flag, as described in section 3.1.4.1.5, basic flags are not supported by Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016.

<16> Section 3.1.4.1.3: Exchange 2003 and Office Outlook 2003 do not support time flags.

<17> Section 3.1.4.1.4: In addition to the exceptions as noted for individual properties, Exchange 2003 and Office Outlook 2003 do not set the following properties when marking a Message object complete: PidTagToDoItemFlags (section 2.2.1.6), PidLidToDoTitle (section 2.2.1.12), PidLidToDoOrdinalDate (section 2.2.1.13), PidLidToDoSubOrdinal (section 2.2.1.14), PidLidTaskDateCompleted ([MS-OXOTASK] section 2.2.2.2.9), PidLidTaskComplete ([MS-OXOTASK] section 2.2.2.2.20), PidLidTaskStatus ([MS-OXOTASK] section 2.2.2.2.2), and PidLidPercentComplete (section 2.2.2.3). Becuase Exchange 2003 and Office Outlook 2003 also do not set the PidTagFlagStatus property (section 2.2.1.1) for a meeting-related object, Exchange 2003 and Office Outlook 2003 do not support complete flags for a meeting-related object.

<18> Section 3.1.4.1.6: Office Outlook 2003 does not support sender flags. Only recipient flags can be set in Office Outlook 2003.

<19> Section 3.1.4.3: Exchange 2003 and Office Outlook 2003 do not support sender flags, and thus do not support post-transmit processing of a flagged message.

Show:
© 2016 Microsoft