Skip to content

Latest commit

 

History

History
122 lines (82 loc) · 6.22 KB

Readme.md

File metadata and controls

122 lines (82 loc) · 6.22 KB
Raw

Tab With AdpativeCard Flow

This App talks about the Teams tab which displays Adaptive card with Node JS. For reference please check Build tabs with Adaptive Cards

This bot has been created using Bot Framework v4, it shows how to create a simple bot that accepts Adaptive Cards V1.4 to render in Teams tab.

This feature shown in this sample is in Public Developer Preview and is supported in desktop and mobile.

Key features

  • Tab showing Adaptive card with action controls

Home Page

  • Task module

Task Module

  • Sign in card

Sign in Card

  • Sign in popup

Sing in popup

  • Sign out card

Sign out Card

Prerequisites

  1. Office 365 tenant. You can get a free tenant for development use by signing up for the Office 365 Developer Program.

  2. To test locally, NodeJS must be installed on your development machine (version 10.14 or higher).

    # determine node version
node --version

  3. To test locally, you'll need Ngrok installed on your development machine. Make sure you've downloaded and installed Ngrok on your local machine. ngrok will tunnel requests from the Internet to your local computer and terminate the SSL connection from Teams.

NOTE: The free ngrok plan will generate a new URL every time you run it, which requires you to update your Azure AD registration, the Teams app manifest, and the project configuration. A paid account with a permanent ngrok URL is recommended.

To try this sample

  • Register Azure AD applications

    • Register your bot using bot channel registration in Azure AD portal, following the instructions here.
    • For authentication flow please check Add authentication to bot

  • Clone the repository

    git clone https://github.com/OfficeDev/Microsoft-Teams-Samples.git

  • In a console, navigate to samples/tab-adaptive-cards/nodejs

    cd samples/tab-adaptive-cards/nodejs

  • Run ngrok - point to port 3978

    ngrok http -host-header=localhost 3978

  • Update the .env configuration for the bot to use the MicrosoftAppId (Microsoft App Id) and MicrosoftAppPassword (App Password) from the Bot Framework registration. Also update BaseUrl according to your code runtime environment and ConnectionName with Bot Channel Registration connection name.

NOTE: the App Password is referred to as the client secret in the azure portal and you can always create a new client secret anytime.

  • Install modules & Run the NodeJS Server

    • Server will run on PORT: 3978
    • Open a terminal and navigate to project root directory
    npm run server

    This command is equivalent to: npm install > npm start

  • This step is specific to Teams.

    • Edit the manifest.json contained in the appPackage folder to replace your Microsoft App Id (that was created when you registered your bot earlier) everywhere you see the place holder string <<YOUR-MICROSOFT-APP-ID>> (depending on the scenario the Microsoft App Id may occur multiple times in the manifest.json) also update the <<DOMAIN-NAME>> with the ngrok URL
    • Zip up the contents of the appPackage folder to create a manifest.zip
    • Upload the manifest.zip to Teams (in the Apps view click "Upload a custom app")
      • Go to Microsoft Teams. From the lower left corner, select Apps
      • From the lower left corner, choose Upload a custom App
      • Go to your project directory, the ./appPackage folder, select the zip folder, and choose Open.
      • Select Add in the pop-up dialog box. Your tab is uploaded to Teams.

Interacting with the tab in Teams

You can use this tab by following the below steps:

  • In the navigation bar located at the far left in Teams, select the ellipses ●●● and choose your app from the list.

Deploy the bot to Azure

To learn more about deploying a bot to Azure, see Deploy your bot to Azure for a complete list of deployment instructions.

Further reading