In this scenario, delegation functions as expected. The chairperson is notified, and the Outlook delegate is an invitee of the meeting. There is no action taken by Integration for Notes.
In this scenario, when the Outlook User forwards the meeting to a Notes User, an NDR will be returned to the Outlook User. The NDR instructs the user to notify the Chairperson that the attempted delegate should be added to the meeting. Once the delegate is added to the meeting, workflow functions as expected for an invitee.
Note: If BTDelegateNDR=N, the Domino delegate will receive the forwarded meeting, and can accept the meeting. However; any updates to the meeting will appear as a new meeting and workflow will not function properly. Depending on the meeting type and the changes made, the results can be duplicate calendar entries, deleted calendar entries, missing meeting updates and un-actionable meeting updates.
When the Outlook delegate acts on the invitation (accept/decline), he becomes an unknown invitee of the meeting. The Notes Chairperson’s calendar will not be updated, and no subsequent workflow is ever sent to him. Subsequent workflow (reschedules/cancels) is only sent to the delegator. For the delegate to receive any subsequent workflow, the delegator must continue to forward any meeting notifications.
Since the forwarding action is restricted to the Exchange system, Integration for Notes cannot take any action to remediate the result.
Note: If the Outlook recipient has configured the second Outlook User as a delegate to their calendar, forwarding will work as expected.
In this scenario, when the Outlook User forwards the meeting to a Notes User, an NDR will be returned to the Outlook User. The NDR instructs the user to notify the Chairperson that the attempted delegate should be added to the meeting. Once the delegate is added to the meeting, workflow functions as expected for an invitee.
Note: If BTDelegateNDR=N, the Notes delegate can accept the forwarded meeting invitation. The Outlook chairperson is correctly notified, and the Notes delegate is added as an optional attendee. Although this scenario functions as expected, Binary Tree still recommends that BTDelegateNDR be set to Y to prevent Outlook users from forwarding invitations chaired by Notes users. There is no identifying information in forwarded calendar items from Exchange to Domino that can discern the mail system of the chairperson.
Outlook Chairperson invites Notes User who delegates to an Outlook User
In this scenario, the following issues will occur:
When the Outlook delegate accepts the invitation, he becomes an optional invitee of the meeting.
The Outlook Chairperson receives the delegation notice, which is interpreted it as a tentative acceptance from the Notes delegator. The Notes delegator is still seen as a required invitee.
Subsequent workflow (reschedules/cancels) will be sent to both the delegator and the delegate.
When the Notes delegator receives the subsequent workflow, he cannot act on them (since it was delegated to another user).
Note: There is no identifying information in the delegated item sent from Domino to Exchange that would enable Integration for Notes to take remediation action.
© ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center
