nodejs

page_type	description	products	languages	extensions	urlFragment
sample	Demonstrating feature where user can checkin with current location and view all previous checkins.	office-teams office office-365	nodejs	contentType createdDate samples 11-11-2021 23:30:17	officedev-microsoft-teams-samples-app-checkin-location-nodejs

Get Checkin info of user

This sample shows feature where user can checkin with current location and view all previous checkins.

Currently, Microsoft Teams support for get geolocation capability is only available for mobile clients

Prerequisites

• Microsoft Teams is installed and you have an account (not a guest account)
• NodeJS
• ngrok or equivalent tunneling solution
• M365 developer account or access to a Teams account with the appropriate permissions to install an app.

To try this sample

Note these instructions are for running the sample on your local machine, the tunnelling solution is required because the Teams service needs to call into the bot.

1. Setup for Bot

In Azure portal, create a Azure Bot resource.

• Ensure that you've enabled the Teams Channel
• While registering the bot, use https://<your_ngrok_url>/api/messages as the messaging endpoint. NOTE: When you create your bot you will create an App ID and App password - make sure you keep these for later.

2. Run your bot sample

1. Clone the repository

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

2. In a terminal, navigate to samples/app-checkin-location/nodejs

3. Install modules

   npm install

4. Run ngrok - point to port 3978

   ngrok http -host-header=rewrite 3978

5. Update the .env configuration for the bot to use the MicrosoftAppId and MicrosoftAppPassword, BaseUrl with application base url. For e.g., your ngrok url. (Note the MicrosoftAppId is the AppId created in step 1 (Setup for Bot), the MicrosoftAppPassword is referred to as the "client secret" in step 1 (Setup for Bot) and you can always create a new client secret anytime.)

6. Run your app

   npm start

• Manually update the manifest.json
  • Edit the manifest.json contained in the appPackage/ folder to replace with your MicrosoftAppId (that was created in step1.1 and is the same value of MicrosoftAppId in .env file) everywhere you see the place holder string {MicrosoftAppId} (depending on the scenario the Microsoft App Id may occur multiple times in the manifest.json)
  • Zip up the contents of the appPackage/ folder to create a manifest.zip
  • Upload the manifest.zip to Teams (in the left-bottom Apps view, click "Upload a custom app")

Features of this sample

• Card with actions check in.

• Geo Location of user.

• User details.

• viewcheckindetails of user.