Forum Widgets
Latest Discussions
Use Video Cards in Health Bot using Web Chat
There are several ways to display video content inside a Health Bot conversation using WebChat client. One way is to use Adaptive Cards. But if you don't need all the layout features of an adaptive card, you can also use a much simpler "VideoCard" attachment as part of a prompt or a statement in your Health Bot scenario flow. Based on the video source url, it will host YouTube or Vimeo video clips inside an iframe in the WebChat widget. Create a prompt or a statement step, click on adding a "Dynamic Card" and paste code snippet such as this: (function(){ return [ { contentType: "application/vnd.microsoft.card.video", content: { media: [{ url: "https://youtu.be/rwe2291YT8Rxw?si=t5m40pOGou5XdFqm" }], } } ] })() This will generate an attachment JSON that will be added to the prompt/statement activity. Obviously, you can use an expression instead of the hard codes URL link. When running the bot scenario, in WebChat widget, you will see the prompt hosting the native player with all the features.
Failed fetching CLU intents, please try again.
I have created a CLU language model with intents, variables etc. I have trained the language model and deployed it. I was able to successfully test the deployment aswell. I am trying to attach this CLU model in Healthbot. I have given all the details necessary to add the language to bot. The details included subscription key, deployment name, project name etc. When I click fetch CLU intents, I get 'failed fetching CLU intents, please try again'. I double checked on the configurations and they are looked good but I am not sure why I get this error. Could someone please help resolve this issue.Accessing "Conversation", "User" or "Scenario" entire objects is not allowed
Health bot uses three scopes of variables: Conversation - Variables that store data throughout the entire conversation. They are removed when the conversation ends. User - Variables that are stored in the context of the User Id that interacts with the bot. They are stored until the user asks to remove them. They are used so that we can retrieve user specific data, like birthdate, without asking it each time the same user interacts with the bot. Scenario - Variables that are stored in the context of the scenario and kept until the scenario ends. In analogy to normal programming language, they are like function variables that are allocated on the stack. If scenario A calls scenario B, each of the scenarios can have the same variable "foo" and each scenario will hold a different value. This allows us to write contained and reusable scenarios without the fear of "side effects". The syntax for accessing each variable scope is as follows: "This is a welcome message " + conversation.welcomeMessage "conversation" is not a real object, it's just a scope of the welcomeMessage variable. Therefore, we don't allow accessing the "conversation" as plain JavaScript object since it's really a reserved word. To access specific variables within the conversation scope, you can use the assign step and "pluck" the variables within the conversation scope into a new object. For example: We define a new object on the scenario scope called "dumpObject", we then "cherry pick", variables from scenario or conversation scopes. We later can use this object whenever we like, for example use it to dump onto custom telemetry.
Introducing the new look of the Health Bot management portal
In the next few weeks, a new version of the Health Bot management portal will be rolled out. The new version has an improved UI and enhanced accessibility. The transition will be seamless and does not require any action from your end. As always, we are happy to hear your feedback, please use the smiley icon at the top-right side of the frame to submit your feedback. What is new? New stylish look and feel: The scenario editor tool is now keyboard accessible: Users can smartly navigate the scenario flow, using the Arrows and Tab keys. All the actions applicable to the scenario steps are keyboard accessible as well. Adding and Deleting edges are also accessible using the Enter and Delete keys. Users can even move the steps around the canvas using the Shift+Arrows keys. Smooth navigation to and from the Scenario Editor tool: Open the Editor by clicking the “Edit steps” button: Navigate back to scenario management using the “Back arrow”: Using the navigation bar to the left, any page in the portal is one click away even from within the editor. Search & Filter: Every page containing a table or list includes also a Search & Filter component on the right-side of the page: And many more experience enhancements. Useful tips to boost your experience: To add a new element on the canvas to a specific location, use the mouse right-click and the Add menu will pop-up, each of the 3 categories will expand to the list of elements. To easily open a sub-scenario from within a parent scenario, click the “Open scenario” button from the actions menu, and the sub-scenario will be opened in a new tab. To select multiple elements and edges, press the Shift key and select the desired elements with your mouse. You can move them around and you can also delete them by using the Delete key. To restart the WebChat conversation, use the new Start-over button next to the language picker. Use your mouse roller to zoom the canvas in and out.
