Skip to content

Commit 9af5d5c

Browse files
authored
Merge pull request #106960 from diberry/diberry/0309-qna-pva
[Cogsvcs] QnA - Power Virtual Agent
2 parents 92679b5 + 58dcd78 commit 9af5d5c

24 files changed

+304
-7
lines changed

articles/cognitive-services/QnAMaker/Tutorials/integrate-qnamaker-luis.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: LUIS and QnAMaker - Bot Integration
2+
title: LUIS and QnAMaker - Bot Integration
33
titleSuffix: Azure Cognitive Services
44
description: As your QnA Maker knowledge base grows large, it becomes difficult to maintain it as a single monolithic set and there is a need to split the knowledge base into smaller logical chunks.
55
services: cognitive-services
@@ -32,13 +32,13 @@ In the above scenario, QnA Maker first gets the intent of the incoming question
3232
1. [Create an app](https://docs.microsoft.com/azure/cognitive-services/luis/create-new-app).
3333
1. [Add an intent](https://docs.microsoft.com/azure/cognitive-services/luis/add-intents) for each QnA Maker knowledge base. The example utterances should correspond to questions in the QnA Maker knowledge bases.
3434
1. [Train the LUIS app](https://docs.microsoft.com/azure/cognitive-services/luis/luis-how-to-train) and [publish the LUIS app](https://docs.microsoft.com/azure/cognitive-services/luis/publishapp) your LUIS App.
35-
1. In the **Manage** section, make note of your LUIS app ID, LUIS endpoint key, and [custom domain name](../../cognitive-services-custom-subdomains.md). You will need these values later.
35+
1. In the **Manage** section, make note of your LUIS app ID, LUIS endpoint key, and [custom domain name](../../cognitive-services-custom-subdomains.md). You will need these values later.
3636

3737
## Create QnA Maker knowledge bases
3838

3939
1. Sign in to [QnA Maker](https://qnamaker.ai).
4040
1. [Create](https://www.qnamaker.ai/Create) a knowledge bases for each intent in the LUIS app.
41-
1. Test and publish the knowledge bases. When you publish each KB, make note of the KB ID, resource name (custom subdomain before _.azurewebsites.net/qnamaker_), and the authorization endpoint key. You will need these values later.
41+
1. Test and publish the knowledge bases. When you publish each KB, make note of the KB ID, resource name (custom subdomain before _.azurewebsites.net/qnamaker_), and the authorization endpoint key. You will need these values later.
4242

4343
This article assumes the KBs are all created in the same Azure QnA Maker subscription.
4444

@@ -55,7 +55,7 @@ In the above scenario, QnA Maker first gets the intent of the incoming question
5555

5656
## Change code in BasicLuisDialog.cs
5757
1. From the **Bot Management** section of the web app bot navigation in the Azure portal, select **Build**.
58-
2. Select **Open online code editor**. A new browser tab opens with the online editing environment.
58+
2. Select **Open online code editor**. A new browser tab opens with the online editing environment.
5959
3. In the **WWWROOT** section, select the **Dialogs** directory, then open **BasicLuisDialog.cs**.
6060
4. Add dependencies to the top of the **BasicLuisDialog.cs** file:
6161

@@ -150,7 +150,7 @@ In the above scenario, QnA Maker first gets the intent of the incoming question
150150
```
151151

152152

153-
7. Modify the BasicLuisDialog class. Each LUIS intent should have a method decorated with **LuisIntent**. The parameter to the decoration is the actual LUIS intent name. The method name that is decorated _should_ be the LUIS intent name for readability and maintainability but doesn't have to be the same at design or run time.
153+
7. Modify the BasicLuisDialog class. Each LUIS intent should have a method decorated with **LuisIntent**. The parameter to the decoration is the actual LUIS intent name. The method name that is decorated _should_ be the LUIS intent name for readability and maintainability but doesn't have to be the same at design or run time.
154154

155155
```csharp
156156
[Serializable]
@@ -165,7 +165,7 @@ In the above scenario, QnA Maker first gets the intent of the incoming question
165165
// assumes all KBs are created with same Azure service
166166
static string qnamaker_endpointKey = "<QnA Maker endpoint KEY>";
167167
static string qnamaker_resourceName = "my-qnamaker-s0-s";
168-
168+
169169
// QnA Maker Human Resources Knowledge base
170170
static string HR_kbID = "<QnA Maker KNOWLEDGE BASE ID>";
171171

@@ -235,4 +235,4 @@ In the Azure portal, select **Test in Web Chat** to test the bot. Type messages
235235
## Next steps
236236

237237
> [!div class="nextstepaction"]
238-
> [Create a business continuity plan for QnA Maker](../How-To/business-continuity-plan.md)
238+
> [Integrate your knowledge base with a Power Virtual Agent](integrate-with-power-virtual-assistant-fallback-topic.md)

articles/cognitive-services/QnAMaker/Tutorials/integrate-with-power-virtual-assistant-fallback-topic.md

Lines changed: 295 additions & 0 deletions
Large diffs are not rendered by default.
4.31 KB
Loading
5.25 KB
Loading
180 KB
Loading
Loading
Loading
Loading
Loading
Loading

0 commit comments

Comments
 (0)