Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Microsoft] Add "omnichannel" channel to Channels list, as it is now available in Azure Bot Service #5886

Closed
kaczmarekmhl opened this issue Sep 15, 2021 · 0 comments · Fixed by #5891
Assignees
Labels
Area: SDK General SDK issues that don't clearly map to other areas (e.g.: helper methods) Bot Services Required for internal Azure reporting. Do not delete. Do not change color. P0 Must Fix. Release-blocker
Milestone

Comments

@kaczmarekmhl
Copy link

Hi Bot Framework Team,
We'd like to add new "omnichannel" channel to Channels list in Bot.Builder.SDK. This should be added to all available programming languages, so bot developers can easily do a channel ID check on incoming Bot Activities.

For further details please contact those Microsoft aliases - michalka (engineering) and jone (PM).

Thank you!

@srinaath srinaath added Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-reported Issue is created by anyone that is not a collaborator in the repository. labels Sep 17, 2021
@mrivera-ms mrivera-ms added P0 Must Fix. Release-blocker Area: SDK General SDK issues that don't clearly map to other areas (e.g.: helper methods) and removed customer-reported Issue is created by anyone that is not a collaborator in the repository. labels Sep 21, 2021
@mrivera-ms mrivera-ms added this to the R15 milestone Sep 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: SDK General SDK issues that don't clearly map to other areas (e.g.: helper methods) Bot Services Required for internal Azure reporting. Do not delete. Do not change color. P0 Must Fix. Release-blocker
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants