I developed an add-in with a MessageComposeCommandSurface extension point.
It appears, is activated and works on outlook.office.com but with windows desktop client, Outlook 2016 (version 16.0.8625.2121), the button appears in compose mode but stays gray and it is not clickable.
I tested the command-demo-addin mentioned in Microsoft Docs and published on Github with the same result. Similarly, as shown on screenshot, it is impossible to click and launch the add-in which seems unactivated.
The COMPOSE buttons are disabled in the following instances:
1) The Item is in a public folder.
2) The Item is in Junk, Outbox (not drafts), or Sync Issues.
3) The item is "secure". DRM, or S-MIME encrypted. (older versions of Outlook also do not support S-MIME signed)
4) Outlook is offline.
In the situation where Read Mode add-ins are working, but Compose does NOT it is almost always #3. Usually the user will have on the option to always DRM / S-MIME their outgoing messages.
Update with image of security settings:
If Com Add-ins load a Custom Form this can also affect add-ins:
Checking Com Add-ins:
Note that outlook actually ships with some add-ins and a lot of com-addins work fine with Web Add-ins. It's only when Com Add-ins override the default new mail form (or other forms) that they can interfere with Web Add-ins.
Some COM add-ins will NOT use Custom Form, but will access the parent folder (item.Parent) and there is currently a bug that disable's Web Add-ins when a COM Add-in or VBA script does this.
File->Options->Add-Ins-> "Go" (next to manage add-ins)
If you have an antivirus instaled like avast, try to disable the addin of this and then try to open your compose mail window.
Related
We run some custom add-ins in Outlook application and occasionally find that the Outlook application disables them; I then have to manually go to the application settings and re-enable them on each users PC. We are running Microsoft Office 365 click to run applications. I have tried the following but nothing seem to work 100% of the time.
I have tried setting the "AddinList/ProgID" REG key to 1 (always enabled) as described here - https://learn.microsoft.com/en-us/office/vba/outlook/concepts/getting-started/support-for-keeping-add-ins-enabled.
I have also tried setting a number of registry key combinations as described here - https://www.konnectemail.com/prevent-outlook-add-in-from-getting-disabled
Is there a specific way to tell the office application to NEVER disable a particular add-in regardless of the Office version?
I have VSTO word addin and I have put a button in the ribbon and a label (company name).
On button click, I get selected text and pass this selected word as a queryparam to my application as below: www.myapplication.com?selectedtext= [getselectdwordfromword]
We have few clients and all have a different application name.
So how can the client set his application URl and label (company name)?
Is there any way so we can provide configurations and client changes configurations based on their requirements before installing VSTO in their system?
Thanks in advance
You can develop a custom UI for the add-in installer where your customers can enter the required application URL and company name. So, at runtime you could read such values from the windows registry or any other place where the add-in installer could write down these values after installing. The Deploy an Office solution by using Windows Installer article describes all the required steps for creating MSI installers.
I have a problem with Outlook 365 add-in we are developing. The add-in should accept files dragged from user desktop. The web page is working fine with Drag&Drop in any browser: IE, Edge, Opera.
Same web page in add-in accepts only files dragged from Office 365 Application and doesn't accept anything from Outlook, user desktop, any other website or app.
So in fact add-in is droppable and working fine, but only for files dragged from Office 365 App.
Is there any special security setting in place?
The web browser which hosts your web add-in doesn't recognize and understand the format which is used for dragged items from Outlook. On the page Upload fails when user drags and drops attachment from email client you may find the following explanation:
All browsers are only expecting the actual file drag/drop format (CF_HDROP), but when dragging from Outlook, there is no file on the filesystem. What you get is the CF_FILEDESCRIPTOR and CF_FILECONTENTS formats. No browser that I know of (not even IE), knows how to handle that.
I am currently having problems with the on-send feature on some desktop clients. I have implemented an addin but for some desktop clients emails are blocked from being sent. The email hangs and does not get sent. Is there a way to use on-send by disable for desktop clients. Can i do this in the manifest file or in powershell? Is it even possible to disable on-send for specific platforms. I want to configure my addin to never block emails. I suspect emails are blocked because event.completed() close as expected on some Desktop clients.
This is a new thing since the on-send never worked on desktop clients before. Now that it does...i have to deal with this bug somehow
There is no way to disable an add-in for just desktop clients. It is either enabled for all Win32, Mac and OWA, or off for all. This is true of all add-ins not just OnSend. Though previously this feature was not enabled for Desktop clients, it now is.
Note to unblock e-mails you should be calling event.completed({allowEvent:true}); (or false) to block e-mails. See: https://learn.microsoft.com/en-us/javascript/api/office/office.addincommands.event?view=word-js-preview
What is your scenario that you need to disable this for Desktop but NOT OWA?
You could also detect what platform you are on an change behavior of your add-in as necessary.
But the event.completed({allowEvent:true}); also have problem.
For example:
If I install a com app on Outlook then install an on-send add-in.
The problem is, if they both have simultaneous response on-send event. It will stack in an infinite loop.
As an add-in developer, the root cause looks like, event.completed({allowEvent:true}) not only end add-in but also send an 'send' event out. This will trigger a non self sending event response.
I have a published/certified MS Outlook Add-In on the Microsoft Store:
https://appsource.microsoft.com/en-us/product/office/WA104381281?src=office&tab=Overview
It shows Product Supported: OfficeProductForAndroid and OfficeProductForIOS. However, the Add-In only appears on IOS devices (as well as Desktop, OWA, etc).
How can I get support to know why the Add-in does not appear on Android devices?
PS - it does work by adding our XML staging manifest directly. And other public store Add-Ins are working.
In mobile(iOS and Android) add-in need to be whitelisted to show on Add-in Management Screen if it is not installed manually or not installed at all.
Whitelisting of Add-in is done by our team on request. I think franConnect has been whitelisted. Soon it will start coming on Addin Management Screen.