Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

3.1.4.4 Sending a Task Communication

The client creates a task communication, as specified in section 3.1.4.1, and then adds the recipients (2) and saves the Message object, as specified in [MS-OXCMSG]. The client then performs other actions, which are dependent on the particular type of task communication that will be sent. To send the task communication, the client submits the task communication for delivery, as specified in [MS-OXOMSG].

Task request: Before the client sends a task request, it computes the name of the new owner of the task by retrieving the primary recipients from the Task object. If there is only one primary recipient, its display name is the name of the new owner. If there are multiple primary recipients, the new owner name is derived by concatenating the display names of all the primary recipients, separated with semicolons (";"). A task can be assigned to only one task assignee. If a Task object has more than one primary recipient, the task is shared, not assigned. A Task object that is in a public folder is not assigned. The client sets the value of the PidLidTaskOwner property (section 2.2.2.2.22) of the Task object with this new owner name. The client also sets the value of the PidLidTaskGlobalId property (section 2.2.2.2.32) of the Task object to a new, unique GUID if it does not already have one.

Task acceptance: When the client sends a task acceptance, the client creates a local Task object and copies to it the relevant properties from the embedded Task object of the task request. Then, the client sets the recipient (2) to the last task assigner listed in the PidLidTaskAssigners property (section 2.2.2.2.16) of the Task object. The stack of task assigners is deleted from the PidLidTaskAssigners property, leaving only the most recent task assigner. The client sets the PidLidTaskOwnership property (section 2.2.2.2.29) to 0x00000002. The client does not send a task acceptance when the Task object has more than one primary recipient.

Task rejection: When the client sends a task rejection, it removes the last entry from the PidLidTaskAssigners property of the Task object. The client sets the value of the PidLidTaskOwner property of the Task object to the name from this last entry. Then, the client sets the recipient (2) to the last task assigner listed in the PidLidTaskAssigners property of the Task object. The client does not send a task rejection when the Task object has more than one primary recipient.

Task update: When the client changes a Task object, it sends a task update to all Cc recipients of the Task object if the PidLidTaskUpdates property (section 2.2.2.2.19) is set to nonzero (TRUE). The revised Task object is embedded in the task update, as specified in section 3.1.4.3. When the client sends a task update, it sets the recipient (2) to the last task assigner listed in the PidLidTaskAssigners property of the Task object. The client does not send a task update when the Task object has more than one primary recipient.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.