User Profile

MykolaMedynskiy

Copper Contributor

Joined Nov 08, 2021

4 Posts1 LikeLikes received

View All Badges

User Widgets

Recent Discussions

MS Teams oAuth Prompt Customization
Hey everyone, We are using standard https://github.com/microsoft/botbuilder-js for Node.js and specifically the https://www.npmjs.com/package/botbuilder-dialogs package which provides us with OAuth prompt dialog which uses the https://www.npmjs.com/package/botbuilder-core OAuth card, here is the interface: We need to customize this card with some elements like other buttons, columns, images, and other adaptive card elements. But it does not seem possible straight from the definition. So here are the questions we have: Is it possible to do the required customizations to the OAuth Card? or as an alternative, is it possible to use the "signin" action directly in the adaptive card which is easily designable? We already tried putting "signin" action directly into the adaptive card but it's not being rendered by MS Teams. And we already tried sending the adaptive card with OAuth content-type – same behavior. Thanks
May 25, 2022 Place Teams Developer
Bots
developer
User Interface
1.5KViews
0likes
2Comments
Re: Bot Framework Dispatch CLI replacement with Orchestrator
Nivedipa-MSFT we've checked all the documentation and haven't found the way to implement it. We can see that there is a refresh option, but how to use it and not affect the bot application files? Can it be kept separately from the bot project and be queried via some API?
Dec 01, 2021 Place Teams Developer
1.8KViews
0likes
1Comment
Re: Bot Framework Dispatch CLI replacement with Orchestrator
Hey Nivedipa-MSFT, So the requirements are: – periodically refresh orchestrator model – use it in the bot for intent recognition And the problem is refreshing the model without restarting the application, since the orchestrator model is not a Luis App, as was with Dispatch.
Nov 19, 2021 Place Teams Developer
1.9KViews
0likes
4Comments
Bot Framework Dispatch CLI replacement with Orchestrator
Hey everyone, As the Dispatch CLI will be deprecated on December 31, 2021, we've started evaluating Orchestrator as an alternative to it. Information about Dispatch CLI https://github.com/Microsoft/botbuilder-tools/tree/master/packages/Dispatch. We were using Dispatch CLI basically as a high-level router for our bot that will route the occurrence (text) to the correct resource (Luis, QnA) and produce a resource-specific intent. Also, we are retraining it periodically so the dispatcher will always have the up-to-date data from all resources so it will route to the correct resource. So, wanted to ask – what is the strategy of using an orchestrator in the current flow? We are able to retrain it with https://github.com/microsoft/botframework-clibut we don't wanna restart the bot after refreshing the orchestrator. Also, how can we use the same trained orchestrator model in multiple bots? (as I understood it's not a trained Luis app)
Solved
Nov 16, 2021 Place Teams Developer
developer
microsoft teams
2.1KViews
1like
7Comments

Recent Blog Articles

No content to show