{"id":28,"date":"2022-01-27T19:52:42","date_gmt":"2022-01-27T19:52:42","guid":{"rendered":"https:\/\/blogs.oregonstate.edu\/coucoulr\/?p=28"},"modified":"2022-01-27T19:52:42","modified_gmt":"2022-01-27T19:52:42","slug":"creating-a-microsoft-teams-bot-part-4-bot-commands","status":"publish","type":"post","link":"https:\/\/blogs.oregonstate.edu\/coucoulr\/2022\/01\/27\/creating-a-microsoft-teams-bot-part-4-bot-commands\/","title":{"rendered":"Creating a Microsoft Teams Bot – Part 4: Bot Commands"},"content":{"rendered":"\n
This is the fourth post in a series of posts documenting the creation of BeaverHours, a Microsoft Teams bot which handles office hours queueing. <\/p>\n\n\n\n
In the last installment, we learned how the bot processes input with its onMessage<\/code> event handler. Now, we’ll learn how to populate the bot’s command menu to offer suggestions to the user about what commands the bot will process. The command menu, seen in the screenshot below, offers an intuitive way to signal to the user what the bot can be expected to do.<\/p>\n\n\n\n<\/figure>\n\n\n\n
Searching the contents of the code reveals two places where this particular command menu is defined: templates\/appPackage\/manifest.local.template.json<\/code> and templates\/appPackage\/manifest.remote.template.json<\/code>. Intuition tells us (and the docs confirm) that these are configuration files for local and remote deployment; that is, local behavior will be defined by manifest.local.template.json<\/code> and remote behavior will be defined by manifest.remote.template.json<\/code>. In these files, the key property that is of interest to us is the bots array, which holds bot objects which take the form:<\/p>\n\n\n\n
Clearly, commandLists.commands<\/code> is the property of interest here. It takes the form of an array of { title, description }<\/code> objects. Let’s try replacing the commands here with the hello<\/code> command we wrote in the previous post.<\/p>\n\n\n\n
It works! We now have a way to signal to the user what commands are available in the bot.<\/p>\n\n\n\n<\/figure>\n\n\n\n
Using the command menu along with the onMessage<\/code> handler, we were able to define bot behavior and advertise that behavior to the user. In the next installment, we’ll implement some in-memory structures to preserve state in the bot between messages.<\/p>\n","protected":false},"excerpt":{"rendered":"
This is the fourth post in a series of posts documenting the creation of BeaverHours, a Microsoft Teams bot which handles office hours queueing. In the last installment, we learned how the bot processes input with its onMessage event handler. Now, we’ll learn how to populate the bot’s command menu to offer suggestions to the … <\/p>\n
![\"\"](\"https:\/\/osu-wams-blogs-uploads.s3.amazonaws.com\/blogs.dir\/5205\/files\/2022\/01\/image-5.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/osu-wams-blogs-uploads.s3.amazonaws.com\/blogs.dir\/5205\/files\/2022\/01\/image-7.png\")
<\/figure>\n\n\n\n