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
Please add not that Outlook(desktop client) is NOT full support actionable message. #880
Comments
I'm not sure I understand. The documentation states it does not support |
Thank you for your replying. I understood that "Action.submit" was part of the "Actionable message" so I thought the "Docs" were incorrect. However, as you told me, if "Action.submit" is different from "Actionable message", I think there is no mistake in the description of Docs.Please close this issue. However, I think that this is a point that is easy to misunderstand for beginners who started learning Adaptive Cards" so if there are other people besides me, please consider commenting on Docs. |
Ah, I think I see. Actionable Messages is an Outlook-specific feature - an email that supports a card that can do stuff. Adaptive Card is just the UI piece of the feature. The original Actionable Message used what we call MessageCard format. Today, Actionable Messages also support the Adaptive Card format, which is not Outlook-specific. However, Outlook has some Outlook-specific additions to Adaptive Card, including a new action ( Think of Adaptive Card as being a "spec", and Outlook supports most of it, but not |
This issue has been marked resolved and will be closed. teraco, if you do not believe this issue has been resolved, please leave a comment with the text |
Hi,
I'd try to use actionable message in Outlook(desktop client) but Outlook(desktop client) NOT supported Action.Submit.
Would you add note that Outlook(desktop client) is NOT full support actionable message and link to this article?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: