An example scenario is assigning a task or ticket to a fellow team member and then notifying that team member.
Ms bot framework chatbot examples update#
Often you’ll want to notify the end user whenever an update or a user action occurs in a tab. In personal chats, because tabs are static and installed with the app, you can always assume their existence and thus construct deep links accordingly. When your bot constructs a message, it can target the entityId associated with that tab. For example, flag on your backend indicating the tab is created in the channel. When the tab is created, you store some simple state. For this to happen, you’ll need to encode your bot’s message to include a deep link URL, either through markup or as the target of the openUrl action.ĭeep links rely on an entityId, which is an opaque value that maps to a unique entity in your system. For example, consider navigating the user to the tab when the user selects the card from your bot. You want to use tabs to show more content that can fit inside of a card, or provide a way to complete complex form-filling tasks using the tab canvas. You can then associate the Teams user ID with the user’s credentials from your own identity service.Ĭonstructing deep links to tabs in messages from your bot This flow works best if your identity provider implements the OAuth 2.0 protocol. You can implement via the sign in action, which typically signs in the user via an OAuth flow. In general, the recommended approach is to sign the user in with the bot using the same identity system used to provide authentication for the tab content. So how do you associate these two identities? The challenge is that the user ID in your system is likely different from the Microsoft Teams user ID. Typically, you’ll want to show content in the tab that is specific to the viewing user. Suppose you also have a bot that can interact with the user. Suppose your tab application uses a proprietary ID system to secure its content. Associating user identities across bot and tab This section describes best practices and common patterns for using tabs and bots together. If you are looking for current documentation version 4.6 or later of the SDK, see the conversational bots section.īots and tabs work together, and are often combined into a single back-end service.
This article is based on the v3 Bot Framework SDK.
0 kommentar(er)
