microsoft / microsoft/CopilotStudioSamples
Copilot studio not able to provide the correct outcome in embedded third party app using BOT framework webchat
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 797
- Forks
- 491
- PR merge metrics
- No merged PRs in 30d
Description
What sample tool are you using?
CopilotStudioSamples/BuildYourOwnCanvasSamples
Describe the bug
Cx has written the code in standard web chat interface, and they followed the documents that are available on git hub copilot studio sample to build own sample canvas BOT.
They have pulled the webchat interface from CDN and that is the latest version of Web chat by following the below articles.
GitHub - microsoft/BotFramework-WebChat: A highly-customizable web-based client for Azure Bot Services.
CopilotStudioSamples/BuildYourOwnCanvasSamples at master · microsoft/CopilotStudioSamples · GitHub
They have not embedded the BOT into the website yet because user was not having the access. But they have generated an HTML file and testing the BOT there.
To Reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior
Bot is working fine in copilot studio, but it is not giving the expected answers in webchat i.e, in web browser.
Screenshots
Additional context
Sample canvas in copilot studio
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with CopilotStudioSamples/BuildYourOwnCanvasSamples and the generated HTML file using the Web Chat CDN. Reproduce the behavior in the browser and compare the responses with the same bot in Copilot Studio. Done means the embedded Web Chat provides the expected answers; the issue needs more complete reproduction steps to identify the relevant change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100