Name: Outlook-Add-In-Actionable-Message
Owner: Office Developer
Description: A sample Outlook add-in that is activated by an actionable message. Shows how to retrieve initialization context from the action.
Created: 2017-10-19 20:01:24.0
Updated: 2018-05-17 21:57:35.0
Pushed: 2017-12-28 21:34:21.0
Homepage: null
Size: 320
Language: JavaScript
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
The sample demonstrates how to activate an add-in from an actionable message and pass an intialization context to the add-in.
In order to run this sample, you will need to host the included files on a web server. The choice of web server is completely up to you. The only requirement is that the web server be protected by a valid SSL certificate.
Before loading the add-in, you must update the manifest to replace all instances of localhost:8080 with the base URL of the server where you are hosting your add-in.
Follow the instructions in Sideload Outlook add-ins for testing to sideload the actionable-add-in.xml file to install the add-in.
The add-in adds two buttons to the ribbon when you are reading email messages.
Note: The initialization context is only present when the taskpane is invoked from an actionable message. If you open the taskpane by using the ribbon button, you will see a message letting you know that you need to invoke the add-in from a message.
Click the Send Add-in Activation button. A dialog opens to send the message:
(Optional): Modify the initialization context.
Click the Send Message button.
When the message arrives in your inbox, open it.
Click the Invoke “View Initialization Context” button.
The add-in taskpane opens and displays the initialization context.
You can use the second button in the actionable message to see how on-demand installation of store add-ins works. Before trying it, if you already have the Message Header Analyzer, be sure to uninstall it.
This project has adopted the Microsoft Open Source Code of Conduct. For more information, see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
