![]() ![]() These examples can also be found in the image down below. For example, to start one of the other flows, or to call upon an Azure Function to connect to the database. In the last case, you can define follow-up actions based on the answer chosen by the user. For instance, that the chatbot simply sends a specific sentence, or that the chatbot asks the user to choose an answer for a question. In the flow you can create different commands your chatbot executes. These flows can be found in the upper left corner in the picture down below. The Bot Framework Composer works as follows: you can define different flows and model a chatbot conversation inside this flow based on user input and if/else statements. Once this worked out, we proceeded building our own chatbot. The hardest part was to get the composer configured, since to get it working, you need a lot of Azure services. This tool is a very user-friendly way to create a chatbot quite easily. Our Microsoft experts advised us to build the chatbot in Azure Bot Framework Composer. To start off this hackathon project, we focused on creating the first part of our solution: a chatbot. The supporting elements or elements which were not implemented yet, are not further discussed in this article. During the hackathon we mostly focused on the modules indicated by the red squares in the picture. ![]() Let’s now zoom in on these different modules in the architecture. Both the Azure Functions and Cosmos DB are created and set up by code in Visual Studio Code. The bot is connected to the database with Azure Functions, which contain queries to save and search the data collected by the bot. Lastly, our chatbot will be made available for our colleagues via either Microsoft Teams or Slack. Furthermore, the chatbot that we created was built in Azure Bot Framework Composer and will eventually be deployed to Azure Bot runtime (for now, to test, we simply use the Emulator within Azure Bot Framework Composer). The platform we used to store our project was GitHub. In this article we would like to focus more on the content of our project: what exactly did we achieve? The objective of our project was:īuilding a smart skill matrix which will help management and teams to keep track of the available and needed skills on personal and team levels to deliver the work that is coming their way.īelow, you find the architectural overview of our solution. This previous blogpost is a great read if you would like to know more about our trip and the great time we had. As you might have read in our previous article, the Techlab team participated in the E.ON and Microsoft Hackathon at the German headquarters of Microsoft in Munich. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |