Table of Contents
- Part 1 - First Bot
- Part 2 - QnA Maker
- Part 3 - Bot State
- Part 4 - Dialogs <-- this section
- Part 5 - LUIS
- Part 6 - Adaptive Cards
- Part 7 - Calling back-end services
Different environments call for different dialog styles. Teams channels are threaded, and a back-and-forth conversation can get confusing so cards are better.
See Design and control conversation flow for more details.
Here's an overview of dialogs in Bot Framework v4. I found this, more succinct article helpful as well.
If you want to add branching and looping to your dialogs, check out Create advanced conversation flow using branches and loops.
Prompt options are detailed here (.NET, Node).
The Multi-turn prompt sample shows a sequence of several prompt dialogs called by a waterfall dialog.
Notice that the bot saves state at the end of each turn.
Walk through the Consuling Bot dialogs.
CHALLENGE (after class)
- The current sample resolves the project and looks up its information in the Add to Project dialog, but not the Bill to Project dialog. Resolve the project in both dialogs.
-
https://github.com/BobGerman/Bots: Bob's repo, containing samples specific to this workshop, and these notes
-
https://github.com/microsoft/BotBuilder-Samples: Great samples for Bot Framework - now including Teams examples!
-
https://github.com/OfficeDev/msteams-samples-outgoing-webhook-nodejs: Outgoing webhook - the simplest bot for Teams
-
https://github.com/OfficeDev/msteams-sample-contoso-hr-talent-app.git: Great Teams bot/app sample showing an HR recruiting application