Updates from: 06/01/2021 03:28:55
Service Microsoft Docs article Related commit history on GitHub Change details
platform First Message Extension https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/get-started/first-message-extension.md
Deployment involves provisioning resources on an active Azure subscription and d
</details>
+## Add a configuration page to your messaging extension
++
+## Code sample
+
+The Teams Search Auth Config for sample projects on GitHub, demonstrate how to create messaging extensions that include a configuration page and [Bot Service authentication](https://github.com/microsoft/BotBuilder-Samples#teams-samples). The samples also demonstrate how to create message extensions that accept search requests and return the results after the user has signed in.
+
+| **Sample name** | **Description** | **.NET** | **Node.js** | **Python** |
+|--|--|-|--|--|
+| Bot builder | To create messaging extensions. | [View](https://github.com/microsoft/BotBuilder-Samples/tree/master/samples/csharp_dotnetcore/52.teams-messaging-extensions-search-auth-config) | [View](https://github.com/microsoft/BotBuilder-Samples/tree/master/samples/javascript_nodejs/52.teams-messaging-extensions-search-auth-config) | [View]( https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/python/50.teams-messaging-extension-search) |
+
+## Additional code sample
+
+> [!div class="nextstepaction"]
+> [View more Bot Framework Samples on GitHub](https://github.com/OfficeDev/microsoft-teams-samples#messaging-extensions-samples-using-the-v4-sdk)
+ ## Next steps Learn about other methods for creating Teams apps:
platform Respond To Task Module Submit https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/messaging-extensions/how-to/action-commands/respond-to-task-module-submit.md
You have the following options to respond:
* [Card response](#respond-with-a-card-inserted-into-the-compose-message-area): You can respond with a card that the user can interact with or insert into a message. * [Adaptive Card from bot](#bot-response-with-adaptive-card): Insert an Adaptive Card directly into the conversation. * [Request the user to authenticate](~/messaging-extensions/how-to/add-authentication.md).
-* [Request the user to provide additional configuration](~/messaging-extensions/how-to/add-configuration-page.md).
+* [Request the user to provide additional configuration]~/get-started/first-message-extension.md).
For authentication or configuration, after the user completes the process, the original invoke is resent to your web service. The following table shows which types of responses are available based on the invoke location `commandContext` of the messaging extension:
platform Add Configuration Page https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/messaging-extensions/how-to/add-configuration-page.md
- Title: Add a configuration page to your messaging extension-
-description: How to add a configuration page to a messaging extension
-localization_priority: Normal
---
-# Add a configuration page to your messaging extension
--
-## Code sample
-
-The Teams Search Auth Config for sample projects on GitHub, demonstrate how to create messaging extensions that include a configuration page and Bot Service authentication. The samples also demonstrate how to create message extensions that accept search requests and return the results after the user has signed in.
-
-| **Sample name** | **Description** | **.NET** | **Node.js** | **Python** |
-|--|--|-|--|
-| Bot builder | To create messaging extensions. | [View](https://github.com/microsoft/BotBuilder-Samples/tree/master/samples/csharp_dotnetcore/52.teams-messaging-extensions-search-auth-config) | [View](https://github.com/microsoft/BotBuilder-Samples/tree/master/samples/javascript_nodejs/52.teams-messaging-extensions-search-auth-config) | [View]( https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/python/50.teams-messaging-extension-search) |
-
-## Additional code sample
-
-> [!div class="nextstepaction"]
-> [View more Bot Framework Samples on GitHub](https://github.com/microsoft/BotBuilder-Samples)
platform Respond To Search https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/messaging-extensions/how-to/search-commands/respond-to-search.md
The default query has the same structure as any regular user query, with the `na
## See also
-[Add configuration to a messaging extension](~/messaging-extensions/how-to/add-configuration-page.md)
-
+[Add configuration to a messaging extension](~/get-started/first-message-extension.md)
+ ## Next step > [!div class="nextstepaction"]
platform Manifest Schema https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/resources/schema/manifest-schema.md
keywords: teams manifest schema
# Reference: Manifest schema for Microsoft Teams The Teams manifest describes how the app integrates into the Microsoft Teams product. Your manifest must conform to the schema hosted at [`https://developer.microsoft.com/json-schemas/teams/v1.10/MicrosoftTeams.schema.json`]( https://developer.microsoft.com/json-schemas/teams/v1.10/MicrosoftTeams.schema.json). Previous versions 1.0, 1.1,..., 1.6, and so on are also supported (using "v1.x" in the URL).
+For more information on the changes made in each version, see [manifest change log](https://github.com/OfficeDev/microsoft-teams-app-schema/releases).
The following schema sample shows all extensibility options:
platform Conversational Tabs https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/tabs/how-to/conversational-tabs.md
+
+ Title: Create conversational tabs
+
+description: Create conversational sub-entity chat for your channel tabs
+keywords: teams tabs channel configurable
+++
+# Create conversational tabs
+
+Conversational sub-entities provides a way to allow users to have conversations about sub-entities in your tab, such as specific task, patient, and sales opportunity, instead of discussing the entire tab, also known as entity. A traditional channel or configurable tab allows the user to have a conversation about a tab, but the user may want a more focused conversation. The requirement for a more focused conversation can arise either, if there is too much content to have a centralized discussion or the content changed over time, making the conversation irrelevant to the content being shown. Conversational sub-entities provides a much more focused conversation experience for dynamic tabs.
+
+Conversational sub-entities are only supported in channels. However, they can be used from a personal or static tab to create or continue conversations in tabs that are *already* pinned to a channel. The static tab is useful if you wish to provide one location for a user to view and access conversations happening across multiple channels.
+
+## Prerequisites
+
+In order to support conversational sub-entities, your tab web application must have the ability to store a mapping between sub-entities Γåö conversations in a backend database. We will provide you with the `conversationId`, but it will be your responsibility to store that `conversationId` and return it to Teams in order for users to continue the conversation.
+
+## Start a new conversation
+
+To start a new conversation, you use the `openConversation()` function. Starting and continuing a conversation are all handled by this method, however, the inputs to the function change depending on which action you want to take. From the users perspective, this opens the conversation panel to the right of the screen, either to initiate a conversation or continue a conversation.
+
+``` javascript
+microsoftTeams.conversations.openConversation(openConversationRequest);
+```
+
+**openConversation** takes the following inputs to start a conversation in a channel:
+
+* **subEntityId**: This is the ID of your specific sub-entity. For example, task-123.
+* **entityId**: This is the ID of the tab instance when it was created. The ID is important to refer back to the same tab instance.
+* **channelId**: This is the channel in which the tab instance resides.
+ > [!NOTE]
+ > The **channelId** is optional for channel tabs. However, it is recommended if you wish to keep your implementation across channel and static tabs the same.
+* **title**: This is the title that is shown to the user in the chat panel.
+
+Most of these values can also be retrieved from the `getContext` API.
+
+```javascript
+microsoftTeams.conversations.openConversation({ΓÇ£subEntityIdΓÇ¥:ΓÇ¥task-1ΓÇ¥, ΓÇ£entityIdΓÇ¥: ΓÇ£tabInstanceId-1ΓÇ¥, ΓÇ£channelIdΓÇ¥: ΓÇ¥19:baa6e71f65b948d189bf5c892baa8e5a@thread.skypeΓÇ¥, ΓÇ£titleΓÇ¥: "Task TitleΓÇ¥});
+```
+
+This will open the conversation panel.
+
+![Conversationl Sub Entities - Start Conversation](~/assets/images/tabs/conversational-subentities/start-conversation.png)
+
+If the user starts a conversation, itΓÇÖs important to listen for the callback of that event in order to retrieve and save the **conversationId**:
+
+```javascript
+microsoftTeams.conversations.onStartConversation = (conversationResponse) => {
+ // console.log(conversationReponse.conversationId)
+};
+```
+
+The `conversationReponse` object contains information related to the conversation that was just started. We recommend you save all the properties of this response object for reuse later.
+
+## Continue a conversation
+
+After a conversation starts, subsequent calls to `openConversation()` requires that you also provide the same inputs as in [Starting a new channel tab conversation](#Starting a new channel tab conversation), but also include the **conversationId**. The conversation panel opens for the user with the appropriate conversation in view. Users are able to see new or incoming messages in real-time.
+
+![Conversationl Sub Entities - Continue Conversation](~/assets/images/tabs/conversational-subentities/continue-conversation.png)
+
+## Enhance a conversation
+
+Finally, itΓÇÖs important that your tab consumes [deeplinks to your sub-entity](~/concepts/build-and-test/deep-links.md). For example, user clicking the tab chiclet deeplink from the channel conversation. The expected behavior is for you to receive the deeplink, open that sub-entity, and then open the conversation panel for that specific sub-entity.
+
+To support conversational sub-entities from your personal or static tab, you do not have to change anything about your implementation. We only support starting or continuing conversations from channel tabs that are already pinned. Supporting static tabs allow you to provide a single location for your users to interact with all your sub-entities. It is, however, important that you save the `subEntityId`, `entityId`, and `channelId` when your tab is originally created in a channel in order for you to have the right properties when opening the conversation view in a static tab.
+
+## Close a conversation
+
+You can manually close the conversation view by calling the `closeConversation()` function.
+
+```javascript
+microsoftTeams.conversations.closeConversation();
+```
+
+You can also listen for an event when the conversation view is closed by a user.
+
+```javascript
+microsoftTeams.conversations.onCloseConversation = (conversationResponse) => {
+ // console.log(conversationResponse)
+};
+```
platform Whats New https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/whats-new.md
Microsoft Teams platform features that are available to all app developers.
| **Date** | **Notes** | **Changed topics** | | -- | | |
-|05/24/2021|Updated Teams app design guidelines with mobile patterns and more.|[Designing your Teams app](~/concepts/design/design-teams-app-overview.md)
-|05/13/2021|Added information on mConnect and Skooler.|[Moodle learning management system](resources/moodle-overview.md)
+|05/31/2021| Conversational tabs | [Start and continue conversations about content in your tabs](~/tabs/how-to/conversational-tabs.md) |
+|05/24/2021| Updated Teams app design guidelines with mobile patterns and more.|[Designing your Teams app](~/concepts/design/design-teams-app-overview.md)
+|05/13/2021| Added information on mConnect and Skooler.|[Moodle learning management system](resources/moodle-overview.md)
|05/10/2021| Manifest v1.10 is released.|[Manifest schema](resources/schem) | |05/10/2021| New app customization feature.| [Enable orgs to customize your app](concepts/design/enable-app-customization.md) | |05/07/2021| Deep links for audio and video calls in chat. |[Deep links](concepts/build-and-test/deep-links.md#deep-linking-to-an-audio-or-audio-video-call) |
Microsoft Teams platform features that are available to all app developers.
|09/22/2020|New information for getting started with Teams development.|[Build your first Teams app overview](build-your-first-app/build-first-app-overview.md)| |09/18/2020|Support for in-meeting Teams apps (Release Preview).|[Create apps for Teams meetings](apps-in-teams-meetings/create-apps-for-teams-meetings.md) and [Apps in Teams meetings](apps-in-teams-meetings/teams-apps-in-meetings.md)| |08/19/2020|Import Teams messages with Microsoft Graph.|[Import third-party platform messages to Teams using Microsoft Graph](graph-api/import-messages/import-external-messages-to-teams.md)
-| 08/12/2020 |Adaptive Cards support in incoming webhook moved to GA.|[Send adaptive cards using an incoming webhook](~/webhooks-and-connectors/how-to/connectors-using.md#send-adaptive-cards-using-an-incoming-webhook) |
+|08/12/2020 |Adaptive Cards support in incoming webhook moved to GA.|[Send adaptive cards using an incoming webhook](~/webhooks-and-connectors/how-to/connectors-using.md#send-adaptive-cards-using-an-incoming-webhook) |
|08/10/2020|Get started building Teams apps with the Visual Studio Toolkit.|[Build apps with the Microsoft Teams Toolkit and Visual Studio Code](toolkit/visual-studio-overview.md) | |08/06/2020|Support for Tabs SSO authentication.|[Develop an SSO Microsoft Teams Tab](tabs/how-to/authentication/auth-aad-sso.md#develop-an-sso-microsoft-teams-tab) | |07/27/2020 | Graph proactive bots and messages (Public Preview).|[Enable proactive bot installation and proactive messaging in Teams with Microsoft Graph](graph-api/proactive-bots-and-messages/graph-proactive-bots-and-messages.md)|
-| 07/22/2020 |Mobile device capability updates.|[Request device permissions for your Microsoft Teams tab](concepts/device-capabilities/native-device-permissions.md) |
+|07/22/2020 |Mobile device capability updates.|[Request device permissions for your Microsoft Teams tab](concepts/device-capabilities/native-device-permissions.md) |
|07/20/2020|Teams App Validation Tool for AppSource submissions.|[Teams App Validation Tool](concepts/deploy-and-publish/appsource/prepare/submission-checklist.md) |07/15/2020|Create a virtual assistant for Teams.|[Virtual Assistant for Microsoft Teams](samples/virtual-assistant.md)| |07/14/2020|Surfacing a native loading indicator documentation.|[Showing a native loading indicator](tabs/how-to/create-tab-pages/content-page.md#show-a-native-loading-indicator)
Microsoft Teams platform features that are available to all app developers.
|06/05/2020| Manifest schema updated to version 1.7.| [Reference: Manifest schema for Microsoft Teams](resources/schem)| |05/18/2020|Integrate Power Virtual Agents with Teams.|[Integrate a Power Virtual Agents chatbot with Microsoft Teams](bots/how-to/add-power-virtual-agents-bot-to-teams.md)| |04/01/2020|Integrate WFM systems with Shifts Connector for Teams.|[Microsoft Teams Shifts WFM connectors](samples/shifts-wfm-connectors.md)
-| 03/24/2020 | Added support for retrieving a single member of a conversation, and additional support for retrieving paged members. | [Get Teams context for your bot](~/bots/how-to/get-teams-context.md) |
+|03/24/2020 | Added support for retrieving a single member of a conversation, and additional support for retrieving paged members. | [Get Teams context for your bot](~/bots/how-to/get-teams-context.md) |
<br>