You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cognitive-services/QnAMaker/Tutorials/integrate-qnamaker-luis.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: LUIS and QnAMaker - Bot Integration
2
+
title: LUIS and QnAMaker - Bot Integration
3
3
titleSuffix: Azure Cognitive Services
4
4
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.
5
5
services: cognitive-services
@@ -32,13 +32,13 @@ In the above scenario, QnA Maker first gets the intent of the incoming question
32
32
1.[Create an app](https://docs.microsoft.com/azure/cognitive-services/luis/create-new-app).
33
33
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.
34
34
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.
36
36
37
37
## Create QnA Maker knowledge bases
38
38
39
39
1. Sign in to [QnA Maker](https://qnamaker.ai).
40
40
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.
42
42
43
43
This article assumes the KBs are all created in the same Azure QnA Maker subscription.
44
44
@@ -55,7 +55,7 @@ In the above scenario, QnA Maker first gets the intent of the incoming question
55
55
56
56
## Change code in BasicLuisDialog.cs
57
57
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.
59
59
3. In the **WWWROOT** section, select the **Dialogs** directory, then open **BasicLuisDialog.cs**.
60
60
4. Add dependencies to the top of the **BasicLuisDialog.cs** file:
61
61
@@ -150,7 +150,7 @@ In the above scenario, QnA Maker first gets the intent of the incoming question
150
150
```
151
151
152
152
153
-
7. ModifytheBasicLuisDialog 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. ModifytheBasicLuisDialog 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.
154
154
155
155
```csharp
156
156
[Serializable]
@@ -165,7 +165,7 @@ In the above scenario, QnA Maker first gets the intent of the incoming question
165
165
// assumes all KBs are created with same Azure service
0 commit comments