Rich Card with Bot Framework SDK V4

Messages exchanged between a user and a bot can contain media such as images, video, etc. The Bot Framework SDK supports the task of sending rich messages to the user.

In this tutorial, you will learn the following.

1. Design Hero Card and Response with Images.
2. Design the Video Card and Response with Video.
3. Build and Publish the Solution.
4. Test your bot with Web Chat Client.

Below are the prerequisites.

1. The bot created in the previous article to help you understand the simple QnA Maker Bot
2. Response card can be designed with different media response, i.e., Image & Video

Let's understand the architecture flow with respect to this article.

Primary bot communicates with the user through message activities.

To send a simple text message, use turn context object SendActivityAsync method to send a single message response. You can use SendActivitiesAsync method to send multiple messages. 

1. await turnContext.SendActivityAsync($"Welcome!");  

To receive a simple text message, use text property of activity object. 

1. var responseMessage = turnContext.Activity.Text;  

Some message activities consist of simple text and others may consist of richer context such as Cards, i.e., Hero Card, Video Card etc. Let’s start designing the cards.

Step 1 - Design Hero Card and Response with Images

Hero card allows you to combine images and buttons in one object, and send them to the user.

To process with rich card i.e. Hero Card, the below properties are required.

Type	Description
Tile	Title of the hero card
Sub Title	Sub Title of the hero card
Text	Text or Description need to display the below image
Images	Image URL which needs to be rendered
Buttons	Button with the click event,  clicking allows the user to navigate

1. public static HeroCard GetHeroCard()  
2. {  
3.     var heroCard = new HeroCard  
4.     {  
5.         Title = "<<Title>>",  
6.         Subtitle = "<<SubTitle>>",  
7.         Text = "<<Secription>>",  
8.         Images = new List<CardImage> { new CardImage("<<Image Path>>") },  
9.         Buttons = new List<CardAction> { new CardAction(ActionTypes.OpenUrl, "Get Started", value: "<<Re-direct Url>>") },  
10.     };  
11.     return heroCard;  
12. }  

QnAMaker Hero Card Response Design

Set Response design with Hero Card values.

Step 2 - Design Video Card and Response with Video

Video Card allow you to play video. Typically it's used to open a URL and stream an available video.

To process with rich card i.e. Video Card, the below properties are required.

Type	Description
Tile	Title of the hero card
Sub Title	Sub Title of the hero card
Text	Text or Description need to display the below image
Images	Image URL which needs to be rendered
Media	URL, i.e., video URL to stream any available video
Buttons	Button with the click event, Onclick allows the user to navigate

1. public static VideoCard GetVideoCard(string[] qnaAnswerData)  
2.         {  
3.             var videoCard = new VideoCard  
4.             {  
5.                 Title = <<”Title”>>,  
6.                 Subtitle = <<”Title”>>,  
7.   
8.                 Text = <<”Title”>>,  
9.                 Image = new ThumbnailUrl  
10.                 {  
11.                     Url = <<”Title”>>,  
12.                 },  
13.                 Media = new List<MediaUrl>  
14.                 {  
15.                     new MediaUrl()  
16.                     {  
17.                         Url = <<”Title”>>,  
18.                     },  
19.                 },  
20.                 Buttons = new List<CardAction>  
21.                 {  
22.                     new CardAction()  
23.                     {  
24.                         Title = "Learn More",  
25.                         Type = ActionTypes.OpenUrl,  
26.                         Value =  <<”Title”>>,  
27.   
28.                     },  
29.                 },  
30.             };  
31.   
32.             return videoCard;  
33.         }  

QnaMaker Video Card Response Design.

Set Response design with Video Card values.

Step 3 - Build and Publish the Solution

Navigate to EchoBot.cs file and add a condition for Hero Card and Video Card response and design.

Replace the AccessQnAMaker code with the below section. It checks the response parameter and design card. If the response has 5 parameters, it calls the Hero Card method. If the response has 6 parameters, it calls Video Card method else replies with simple text. 

1. private async Task AccessQnAMaker(ITurnContext<IMessageActivity> turnContext, CancellationToken cancellationToken)  
2.         {  
3.             var results = await EchoBotQnA.GetAnswersAsync(turnContext);  
4.             string[] qnaAnswerData = results[0].Answer.Split(';');  
5.             int dataSize = qnaAnswerData.Length;  
6.             if (results.Any())  
7.             {  
8.                 var attachments = new List<Attachment>();  
9.                 // Reply to the activity we received with an activity.  
10.                 var reply = MessageFactory.Attachment(attachments);  
11.                 //image card have 5 paramters  
12.                 if (dataSize == 5)  
13.                 {  
14.                     reply.Attachments.Add(Cards.GetHeroCard(qnaAnswerData).ToAttachment());  
15.                     await turnContext.SendActivityAsync(reply, cancellationToken);  
16.                 }  
17.                 //video card have 6 parameter  
18.                 else if (dataSize == 6)  
19.                 {  
20.                     reply.Attachments.Add(Cards.GetVideoCard(qnaAnswerData).ToAttachment());  
21.                     await turnContext.SendActivityAsync(reply, cancellationToken);  
22.                 }  
23.                 else  
24.                 {  
25.                     await turnContext.SendActivityAsync(MessageFactory.Text(results.First().Answer), cancellationToken);  
26.                 }  
27.             }  
28.             else  
29.             {  
30.                 await turnContext.SendActivityAsync(MessageFactory.Text("Sorry, could not find an answer in the Q and A system."), cancellationToken);  
31.             }  
32.         }  

Right-click the solution. Select "Build and publish the solution"with the help of published profile.

Step 4 - Test your bot with Web Chat Client

Navigate to Azure WebApp Bot and select Test in WebChat client.

The previous article can be found from these links.

• Learn and Build Azure Bot With Bot Framework SDK V4
• Build QnAMaker Azure Bot with Bot Framework SDK V4

I hope you have enjoyed and learned something new in this article. Thanks for reading and stay tuned for the next article.

Learn QnAMaker Azure Bot With Bot Framework SDK V4

QnA Maker service is used to create a knowledge base to add question-and-answer support to your Azure Bot. When you create your knowledge base, you seed it with questions and answers.




Previous Article : Learn azure bot service using Bot Framework SDK V4

In this tutorial, you will learn the following.

1. Create a QnA Maker service and knowledge base.
2. Train and Publish knowledge base information.
3. Add QnA Maker Knowledge Bas information to your Bot
4. Update your bot to query the knowledge base
5. Test you bot locally
6. Publish your bot to Azure Bot Service
7. Test your bot using Web Chat Client

Below are the prerequisites,

1. The bot created in the previous article. We will add a question-and-answer feature to the bot.
2. QnA Maker portal is used to create, train, and publish the knowledge base to use with the bot.

Step 1 - Create a QnA Maker service and knowledge base

• Sign into to the QnA Maker portal with your Azure credentials.
• Click "Create a knowledge base".
• Click “Create a QnA Services".

• It will navigate to Azure Portal. Once there, fill all the below details to proceed
• Name
• Subscription
• Pricing Tier
• Resource Group
• Search Location
• App Name
• Website Location

• Once it is created, connect your QnA Services with your knowledge base.
• Select Microsoft Azure Directory ID.
• Select Azure Subscription Name.
• Select available Azure QnA Service.
• Name your knowledge base.

•  Provide the URL from where the data needs to be extracted.

• Click “Create your KB” to build a knowledge base.

Step 2 - Train and Publish knowledge base information

• Once the knowledge base is created, click “Save and Train” followed by Publish button to publish the knowledge base.

• You can click "Create Bot" using this screen or integrate the QnA Maker Services with an existing solution.

Step 3 - Add QnA Maker Knowledge information to your Bot

To continue with the below steps, kindly visit my previous article and download the source code.

Browse the solution and navigate to the app.settings file.

1. {  
2.   "MicrosoftAppId": "",  
3.   "MicrosoftAppPassword": "",  
4.   "ScmType": "None",  
5.     
6.   "QnAKnowledgebaseId": "knowledge-base-id",  
7.   "QnAAuthKey": "qna-maker-resource-key",  
8.   "QnAEndpointHostName": "your-hostname"   
9. }  

Field	Value
QnAKnowledgebaseId	The knowledge base ID that the QnA Maker portal generated for you.
QnAAuthKey	The endpoint key that the QnA Maker portal generated for you.
QnAEndpointHostName	The host URL that the QnA Maker portal generated. Use the complete URL, starting with https:// and ending with /qnamaker. The full URL string will look like "look like "https://< >.azure.net/qnamaker".

Step 4 - Update your bot to query the knowledge base

• Add NuGet Package to your project Microsoft.Bot.Builder.AI.QnA
• Right-click dependencies and select Manage Nuget Package
• Select Browse Option
• Type NuGet package “Microsoft.Bot.Builder.AI.QnA”
• Select the Nuget Package
• Check the version and click install and accept the prompt.

Similarly, add Nuget Package Microsoft.Extensions.Configuration

Navigate to Startup.cs file, add these namespace references.

1. using Microsoft.Bot.Builder.AI.QnA;  
2. using Microsoft.Extensions.Configuration;  

And, modify the ConfigureServices method create a QnAMakerEndpoint that connects to the knowledge base defined in the appsettings.json file in Startup.cs.

1. services.AddSingleton(new QnAMakerEndpoint    
2. {    
3.    KnowledgeBaseId = Configuration.GetValue<string>($"QnAKnowledgebaseId"),    
4.    EndpointKey = Configuration.GetValue<string>($"QnAAuthKey"),    
5.    Host = Configuration.GetValue<string>($"QnAEndpointHostName")    
6.  });    

In your EchoBot.cs file, add these namespace references.

1. using System.Linq;  
2. using Microsoft.Bot.Builder.AI.QnA;  

 Add a EchoBotQnA connector and initialize it in the bot's constructor to EchoBot.cs.

1. public QnAMaker EchoBotQnA { get; private set; }  
2. public EchoBot(QnAMakerEndpoint endpoint)  
3. {  
4.    EchoBotQnA = new QnAMaker(endpoint);  
5. }  

Below the OnMembersAddedAsync( ) method, create the method AccessQnAMaker( ) by adding the following code.

1. private async Task AccessQnAMaker(ITurnContext<IMessageActivity> turnContext, CancellationToken cancellationToken)  
2. {  
3.    var results = await EchoBotQnA.GetAnswersAsync(turnContext);  
4.    if (results.Any())  
5.    {  
6.       await turnContext.SendActivityAsync(MessageFactory.Text(" results.First().Answer), cancellationToken);  
7.    }  
8.    else  
9.    {  
10.       await turnContext.SendActivityAsync(MessageFactory.Text("Sorry, could not find an answer in the Q and A system."), cancellationToken);  
11.    }  
12. }  

Now, within OnMessageActivityAsync( ), call your new method AccessQnAMaker( ) by adding the following code.

1. protected override async Task OnMessageActivityAsync(ITurnContext<IMessageActivity> turnContext, CancellationToken cancellationToken)  
2. {  
3.    // First send the user input to your QnA Maker knowledge base  
4.    await AccessQnAMaker(turnContext, cancellationToken);  
5.    ...  
6. }  

Step 5 - Test your bot locally

• Press F5, Browse the bot emulator and connect with localhost and port number
• At this point, your bot should be able to answer some questions. Run the bot locally and open it in the Emulator.

Step 6 - Publish your bot to Azure Bot Service

• Right-click the solution.
• Select the Publish option.
• Select the publish profile  and click Publish to proceed. 

Step 7 - Test your bot using Web Chat Client

• Browse the WebApp Bot using Azure Portal
• Select the Test in WebChat under Bot Management

I hope you have enjoyed and learned something new in this article. Thanks for reading and stay tuned for the next article.

Learn and Build Azure Bot With Bot Framework SDK V4

Azure Bot Service provides an integrated environment that is purpose-built for bot development, enabling you to build, connect, test, deploy, and manage intelligent bots.

In this tutorial, you will learn the following:

1. Create Bot using VS2017 (Bot Framework SDK V4 template)
2. Launch Emulator to run and test the Bot locally
3. Create Azure Bot using Azure Bot Services
4. Deploy and test the Bot at Web Chat

Below are the prerequisites:

• Visual Studio 2017 or later version 
• Bot Framework Emulator for SDK V4
• Bot Framework SDK V4 Template for C#

Step 1 - Create Bot using VS2017 (Bot framework SDK V4 template)

• Launch Visual Studio 2017, create a new project, and select the Bot Framework.
• Select the Echo Bot (Bot Framework V4) template.
• Select the location and give the bot name.
• Click OK to create the project.

• The project consists of all necessary code to get started with a quick bot. Expand the solution followed by the Bot folder. Click on the EchoBot.cs file.

EchoBot.cs file consists of two main methods.

• OnMessageActivityAsync -> Invoke with every new message
• OnMembersAddedAsync -> invoke first time to add to any channel

Step 2 - Launch Emulator to run and test the Bot locally

• Fill out the fields for your bot. Use your bot's welcome page address (typically http://localhost:3978) and append routing info '/api/messages' to this address.
• Click "Connect".

As you connect with Bot Framework Emulator.

• A welcome message will appear at the initial stage, i.e., “Hello and Welcome”.
• Type the message “How r u “. You will get back the echo with the same message.

So, a simple echo bot is created and tested locally using Bot Framework V4.

Step 3 - Create an Azure Bot using Azure Bot Services

Log into the Azure portal.

• Click the "Create a new resource" link found on the upper left-hand corner of the Azure portal.
• Select AI + Machine Learning.
• Select Web App bot.

Navigate to Azure Bot Service blade.

• Set all the required information.
• Name
• Subscription
• Resource Group
• Location
• Pricing
• App Name

• Select the Bot Template, i.e., Echo Bot (C#).
• Click OK to select the template.
• Click "Create" to the Azure Bot Service and deploy the bot to the cloud.

Navigate to the App Service Setting to get the Publish profile.

• Select "All App Service Settings".
• Select "Overview".
• Click on "Get Publish Profile" to download.

Step 4 - Deploy and test the Bot at Web Chat

• Navigate and right-click on Visual Studio Project solution.
• Select "Build" and then publish it.
• As you are doing the first time, the profile is not selected till yet. Click the Start 

• Browse the downloaded profile and click the Publish button.
• The solution will get deployed to the cloud.

Now that your bot is created, test it in Web Chat.

Test the bot

In the Bot Management section, click Test in Web Chat. The Azure Bot Service will load the Web Chat control and connect to your bot.

I hope you have enjoyed and learned something new in this article. Thanks for reading and stay tuned for the next article. 

SharePoint Online - Set A Reminder

This article will talk about the below-defined two artifacts and when to use what.

1. Set a Reminder
2. Alert Me 

S.no	Set a Reminder	Alert ME
1	It is available for the Modern experience only	It is available for both the Modern and Classic experiences.
2	It works with both List and Library with a defined custom date column	It works with List and Library without any defined column
3	It works as a reminder for a particular user, even without an update or action trigger to item or document	It works as a trigger but it needs an item update or any action trigger to item or document.
4	Custom Date column is a prerequisite	Event trigger; i.e. Item create, update, delete is a prerequisite

Let's get started to explore more on this topic.

Step 1: Create a Custom List or Library with Custom Date Column

List or Library can have multiple date columns, then "Set a reminder" shows all the date columns. It will work with a single selection of date column.

Let's follow the below steps to proceed.

1. Hover on the Flow option.
2. Select Flow option at List View Level.
3. Select Set a reminder.
4. Select custom date column  i.e. Column Name "Date".

Step 2: Configure MS Flow for OOTB Reminder Template

One you select date column, the flow template will appear. Set the "Remind Me" as the number of days, i.e., 2. It means the reminder will trigger two days before the defined timeframe in Date Column.

Step 3: Trigger Flow and Check the Email

How does it work now? Example: If a user has created a couple of items or document in List or Library where date column is configured as the 5th of the current month, as the user mentioned the reminder duration is 2 days, on the 3rd of the same month, they will get notified.

Flow executes and triggers an email two days before, as per the defined date in the Date column.

NoteThe reminder will be triggered for the user who has configured the reminder, irrespective of the document in the list.

Now, let's talk about Alert also. Alert is an existing feature of SharePoint Online and OnPremises. Alert can be defined at Item as well as List or Library level.

Step 1: Alert Me at List Level 

If I navigate to List and click the "...", the fall back menu option will appear with the "ALERT ME" option.

Step 2: Alert Me Trigger Options at List Level

The Alert Me option triggers the email or message based on change type; i.e., a new item added, existing items modified, items deleted.

Step 3: Alert Me at List Item Level

If I navigate to List Item and click the "...", the fall back menu option will appear with "ALERT ME" option.

Step 4: Alert Me Trigger Options at List Item Level

The Alert Me option triggers the email or message based on change type; i.e., any changes to document or item created or modified by ME.

I hope you have enjoyed and learned something about "when to use what" in this article. Thanks for reading and stay tuned for the next article.