page_type | description | products | languages | extensions | contentType | createdDate | ||||
---|---|---|---|---|---|---|---|---|---|---|
sample |
This sample shows a feature where user can schedule a task from messaging extension action and get a reminder card at a scheduled time. |
|
|
samples |
24-11-2021 13:10:00 |
This sample shows a feature where user can schedule a task from messaging extension action and get a reminder card at a scheduled time.
- Personal scope scenario
Select
...
over message to get actioncreate-reminder
for scheduling task.
Task module to schedule a task.
Reminder card of task at scheduled date and time.
- 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.
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.
In Azure portal, create a Azure Bot resource.
-
Clone the repository
git clone https://github.com/OfficeDev/Microsoft-Teams-Samples.git
- Ensure that you've enabled the Teams Channel
-
In the folder where repository is cloned navigate to
samples/bot-task-reminder/nodejs
-
Install node modules
Inside node js folder, open your local terminal and run the below command to install node modules. You can do the same in Visual studio code terminal by opening the project in Visual studio code
npm install
-
Run ngrok - point to port 3978
ngrok http -host-header=rewrite 3978
-
Update the
.env
configuration file in your project folder for the bot to use theMicrosoftAppId
andMicrosoftAppPassword
,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.) -
Run your app
npm start
-
Manually update the manifest.json
- Edit the
manifest.json
contained in theappPackage/
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 themanifest.json
) - Zip up the contents of the
appPackage/
folder to create amanifest.zip
- Upload the
manifest.zip
to Teams (in the left-bottom Apps view, click "Upload a custom app")
- Edit the
- Personal scope scenario
Select
...
over message to get actioncreate-reminder
for scheduling task.
Task module to schedule a task.
Reminder card of task at scheduled date and time.
- Team scope scenario Navigate to team where the app is installed
Select ...
over message to get action create-reminder
for scheduling task.
Task module to schedule a task.
Reminder card of task at scheduled date and time.