Skip to content
This repository has been archived by the owner on Jun 28, 2023. It is now read-only.

QnA Maker follow-up prompts do not work in test WebChat #1272

Closed
kabatmartin123 opened this issue Aug 27, 2019 · 3 comments
Closed

QnA Maker follow-up prompts do not work in test WebChat #1272

kabatmartin123 opened this issue Aug 27, 2019 · 3 comments
Labels
Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-replied-to Required for internal reporting. Do not delete. customer-reported Required for internal Azure reporting. Do not delete.

Comments

@kabatmartin123
Copy link

Tool

Name: QnAMaker|Azure WebChat test
Version:
OS: windows 10

I have been testing my KB in the QnA Maker Portal using the test chatbot and it doesn’t work as expected with follow-up prompts.
The test chatbot respond partially as configured in the KB. However there isnt any of the follow-up prompts.
Could you help and point me the right direction?

Thank you very much

To Reproduce

Steps to reproduce the behavior:
Use any KB in web app bot on azure portal

Expected behavior

I would expect that the follow-up prompts from qnamaker are displayed as they are on the qnamaker portal

image

image

Additional context

Add any other context about the problem here.

[bug]

@Zerryth
Copy link
Contributor

Zerryth commented Aug 27, 2019

QnA Maker's multi-turn feature is still in preview, which is why the Bot Framework SDK Team has delayed integrating it into our SDK natively. So when using QnA Maker with our SDK, you will not get any follow-up prompts out-of-the-box as of today.

However!

We do provide C# and JS samples (qnamaker-prompting) of how to integrate the feature into your bot if you want to do so before we fold it into our SDKs:

Additionally, I've written a Stack Overflow post describing what exactly you're doing in order to manually plug in multi-turn into your bot.


Lastly, the team is on track to fold the multi-turn QnA feature into the SDK, as there are PRs out for 3 of our SDKs, which you could track, below, for when they will merge into the SDK natively:


Closing this issue as we are already working on it, however delay of folding it into our SDK depends on the "preview" status as well as having the PRs ready for all of our languages and not just C#

@Zerryth Zerryth closed this as completed Aug 27, 2019
@Zerryth Zerryth added Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-replied-to Required for internal reporting. Do not delete. customer-reported Required for internal Azure reporting. Do not delete. labels Aug 27, 2019
@kabatmartin123
Copy link
Author

@Zerryth thank you very much,I really appreciate your help. I do not class my self as a developer, so I apology for the questions. In the files you are sharing, which files should I be editing? thanks

@Zerryth
Copy link
Contributor

Zerryth commented Aug 28, 2019

Honestly many files, since you're implementing it all manually while multi-turn is not in the Bot Framework SDKs yet.

See the Stack Overflow post linked for more details, as I had stepped through basically all the files that needed to be edited to implement multi-turn. (No way around having to edit many files until it's baked into the SDK)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-replied-to Required for internal reporting. Do not delete. customer-reported Required for internal Azure reporting. Do not delete.
Projects
None yet
Development

No branches or pull requests

2 participants