Skip to main content

OWA Voting Buttons Compose App for Office365/Exchange 2016

OWA or Outlook on the Web have never quite had the feature parity with the desktop version of Outlook which can be a point of frustration for those primarily using it. Although interesting in Office365 new features like clutter, sweep etc are now lighting up in the OWA first before they make their way into new desktop releases. One of the things you haven't been able to do previously with OWA is create an Email with voting buttons. With compose apps and some of the recent changes in version 1.3 of the API which I posted about here, you now have the ability to add some of this functionality back in. Actually with a little imagination you also have the ability to actually build something a lot better then the voting buttons feature which have been around in Exchange for some time. But in this post I want to show how you can create a Compose Mail App that uses EWS to make changes to the draft message to enable the feature.

One thing also to note is that creating an Email with Voting buttons isn't supported also in EWS  so I'm using a workaround of generating the PidLidVerbStream property value using the documentation from https://msdn.microsoft.com/en-us/library/ee218541(v=exchg.80).aspx . The one issue you can have is if you don't get the value of this property correct this can cause Outlook to crash (which means you then need to delete the offending item with mfcMapi). So this Mail App would be unsupported, experimental and largely untested.

Here's a screenshot of what the Apps looks like in Action


After you select the Voting option you want you need to hit the Save button which will invoke the actions to modify the draft message.

I've put the code for this MailApp up on my GitHub repo https://github.com/gscales/MailApps/tree/master/OWAVoting  if you decide to test it and find any bugs please submit them back. As I mentioned before you should consider this experimental only. All the code is included in the script.js file and uses the workaround I described here as this was only a test app I haven't put any error processing in the Aysnc callbacks.
Labels:

Popular posts from this blog

The MailboxConcurrency limit and using Batching in the Microsoft Graph API

If your getting an error such as Application is over its MailboxConcurrency limit while using the Microsoft Graph API this post may help you understand why. Background   The Mailbox  concurrency limit when your using the Graph API is 4 as per https://docs.microsoft.com/en-us/graph/throttling#outlook-service-limits . This is evaluated for each app ID and mailbox combination so this means you can have different apps running under the same credentials and the poor behavior of one won't cause the other to be throttled. If you compared that to EWS you could have up to 27 concurrent connections but they are shared across all apps on a first come first served basis. Batching Batching in the Graph API is a way of combining multiple requests into a single HTTP request. Batching in the Exchange Mail API's EWS and MAPI has been around for a long time and its common, for email Apps to process large numbers of smaller items for a variety of reasons.  Batching in the Gr...
Read more

Sending a Message in Exchange Online via REST from an Arduino MKR1000

This is part 2 of my MKR1000 article, in this previous post  I looked at sending a Message via EWS using Basic Authentication.  In this Post I'll look at using the new Outlook REST API  which requires using OAuth authentication to get an Access Token. The prerequisites for this sketch are the same as in the other post with the addition of the ArduinoJson library  https://github.com/bblanchon/ArduinoJson  which is used to parse the Authentication Results to extract the Access Token. Also the SSL certificates for the login.windows.net  and outlook.office365.com need to be uploaded to the devices using the wifi101 Firmware updater. To use Token Authentication you need to register an Application in Azure https://msdn.microsoft.com/en-us/office/office365/howto/add-common-consent-manually  with the Mail.Send permission. The application should be a Native Client app that use the Out of Band Callback urn:ietf:wg:oauth:2.0:oob. You ...
Read more

How to test SMTP using Opportunistic TLS with Powershell and grab the public certificate a SMTP server is using

Most email services these day employ Opportunistic TLS when trying to send Messages which means that wherever possible the Messages will be encrypted rather then the plain text legacy of SMTP.  This method was defined in RFC 3207 "SMTP Service Extension for Secure SMTP over Transport Layer Security" and  there's a quite a good explanation of Opportunistic TLS on Wikipedia  https://en.wikipedia.org/wiki/Opportunistic_TLS .  This is used for both Server to Server (eg MTA to MTA) and Client to server (Eg a Message client like Outlook which acts as a MSA) the later being generally Authenticated. Basically it allows you to have a normal plain text SMTP conversation that is then upgraded to TLS using the STARTTLS verb. Not all servers will support this verb so if its not supported then a message is just sent as Plain text. TLS relies on PKI certificates and the administrative issue s that come around certificate management like expired certificates which is why ...
Read more
All sample scripts and source code is provided by for illustrative purposes only. All examples are untested in different environments and therefore, I cannot guarantee or imply reliability, serviceability, or function of these programs.

All code contained herein is provided to you "AS IS" without any warranties of any kind. The implied warranties of non-infringement, merchantability and fitness for a particular purpose are expressly disclaimed.