@@ -3704,6 +3704,133 @@ methods:
3704
3704
return :
3705
3705
type : void
3706
3706
description : ' '
3707
+ - name : ' sendAsync(options, callback)'
3708
+ uid : ' outlook!Office.AppointmentCompose#sendAsync:member(1)'
3709
+ package : outlook!
3710
+ fullName : ' sendAsync(options, callback)'
3711
+ summary : Sends the appointment being composed.
3712
+ remarks : >-
3713
+ \[ [API set: Mailbox 1.15](/javascript/api/requirement-sets/outlook/outlook-api-requirement-sets) \]
3714
+
3715
+
3716
+ **[Minimum permission
3717
+ level](https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions)<!--
3718
+ -->**: **read/write mailbox**
3719
+
3720
+
3721
+ **[Applicable Outlook
3722
+ mode](https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points)<!--
3723
+ -->**: Appointment Organizer
3724
+
3725
+
3726
+ **Important**:
3727
+
3728
+
3729
+ - The `sendAsync` method is only supported in task pane and function command implementations. It isn't supported
3730
+ in [event-based handlers](https://learn.microsoft.com/office/dev/add-ins/outlook/autolaunch) or [item multi-select
3731
+ scenarios](https://learn.microsoft.com/office/dev/add-ins/outlook/item-multi-select)<!-- -->.
3732
+
3733
+
3734
+ - In a function command implementation, the value returned in `asyncResult.status` may not reflect whether the
3735
+ appointment being composed is successfully sent. This is because the `sendAsync` method is an asynchronous API and
3736
+ events outside the add-in's control (for example, events handled by a separately installed [Smart Alerts
3737
+ add-in](https://learn.microsoft.com/office/dev/add-ins/outlook/onmessagesend-onappointmentsend-events)<!-- -->)
3738
+ could block the item from being sent. Since you can't rely on the status returned in `asyncResult.status` to run
3739
+ certain operations, you should only call the
3740
+ [event.completed](https://learn.microsoft.com/javascript/api/office/office.addincommands.event#office-office-addincommands-event-completed-member(1))
3741
+ method in the callback function. The `event.completed` call signals that the add-in has completed processing.
3742
+ Other than this call, other code in the callback function isn't guaranteed to run. We recommend processing other
3743
+ operations before calling `sendAsync`<!-- -->.
3744
+
3745
+
3746
+ - In a task pane implementation, any code included to run when `asyncResult.status` is
3747
+ `Office.AsyncResultStatus.Success` isn't guaranteed to be processed. This is because the item may have already
3748
+ been sent and the add-in has completed processing. We recommend processing other operations before calling
3749
+ `sendAsync`<!-- -->.
3750
+
3751
+
3752
+ - Any code included after the `sendAsync` call isn't guaranteed to run since the add-in completes processing after
3753
+ the `sendAsync` call.
3754
+ isPreview : false
3755
+ isDeprecated : false
3756
+ syntax :
3757
+ content : >-
3758
+ sendAsync(options: Office.AsyncContextOptions, callback?: (asyncResult: Office.AsyncResult<void>) =>
3759
+ void): void;
3760
+ parameters :
3761
+ - id : options
3762
+ description : >-
3763
+ An object literal that contains the `asyncContext` property. Use the `asyncContext` property to specify any
3764
+ object you want to access in the callback function.
3765
+ type : ' <xref uid="office!Office.AsyncContextOptions:interface" />'
3766
+ - id : callback
3767
+ description : >-
3768
+ Optional. When the method completes, the function passed in the `callback` parameter is called with a single
3769
+ parameter, `asyncResult`<!-- -->. The `asyncResult` parameter is an `Office.AsyncResult` object.
3770
+ type : ' (asyncResult: <xref uid="office!Office.AsyncResult:interface" /><void>) => void'
3771
+ return :
3772
+ type : void
3773
+ description : ' '
3774
+ - name : sendAsync(callback)
3775
+ uid : ' outlook!Office.AppointmentCompose#sendAsync:member(2)'
3776
+ package : outlook!
3777
+ fullName : sendAsync(callback)
3778
+ summary : Sends the appointment being composed.
3779
+ remarks : >-
3780
+ \[ [API set: Mailbox 1.15](/javascript/api/requirement-sets/outlook/outlook-api-requirement-sets) \]
3781
+
3782
+
3783
+ **[Minimum permission
3784
+ level](https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions)<!--
3785
+ -->**: **read/write mailbox**
3786
+
3787
+
3788
+ **[Applicable Outlook
3789
+ mode](https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points)<!--
3790
+ -->**: Appointment Organizer
3791
+
3792
+
3793
+ **Important**:
3794
+
3795
+
3796
+ - The `sendAsync` method is only supported in task pane and function command implementations. It isn't supported
3797
+ in [event-based handlers](https://learn.microsoft.com/office/dev/add-ins/outlook/autolaunch) or [item multi-select
3798
+ scenarios](https://learn.microsoft.com/office/dev/add-ins/outlook/item-multi-select)<!-- -->.
3799
+
3800
+
3801
+ - In a function command implementation, the value returned in `asyncResult.status` may not reflect whether the
3802
+ appointment being composed is successfully sent. This is because the `sendAsync` method is an asynchronous API and
3803
+ events outside the add-in's control (for example, events handled by a separately installed [Smart Alerts
3804
+ add-in](https://learn.microsoft.com/office/dev/add-ins/outlook/onmessagesend-onappointmentsend-events)<!-- -->)
3805
+ could block the item from being sent. Since you can't rely on the status returned in `asyncResult.status` to run
3806
+ certain operations, you should only call the
3807
+ [event.completed](https://learn.microsoft.com/javascript/api/office/office.addincommands.event#office-office-addincommands-event-completed-member(1))
3808
+ method in the callback function. The `event.completed` call signals that the add-in has completed processing.
3809
+ Other than this call, other code in the callback function isn't guaranteed to run. We recommend processing other
3810
+ operations before calling `sendAsync`<!-- -->.
3811
+
3812
+
3813
+ - In a task pane implementation, any code included to run when `asyncResult.status` is
3814
+ `Office.AsyncResultStatus.Success` isn't guaranteed to be processed. This is because the item may have already
3815
+ been sent and the add-in has completed processing. We recommend processing other operations before calling
3816
+ `sendAsync`<!-- -->.
3817
+
3818
+
3819
+ - Any code included after the `sendAsync` call isn't guaranteed to run since the add-in completes processing after
3820
+ the `sendAsync` call.
3821
+ isPreview : false
3822
+ isDeprecated : false
3823
+ syntax :
3824
+ content : ' sendAsync(callback?: (asyncResult: Office.AsyncResult<void>) => void): void;'
3825
+ parameters :
3826
+ - id : callback
3827
+ description : >-
3828
+ Optional. When the method completes, the function passed in the `callback` parameter is called with a single
3829
+ parameter, `asyncResult`<!-- -->. The `asyncResult` parameter is an `Office.AsyncResult` object.
3830
+ type : ' (asyncResult: <xref uid="office!Office.AsyncResult:interface" /><void>) => void'
3831
+ return :
3832
+ type : void
3833
+ description : ' '
3707
3834
- name : ' setSelectedDataAsync(data, options, callback)'
3708
3835
uid : ' outlook!Office.AppointmentCompose#setSelectedDataAsync:member(1)'
3709
3836
package : outlook!
0 commit comments