{"id":17,"date":"2022-01-18T18:45:52","date_gmt":"2022-01-18T18:45:52","guid":{"rendered":"https:\/\/blogs.oregonstate.edu\/coucoulr\/?p=17"},"modified":"2022-01-18T18:45:52","modified_gmt":"2022-01-18T18:45:52","slug":"creating-a-microsoft-teams-bot-part-3-bot-operations","status":"publish","type":"post","link":"https:\/\/blogs.oregonstate.edu\/coucoulr\/2022\/01\/18\/creating-a-microsoft-teams-bot-part-3-bot-operations\/","title":{"rendered":"Creating a Microsoft Teams Bot – Part 3: Bot Operations"},"content":{"rendered":"\n
This is the third 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
Previously, the architecture of a Microsoft Teams bot was inspected and found to be a REST API endpoint wrapping a TeamsBot<\/code> object. In this post, we\u2019ll explore the class that object is an instance of and how it handles commands.<\/p>\n\n\n\n
Inspecting the boilerplate code, the TeamsBot<\/code> class is defined in bot\/teamsBot.ts<\/code>. The example bot comes with two built-in commands: \u201cwelcome\u201d and \u201clearn\u201d; searching the source file for these words reveals that the handlers are defined in the constructor, which looks something like:<\/p>\n\n\n\n
By inspection, it appears that the onMessage<\/code> event handler fires when the bot receives a message and provides a context<\/code> object, describing the received event and the contextual state, and a next<\/code> function which the handler is expected to pass control to when it\u2019s finished. In this way, the message handler is much like standard middleware in common backend frameworks. The true meat of this function is the switch statement on the variable txt<\/code>, which contains the sanitized value of context.activity.text<\/code>, the body of the received message.<\/p>\n\n\n\n
Using the existing cases as a guide, we can change the body of the switch statement to handle the command we want. The context.sendActivity<\/code> method appears to be what prompts the bot to send a reply, so we can use that, in conjunction with txt<\/code>, to create an echo bot.<\/p>\n\n\n\n
switch (txt) {\r\n case \"hello\": {\r\n await context.sendActivity(`Hi there! You sent \"${txt}\".`);\r\n break;\r\n }\r\n}\r<\/pre>\n\n\n\n
The result:<\/p>\n\n\n\n<\/figure>\n\n\n\n
It works!<\/p>\n\n\n\n
Next time, we\u2019ll dig into adding commands into the command menu and implementing more complex logic in commands.<\/p>\n","protected":false},"excerpt":{"rendered":"
This is the third post in a series of posts documenting the creation of BeaverHours, a Microsoft Teams bot which handles office hours queueing. Previously, the architecture of a Microsoft Teams bot was inspected and found to be a REST API endpoint wrapping a TeamsBot object. In this post, we\u2019ll explore the class that object … <\/p>\n
![\"\"](\"https:\/\/osu-wams-blogs-uploads.s3.amazonaws.com\/blogs.dir\/5205\/files\/2022\/01\/Screenshot-2022-01-18-103821.png\")
<\/figure>\n\n\n\n