Export (0) Print
Expand All

3.1.4.1 Creating a Task Object and a Task Communication

To create a Task object, the client creates a Message object as specified in [MS-OXCMSG] section 3.1.4.2. The client adds a user as a carbon copy (Cc) recipient if that user is to receive task updates. The client adds a user as a blind carbon copy (Bcc) recipient and sets the PidLidTaskStatusOnComplete property (section 2.2.2.2.17) to nonzero (TRUE) if that user is to receive an e-mail status report when the task is completed. The client sets properties in accordance with the requirements in section 2.2.2 of this document and saves the Message object as specified in [MS-OXCMSG].

Although Task objects support recipients (2), the client does not submit a Task object to the server for delivery to other users. Instead, the client submits a task communication. To create a task communication, the client creates a Message object as specified in [MS-OXCMSG] section 3.1.4.2, sets properties in accordance with the requirements in section 2.2.3 of this document, and saves the Message object as specified in [MS-OXCMSG] section 3.1.4.3. The client embeds a copy of the Task object as an Attachment object within the task communication (the embedding object). For details about embedding a Task object, see section 3.1.4.3. A Task object that is in a public folder is not assigned. Therefore, the client MUST NOT create a task request for a Task object that is in a public folder.

Show:
© 2015 Microsoft