Skip to content

Latest commit

 

History

History
138 lines (98 loc) · 6.13 KB

File metadata and controls

138 lines (98 loc) · 6.13 KB
page_type description products languages extensions contentType createdDate
sample
Microsoft Teams tab sample app for demonstrating tab in stage view
office-teams
office
office-365
nodejs
samples
06-10-2021 01:48:56

Stage View

This App talks about the Teams tab in stage view with Nodejs. For reference please check Tabs link unfurling and Stage View

Key features

  • Welcome message with feature explanation.

Welcome Message

  • Adaptive Card with actions.

Card Actions

  • Opening stage view from Adaptive Card Action.

Stage View

  • Opening stage view from Adaptive card via deep link.

Stage View Deep Link

  • Tab with execute deep link action to open stage view.

Tab View

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.
  • Clone the repository

    git clone https://github.com/OfficeDev/Microsoft-Teams-Samples.git
  • In a console, navigate to samples/tab-stage-view/nodejs

    cd samples/tab-stage-view/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.

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 in the appPackage folder and replace the following details:

    • <<MANIFEST-ID>> with some unique GUID
    • <<BASE-URL>> with your application's base url, e.g. https://1234.ngrok.io
    • <<YOUR-MICROSOFT-APP-ID>> with the MicrosoftAppId.
    • <<DOMAIN-NAME>> with the ngrok URL or app hosted base 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 bot 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