@types/office-js-preview 1.0.461 → 1.0.462
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- office-js-preview/README.md +1 -1
- office-js-preview/index.d.ts +252 -32
- office-js-preview/package.json +2 -2
office-js-preview/README.md
CHANGED
|
@@ -8,7 +8,7 @@ This package contains type definitions for office-js-preview (https://github.com
|
|
|
8
8
|
Files were exported from https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/office-js-preview.
|
|
9
9
|
|
|
10
10
|
### Additional Details
|
|
11
|
-
* Last updated:
|
|
11
|
+
* Last updated: Tue, 09 Apr 2024 18:07:35 GMT
|
|
12
12
|
* Dependencies: none
|
|
13
13
|
|
|
14
14
|
# Credits
|
office-js-preview/index.d.ts
CHANGED
|
@@ -15241,6 +15241,29 @@ declare namespace Office {
|
|
|
15241
15241
|
*
|
|
15242
15242
|
* **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Compose or Read
|
|
15243
15243
|
*
|
|
15244
|
+
* **Important**:
|
|
15245
|
+
*
|
|
15246
|
+
* - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and
|
|
15247
|
+
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens will be turned off by default for all Exchange Online tenants.
|
|
15248
|
+
* This is part of {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative},
|
|
15249
|
+
* which gives organizations the tools needed to respond to the current threat landscape. Exchange user identity tokens will still work for Exchange on-premises.
|
|
15250
|
+
* Nested app authentication is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and
|
|
15251
|
+
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}.
|
|
15252
|
+
*
|
|
15253
|
+
* - This method is only supported in read mode in Outlook on Android and on iOS. For more information on supported APIs in Outlook mobile, see
|
|
15254
|
+
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}.
|
|
15255
|
+
*
|
|
15256
|
+
* - EWS operations aren't supported in add-ins running in Outlook on iOS and on Android. A REST token is always returned in Outlook
|
|
15257
|
+
* mobile clients even if `options.isRest` is set to `false`.
|
|
15258
|
+
*
|
|
15259
|
+
*- Calling the `getCallbackTokenAsync` method in read mode requires a minimum permission level of **read item**.
|
|
15260
|
+
*
|
|
15261
|
+
* - Calling the `getCallbackTokenAsync` method in compose mode requires you to have saved the item.
|
|
15262
|
+
* The `saveAsync` method requires a minimum permission level of **read/write item**.
|
|
15263
|
+
*
|
|
15264
|
+
* - For guidance on delegate or shared scenarios, see the
|
|
15265
|
+
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/delegate-access | shared folders and shared mailbox} article.
|
|
15266
|
+
*
|
|
15244
15267
|
* *REST Tokens*
|
|
15245
15268
|
*
|
|
15246
15269
|
* When a REST token is requested (`options.isRest` = `true`), the resulting token won't work to authenticate EWS calls.
|
|
@@ -15275,22 +15298,6 @@ declare namespace Office {
|
|
|
15275
15298
|
* attachment or item. For example, you can create a remote service to
|
|
15276
15299
|
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/get-attachments-of-an-outlook-item | get attachments from the selected item}.
|
|
15277
15300
|
*
|
|
15278
|
-
* **Important**:
|
|
15279
|
-
*
|
|
15280
|
-
* - This method is only supported in read mode in Outlook on Android and on iOS. For more information on supported APIs in Outlook mobile, see
|
|
15281
|
-
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}.
|
|
15282
|
-
*
|
|
15283
|
-
* - EWS operations aren't supported in add-ins running in Outlook on iOS and on Android. A REST token is always returned in Outlook
|
|
15284
|
-
* mobile clients even if `options.isRest` is set to `false`.
|
|
15285
|
-
*
|
|
15286
|
-
*- Calling the `getCallbackTokenAsync` method in read mode requires a minimum permission level of **read item**.
|
|
15287
|
-
*
|
|
15288
|
-
* - Calling the `getCallbackTokenAsync` method in compose mode requires you to have saved the item.
|
|
15289
|
-
* The `saveAsync` method requires a minimum permission level of **read/write item**.
|
|
15290
|
-
*
|
|
15291
|
-
* - For guidance on delegate or shared scenarios, see the
|
|
15292
|
-
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/delegate-access | shared folders and shared mailbox} article.
|
|
15293
|
-
*
|
|
15294
15301
|
* **Errors**:
|
|
15295
15302
|
*
|
|
15296
15303
|
* - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code.
|
|
@@ -15324,6 +15331,13 @@ declare namespace Office {
|
|
|
15324
15331
|
*
|
|
15325
15332
|
* **Important**:
|
|
15326
15333
|
*
|
|
15334
|
+
* - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and
|
|
15335
|
+
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens will be turned off by default for all Exchange Online tenants.
|
|
15336
|
+
* This is part of {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative},
|
|
15337
|
+
* which gives organizations the tools needed to respond to the current threat landscape. Exchange user identity tokens will still work for Exchange on-premises.
|
|
15338
|
+
* Nested app authentication is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and
|
|
15339
|
+
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}.
|
|
15340
|
+
*
|
|
15327
15341
|
* - You can pass both the token and either an attachment identifier or item identifier to an external system. That system uses
|
|
15328
15342
|
* the token as a bearer authorization token to call the Exchange Web Services (EWS)
|
|
15329
15343
|
* {@link https://learn.microsoft.com/exchange/client-developer/web-service-reference/getattachment-operation | GetAttachment} or
|
|
@@ -15412,7 +15426,16 @@ declare namespace Office {
|
|
|
15412
15426
|
*
|
|
15413
15427
|
* **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Compose or Read
|
|
15414
15428
|
*
|
|
15415
|
-
*
|
|
15429
|
+
* **Important**:
|
|
15430
|
+
*
|
|
15431
|
+
* - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and
|
|
15432
|
+
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens will be turned off by default for all Exchange Online tenants.
|
|
15433
|
+
* This is part of {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative},
|
|
15434
|
+
* which gives organizations the tools needed to respond to the current threat landscape. Exchange user identity tokens will still work for Exchange on-premises.
|
|
15435
|
+
* Nested app authentication is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and
|
|
15436
|
+
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}.
|
|
15437
|
+
*
|
|
15438
|
+
* - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and
|
|
15416
15439
|
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication | authenticate the add-in and user with an external system}.
|
|
15417
15440
|
*
|
|
15418
15441
|
* **Errors**:
|
|
@@ -15444,6 +15467,13 @@ declare namespace Office {
|
|
|
15444
15467
|
*
|
|
15445
15468
|
* **Important**:
|
|
15446
15469
|
*
|
|
15470
|
+
* - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and
|
|
15471
|
+
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} tokens will be turned off by default for all Exchange Online tenants.
|
|
15472
|
+
* This is part of {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative},
|
|
15473
|
+
* which gives organizations the tools needed to respond to the current threat landscape. Exchange user identity tokens will still work for Exchange on-premises.
|
|
15474
|
+
* Nested app authentication is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and
|
|
15475
|
+
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}.
|
|
15476
|
+
*
|
|
15447
15477
|
* - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set `OAuthAuthentication` to `true` on the
|
|
15448
15478
|
* Client Access Server EWS directory .
|
|
15449
15479
|
*
|
|
@@ -15863,6 +15893,26 @@ declare namespace Office {
|
|
|
15863
15893
|
* {@link https://learn.microsoft.com/office/dev/add-ins/outlook/mobile-event-based | Implement event-based activation in Outlook mobile add-ins}.
|
|
15864
15894
|
*/
|
|
15865
15895
|
from: From;
|
|
15896
|
+
/**
|
|
15897
|
+
* Gets the message ID of the original message being replied to by the current message.
|
|
15898
|
+
*
|
|
15899
|
+
* @remarks
|
|
15900
|
+
* [Api set: Mailbox preview]
|
|
15901
|
+
*
|
|
15902
|
+
* **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read item**
|
|
15903
|
+
*
|
|
15904
|
+
* **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Compose
|
|
15905
|
+
*
|
|
15906
|
+
* **Important**:
|
|
15907
|
+
*
|
|
15908
|
+
* - To preview the `inReplyTo` property, you must install Outlook on Windows Version 2402 (Build 17317.20000) or later. Then, join the
|
|
15909
|
+
* {@link https://insider.microsoft365.com/join/Windows | Microsoft 365 Insider program} and select the **Beta Channel** option to access Office beta builds.
|
|
15910
|
+
*
|
|
15911
|
+
* - In Outlook on Windows, the `inReplyTo` value is maintained on all replies regardless of changes made by the user, such as changing the subject in a reply.
|
|
15912
|
+
*
|
|
15913
|
+
* @beta
|
|
15914
|
+
*/
|
|
15915
|
+
inReplyTo: string;
|
|
15866
15916
|
/**
|
|
15867
15917
|
* Gets or sets the custom internet headers of a message.
|
|
15868
15918
|
*
|
|
@@ -16542,6 +16592,54 @@ declare namespace Office {
|
|
|
16542
16592
|
* An object with `ComposeType` and `CoercionType` enum values for the message item.
|
|
16543
16593
|
*/
|
|
16544
16594
|
getComposeTypeAsync(callback: (asyncResult: Office.AsyncResult<any>) => void): void;
|
|
16595
|
+
/**
|
|
16596
|
+
* Gets the Base64-encoded position of the current message in a conversation thread.
|
|
16597
|
+
*
|
|
16598
|
+
* @remarks
|
|
16599
|
+
* [Api set: Mailbox preview]
|
|
16600
|
+
*
|
|
16601
|
+
* **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read item**
|
|
16602
|
+
*
|
|
16603
|
+
* **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Compose
|
|
16604
|
+
*
|
|
16605
|
+
* **Important**: To preview the `getConversationIndexAsync` method, you must install Outlook on Windows Version 2402 (Build 17317.20000) or later. Then, join the
|
|
16606
|
+
* {@link https://insider.microsoft365.com/join/Windows | Microsoft 365 Insider program} and select the **Beta Channel** option to access Office beta builds.
|
|
16607
|
+
*
|
|
16608
|
+
* **Tip**: You can use the conversation index to locate a message in a conversation thread. Then, use its contents
|
|
16609
|
+
* to provide context for the current message being composed.
|
|
16610
|
+
*
|
|
16611
|
+
* @param options - An object literal that contains one or more of the following properties:-
|
|
16612
|
+
* `asyncContext`: Developers can provide any object they wish to access in the callback function.
|
|
16613
|
+
* @param callback - When the method completes, the function passed in the `callback` parameter is called with a single parameter, `asyncResult`, which is an
|
|
16614
|
+
* `Office.AsyncResult` object. The Base64-encoded position of the current message in a conversation is returned in the `asyncResult.value`
|
|
16615
|
+
* property.
|
|
16616
|
+
*
|
|
16617
|
+
* @beta
|
|
16618
|
+
*/
|
|
16619
|
+
getConversationIndexAsync(options: Office.AsyncContextOptions, callback: (asyncResult: Office.AsyncResult<string>) => void): void;
|
|
16620
|
+
/**
|
|
16621
|
+
* Gets the Base64-encoded position of the current message in a conversation thread.
|
|
16622
|
+
*
|
|
16623
|
+
* @remarks
|
|
16624
|
+
* [Api set: Mailbox preview]
|
|
16625
|
+
*
|
|
16626
|
+
* **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read item**
|
|
16627
|
+
*
|
|
16628
|
+
* **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Compose
|
|
16629
|
+
*
|
|
16630
|
+
* **Important**: To preview the `getConversationIndexAsync` method, you must install Outlook on Windows Version 2402 (Build 17317.20000) or later. Then, join the
|
|
16631
|
+
* {@link https://insider.microsoft365.com/join/Windows | Microsoft 365 Insider program} and select the **Beta Channel** option to access Office beta builds.
|
|
16632
|
+
*
|
|
16633
|
+
* **Tip**: You can use the conversation index to locate a message in a conversation thread. Then, use its contents
|
|
16634
|
+
* to provide context for the current message being composed.
|
|
16635
|
+
*
|
|
16636
|
+
* @param callback - When the method completes, the function passed in the `callback` parameter is called with a single parameter, `asyncResult`, which is an
|
|
16637
|
+
* `Office.AsyncResult` object. The Base64-encoded position of the current message in a conversation is returned in the `asyncResult.value`
|
|
16638
|
+
* property.
|
|
16639
|
+
*
|
|
16640
|
+
* @beta
|
|
16641
|
+
*/
|
|
16642
|
+
getConversationIndexAsync(callback: (asyncResult: Office.AsyncResult<string>) => void): void;
|
|
16545
16643
|
/**
|
|
16546
16644
|
* Gets initialization data passed when the add-in is {@link https://learn.microsoft.com/outlook/actionable-messages/invoke-add-in | activated by an actionable message}.
|
|
16547
16645
|
*
|
|
@@ -16557,7 +16655,7 @@ declare namespace Office {
|
|
|
16557
16655
|
* @param callback - When the method completes, the function passed in the `callback` parameter is called with a single parameter
|
|
16558
16656
|
* of type `Office.AsyncResult`.
|
|
16559
16657
|
* On success, the initialization context data is provided as a string (or an empty string if there's no initialization context)
|
|
16560
|
-
* in the `asyncResult.value` property
|
|
16658
|
+
* in the `asyncResult.value` property.
|
|
16561
16659
|
*/
|
|
16562
16660
|
getInitializationContextAsync(options: Office.AsyncContextOptions, callback: (asyncResult: Office.AsyncResult<string>) => void): void;
|
|
16563
16661
|
/**
|
|
@@ -16576,6 +16674,116 @@ declare namespace Office {
|
|
|
16576
16674
|
* in the `asyncResult.value` property.
|
|
16577
16675
|
*/
|
|
16578
16676
|
getInitializationContextAsync(callback: (asyncResult: Office.AsyncResult<string>) => void): void;
|
|
16677
|
+
/**
|
|
16678
|
+
* Gets the Exchange Web Services item class of the selected message.
|
|
16679
|
+
*
|
|
16680
|
+
* @remarks
|
|
16681
|
+
* [Api set: Mailbox preview]
|
|
16682
|
+
*
|
|
16683
|
+
* **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read item**
|
|
16684
|
+
*
|
|
16685
|
+
* **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Compose
|
|
16686
|
+
*
|
|
16687
|
+
* **Important**:
|
|
16688
|
+
*
|
|
16689
|
+
* To preview the `getItemClassAsync` method, you must install Outlook on Windows Version 2402 (Build 17317.20000) or later. Then, join the
|
|
16690
|
+
* {@link https://insider.microsoft365.com/join/Windows | Microsoft 365 Insider program} and select the **Beta Channel** option to access Office beta builds.
|
|
16691
|
+
*
|
|
16692
|
+
* The following table lists the default message classes.
|
|
16693
|
+
*
|
|
16694
|
+
* <table>
|
|
16695
|
+
* <tr>
|
|
16696
|
+
* <th>Item class</th>
|
|
16697
|
+
* <th>Description</th>
|
|
16698
|
+
* </tr>
|
|
16699
|
+
* <tr>
|
|
16700
|
+
* <td>IPM.Note</td>
|
|
16701
|
+
* <td>New messages and message replies</td>
|
|
16702
|
+
* </tr>
|
|
16703
|
+
* <tr>
|
|
16704
|
+
* <td>IPM.Schedule.Meeting.Request</td>
|
|
16705
|
+
* <td>Meeting requests</td>
|
|
16706
|
+
* </tr>
|
|
16707
|
+
* <tr>
|
|
16708
|
+
* <td>IPM.Schedule.Meeting.Canceled</td>
|
|
16709
|
+
* <td>Meeting cancellations</td>
|
|
16710
|
+
* </tr>
|
|
16711
|
+
* <tr>
|
|
16712
|
+
* <td>IPM.Schedule.Meeting.Resp.Neg</td>
|
|
16713
|
+
* <td>Responses to decline meeting requests</td>
|
|
16714
|
+
* </tr>
|
|
16715
|
+
* <tr>
|
|
16716
|
+
* <td>IPM.Schedule.Meeting.Resp.Pos</td>
|
|
16717
|
+
* <td>Responses to accept meeting requests</td>
|
|
16718
|
+
* </tr>
|
|
16719
|
+
* <tr>
|
|
16720
|
+
* <td>IPM.Schedule.Meeting.Resp.Tent</td>
|
|
16721
|
+
* <td>Responses to tentatively accept meeting requests</td>
|
|
16722
|
+
* </tr>
|
|
16723
|
+
* </table>
|
|
16724
|
+
*
|
|
16725
|
+
* @param options - An object literal that contains one or more of the following properties:-
|
|
16726
|
+
* `asyncContext`: Developers can provide any object they wish to access in the callback function.
|
|
16727
|
+
* @param callback - When the method completes, the function passed in the `callback` parameter is called with a single parameter, `asyncResult`, which is an
|
|
16728
|
+
* `Office.AsyncResult` object. The message class is returned in the `asyncResult.value` property.
|
|
16729
|
+
*
|
|
16730
|
+
* @beta
|
|
16731
|
+
*/
|
|
16732
|
+
getItemClassAsync(options: Office.AsyncContextOptions, callback: (asyncResult: Office.AsyncResult<string>) => void): void;
|
|
16733
|
+
/**
|
|
16734
|
+
* Gets the Exchange Web Services item class of the selected message.
|
|
16735
|
+
*
|
|
16736
|
+
* @remarks
|
|
16737
|
+
* [Api set: Mailbox preview]
|
|
16738
|
+
*
|
|
16739
|
+
* **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/understanding-outlook-add-in-permissions | Minimum permission level}**: **read item**
|
|
16740
|
+
*
|
|
16741
|
+
* **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Compose
|
|
16742
|
+
*
|
|
16743
|
+
* **Important**:
|
|
16744
|
+
*
|
|
16745
|
+
* To preview the `getItemClassAsync` method, you must install Outlook on Windows Version 2402 (Build 17317.20000) or later. Then, join the
|
|
16746
|
+
* {@link https://insider.microsoft365.com/join/Windows | Microsoft 365 Insider program} and select the **Beta Channel** option to access Office beta builds.
|
|
16747
|
+
*
|
|
16748
|
+
* The following table lists the default message classes.
|
|
16749
|
+
*
|
|
16750
|
+
* <table>
|
|
16751
|
+
* <tr>
|
|
16752
|
+
* <th>Item class</th>
|
|
16753
|
+
* <th>Description</th>
|
|
16754
|
+
* </tr>
|
|
16755
|
+
* <tr>
|
|
16756
|
+
* <td>IPM.Note</td>
|
|
16757
|
+
* <td>New messages and message replies</td>
|
|
16758
|
+
* </tr>
|
|
16759
|
+
* <tr>
|
|
16760
|
+
* <td>IPM.Schedule.Meeting.Request</td>
|
|
16761
|
+
* <td>Meeting requests</td>
|
|
16762
|
+
* </tr>
|
|
16763
|
+
* <tr>
|
|
16764
|
+
* <td>IPM.Schedule.Meeting.Canceled</td>
|
|
16765
|
+
* <td>Meeting cancellations</td>
|
|
16766
|
+
* </tr>
|
|
16767
|
+
* <tr>
|
|
16768
|
+
* <td>IPM.Schedule.Meeting.Resp.Neg</td>
|
|
16769
|
+
* <td>Responses to decline meeting requests</td>
|
|
16770
|
+
* </tr>
|
|
16771
|
+
* <tr>
|
|
16772
|
+
* <td>IPM.Schedule.Meeting.Resp.Pos</td>
|
|
16773
|
+
* <td>Responses to accept meeting requests</td>
|
|
16774
|
+
* </tr>
|
|
16775
|
+
* <tr>
|
|
16776
|
+
* <td>IPM.Schedule.Meeting.Resp.Tent</td>
|
|
16777
|
+
* <td>Responses to tentatively accept meeting requests</td>
|
|
16778
|
+
* </tr>
|
|
16779
|
+
* </table>
|
|
16780
|
+
*
|
|
16781
|
+
* @param callback - When the method completes, the function passed in the `callback` parameter is called with a single parameter, `asyncResult`, which is an
|
|
16782
|
+
* `Office.AsyncResult` object. The message class is returned in the `asyncResult.value` property.
|
|
16783
|
+
*
|
|
16784
|
+
* @beta
|
|
16785
|
+
*/
|
|
16786
|
+
getItemClassAsync(callback: (asyncResult: Office.AsyncResult<string>) => void): void;
|
|
16579
16787
|
/**
|
|
16580
16788
|
* Asynchronously gets the ID of a saved item.
|
|
16581
16789
|
*
|
|
@@ -17224,10 +17432,7 @@ declare namespace Office {
|
|
|
17224
17432
|
*/
|
|
17225
17433
|
internetMessageId: string;
|
|
17226
17434
|
/**
|
|
17227
|
-
* Gets the Exchange Web Services item class of the selected
|
|
17228
|
-
*
|
|
17229
|
-
* You can create custom message classes that extends a default message class, for example, a custom appointment message class
|
|
17230
|
-
* `IPM.Appointment.Contoso`.
|
|
17435
|
+
* Gets the Exchange Web Services item class of the selected message.
|
|
17231
17436
|
*
|
|
17232
17437
|
* @remarks
|
|
17233
17438
|
*
|
|
@@ -17235,27 +17440,42 @@ declare namespace Office {
|
|
|
17235
17440
|
*
|
|
17236
17441
|
* **{@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-add-ins-overview#extension-points | Applicable Outlook mode}**: Message Read
|
|
17237
17442
|
*
|
|
17238
|
-
*
|
|
17239
|
-
*
|
|
17443
|
+
* **Important**:
|
|
17444
|
+
*
|
|
17445
|
+
* The following table lists the default item classes for messages.
|
|
17240
17446
|
*
|
|
17241
17447
|
* <table>
|
|
17242
17448
|
* <tr>
|
|
17243
|
-
* <th>
|
|
17449
|
+
* <th>Item class</th>
|
|
17244
17450
|
* <th>Description</th>
|
|
17245
|
-
* <th>Item Class</th>
|
|
17246
17451
|
* </tr>
|
|
17247
17452
|
* <tr>
|
|
17248
|
-
* <td>
|
|
17249
|
-
* <td>
|
|
17250
|
-
*
|
|
17453
|
+
* <td>IPM.Note</td>
|
|
17454
|
+
* <td>New messages and message replies</td>
|
|
17455
|
+
* </tr>
|
|
17456
|
+
* <tr>
|
|
17457
|
+
* <td>IPM.Schedule.Meeting.Request</td>
|
|
17458
|
+
* <td>Meeting requests</td>
|
|
17459
|
+
* </tr>
|
|
17460
|
+
* <tr>
|
|
17461
|
+
* <td>IPM.Schedule.Meeting.Canceled</td>
|
|
17462
|
+
* <td>Meeting cancellations</td>
|
|
17463
|
+
* </tr>
|
|
17464
|
+
* <tr>
|
|
17465
|
+
* <td>IPM.Schedule.Meeting.Resp.Neg</td>
|
|
17466
|
+
* <td>Responses to decline meeting requests</td>
|
|
17467
|
+
* </tr>
|
|
17468
|
+
* <tr>
|
|
17469
|
+
* <td>IPM.Schedule.Meeting.Resp.Pos</td>
|
|
17470
|
+
* <td>Responses to accept meeting requests</td>
|
|
17251
17471
|
* </tr>
|
|
17252
17472
|
* <tr>
|
|
17253
|
-
* <td>
|
|
17254
|
-
* <td>
|
|
17255
|
-
* <td>IPM.Note, IPM.Schedule.Meeting.Request, IPM.Schedule.Meeting.Neg, IPM.Schedule.Meeting.Pos, IPM.Schedule.Meeting.Tent, IPM.Schedule.Meeting.Canceled</td>
|
|
17473
|
+
* <td>IPM.Schedule.Meeting.Resp.Tent</td>
|
|
17474
|
+
* <td>Responses to tentatively accept meeting requests</td>
|
|
17256
17475
|
* </tr>
|
|
17257
17476
|
* </table>
|
|
17258
17477
|
*
|
|
17478
|
+
* You can create custom classes that extend a default item class. For example, `IPM.Note.Contoso`.
|
|
17259
17479
|
*/
|
|
17260
17480
|
itemClass: string;
|
|
17261
17481
|
/**
|
office-js-preview/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@types/office-js-preview",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.462",
|
|
4
4
|
"description": "TypeScript definitions for office-js-preview",
|
|
5
5
|
"homepage": "https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/office-js-preview",
|
|
6
6
|
"license": "MIT",
|
|
@@ -45,7 +45,7 @@
|
|
|
45
45
|
},
|
|
46
46
|
"scripts": {},
|
|
47
47
|
"dependencies": {},
|
|
48
|
-
"typesPublisherContentHash": "
|
|
48
|
+
"typesPublisherContentHash": "54eeb9c6a05e90d9e031c3dc7722618c217a413fa27092d699e4c32bb4d809b8",
|
|
49
49
|
"typeScriptVersion": "4.7",
|
|
50
50
|
"nonNpm": true
|
|
51
51
|
}
|