Name		Name	Last commit message	Last commit date
parent directory ..
Wiki		Wiki
appPackage		appPackage
server		server
.env		.env
.eslintignore		.eslintignore
.eslintrc.js		.eslintrc.js
.gitignore		.gitignore
Readme.md		Readme.md
package.json		package.json

Readme.md

Sequential Workflows in adaptive card

This App talks about the Teams Bot User Specific Views and Sequential Workflows in adaptive card with Node JS

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

This is a sample app that provides an experience of managing incidents. This sample makes use of Teams platform capabilities like Universal Bots with below mentioned capabilities. User Specific Views Sequential Workflows Up to date cards

Key features

Incident Creation
- Choose Category
- Choose Sub Category
- Create Incident
- Edit/ Approve/ Reject Incident
List Incidents

Prerequisites

Office 365 tenant. You can get a free tenant for development use by signing up for the Office 365 Developer Program.
To test locally, NodeJS must be installed on your development machine (version 10.14 or higher).
```
# determine node version
node --version
```
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/bot-sequential-flow-adaptive-cards/nodejs
```
cd samples/bot-sequential-flow-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.

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 teamsAppManifest 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 teamsAppManifest folder to create a manifest.zip
- Upload the manifest.zip to Teams (in the Apps view click "Upload a custom app")