Skip to main content

Microsoft Bot Framework - Introduction

Microsoft Bot framework is a building area of Conversational AI bots.



Microsoft introduced many services as independent and coupled inside Azure. Some of then services like QnA, Language Understanding(LUIS), Vision, Speech. 

These API are trending powerful nowadays and becoming easier to develop AI bots. 

It having own life cycle model. After development process we can do testing in local emulator and publish service through azure app service. 

To connect this bots, we can use channels that provides in bot registration under azure service. All you needed is visual Studio 2019 & Azure Subscription. Then You can kick start your bot development.

Life cycle:

Microsoft Bot Framework Life Cycle
Bot Framework Life Cycle

Dialogs

Bots
Cards
Bot Channel Registration
DirectLine



Labels:

Comments

Post a Comment

Popular posts from this blog

UiPath : Orchestrator Basics

UiPath : Orchestrator Basics By Dinesh Baskaran 1. What is Orchestrator? 2. What is Tenant in Orchestrator? 3. What is Jobs in Orchestrator? 4. What is Robots in Orchestrator? 5. What is Environment in Orchestrator? 6. What is Machines in Orchestrator? 7. What is Processes & Packages in Orchestrator? 8. What is Schedules in Orchestrator? 9. What is Assets in Orchestrator ? 10. What is Queues in Orchestrator ? 1. What is Orchestrator? It is the managing body with whole control to the System. One Admin can manage everything through Orchestrator. Also we can add roles to control and monitor the system. In UiPath, generally orchestrator handles the Robots, Environment, Processes, Schedules, Assets and Queues. UiPath Orchestrator is a User Interaction web page that need to be hosted in a webserver(IIS). One should have access to the tenants, then login and manage all the setup. UiPath Admin is the highest role can play with all over setup. 2. What is Tenant in Orche...
Post a Comment
Read more

UiPath : Publish your package from Production Running Machine

UiPath : Publish your package from Production Running Machine Prerequisite : 1. Have to analyse the Machine Schedule first. 2. If you dont know the schedule, Search the Machine name in Jobs. So that you can see Source(i.e., Schedule Name which responsible for the trigger) 3. Then disable that schedule. If more than one machine allocated in the same schedule then remove the particular Machine from the schedule and update. 4. And you have to check whether the machine is already running or not. You can do this in Jobs 5. If the machine already running, do "Stop" 6. Now you are ready for doing changes in production machine itself. Steps to Publish package from Production Machine: 1. Open the machine with the Process ID which ROBOT already configured. 2. Then take the latest package which is published in Orchestrator. 3. If you are unable to find the latest package, then you have to find it via Packages. 4. Check the same version in the Machine folder "C:...
Post a Comment
Read more