botframework | Framework for creating messenger bots | Bot library

In my opinion, CDN will work in your case. Because all the service are from service provider anyway, so create CDN for bot service will be benefit to those contact with service provider. And you need to know that CDN also help user request to choose a better point(not only the nearest, but also a free, well point) to connect to service, e.g one endpoint burst into error or busy. Azure CDN will provide a new url to replace the former one, this is where it will work.

I think any assumption is smaller than the experiment result, you can try to use CDN first to test if it worked. Azure CDN is payed for usage the more you payed indicates the more useful it is.

From your link : https://docs.microsoft.com/en-us/azure/cognitive-services/luis/luis-tutorial-bing-spellcheck

The first line says "The V3 prediction API now supports the Bing Spellcheck API." So it does support it.

In Composer you can use a direct call to the API with a Send HTTP action. see the following:

there are two approaches :

1. Using pro-active messages via the bot's Teams Channel.
   https://docs.microsoft.com/en-us/microsoftteams/platform/bots/how-to/conversations/send-proactive-messages?tabs=dotnet
2. if you do not need/want a bot that there are options to 'just' start a new 1:1 or group-chat with a Graph call.
   https://docs.microsoft.com/en-us/graph/api/chat-post?view=graph-rest-beta&tabs=http

The endpoint i used to postMessage on personal chat is incorrect and it was present in the docs as well.

Below is the correct endpoint. This endpoint can be seen by logging the http payload request body of /api/messages api

the easiest thing to do is go to the designer on Adaptivecards.io. They have a super simple Adaptive Cards Designer experience that is drag and drop.

on other tabs they have example templates which you can launch in the designer to see how they work and play with them.

In your example above, the card is simply a text field with two image links and the images are clickable. You can use the containers and/or columns components in the designer to layout the items.

Geolocation data can be accessed using the below method. This will provide you with the longitude and latitude providing the user grants access to this data.

You will then need another process or library to convert the location data to a physical location in the real world.

When it comes to styling options, that's controlled by Teams and is largely outside your control. However, when it comes to layout, you have a great deal of control because Teams supports Adaptive Cards. Read more about Adaptive Cards here:

• https://adaptivecards.io/
• https://blog.botframework.com/2019/07/02/using-adaptive-cards-with-the-microsoft-bot-framework/

Regarding the RASA part of your question, have a look at this: Does RASA Integration with MS Teams support Adaptive Cards?

ChannelData is the way to send channel-specific info from the bot to the channel, and ultimately to the provider (say Slack), that's not included in the Bot Framework schema.

However, the way that info is converted to what the channel requires is specific to the adapter implementation.

There is a SlackAdapter in Bot Framework SDK that has a the SendActivitiesAsync() method, (as any other adapter) that currently uses the SlackHelper.ActivityToSlack method to create whatever Slack requires.

You could create your own HaackedSlackAdapter inheriting from SlackAdapter and override SendActivitiesAsync() to send exactly what you need.

Then you'd only have to send from the bot, in the ChannelData whatever you need to send to Slack, so your new adapter can "translate" it to Slack lingo.

So, to answer the other part of your answer, you'd have to create a complete new message to send to Slack or maybe just tweak the result from the SlackHelper.

supposing you don't have control over the client, which would be the best.

You can resort to an old overload on the ever-growing hierarchy of bot adapters that hasn't been marked as deprecated.

You'd have to use the PostAsync method (api/post-messages endpoint) in the following controller (showing the one created by the current set of bot framework templates just for comparison):