Is there an option in the manifest.xml to stop the Add-In from appearing in the OWA app ?
It appears that FormSettings is a mandatory field, and at least one Form is required.
There are some functional parity issues with OWA (e.g. UI-less action, TaskPane for EditItems) that push us to forego having it there.
Thanks!
Currently the feature : "showing add-in on specific platform"
, you requested, is not a part of the product. We track Outlook add-in feature requests on our user-voice page. Please add your request there. Feature requests on user-voice are considered, when we go through our planning process.
There are no options currently. You may post your feedback or request on the UserVoice page.
Related
I maintain an application written in C++Builder 2009. Part of it involves using a TWebBrowser control (based on Internet Explorer) to send users to a Google login page in order to obtain an OAuth key. This has worked well for a while, but now Google, bless their hearts, has implemented some kind of security upgrade, and now my users get to a page that says "Couldn't sign you in, this browser or app may not be secure". FYI, I am already setting a Registry key that is supposed to make IE run in version 11 emulation mode.
I do have a couple of workarounds: If the user runs IE first in admin mode, signs on, leaves it up while running my application, we don't get the problem. Second, I can start up the default browser - Chrome, IE, whatever - and send them to the URL for OAuth, then it avoids the error message.
The problem with this solution is that without being able to hook into TWebBrowser events, I don't have any way to automatically retrieve the OAuth key - it is necessary for the user to cut/paste it into my application. I'd like to avoid these clunky solutions.
I should also mention, this problem occurs only for certain Gmail accounts. I have no idea what the difference is between accounts that work and don't work. Any ideas on that?
So, is there any way to configure IE or TWebBrowser so this security issue is bypassed? Or, if I was to update to a modern version of C++Builder and use TWebBrowser (or something else?), would this problem be avoided? Any other ideas to fix this problem?
The latest C++Builder supports Google's Chromium engine, it's probably safe to say it'll be compatible with Google's security upgrades.
Powerful Chromium Based WebView Component To Host Web Content In Your Delphi/C++ Builder FireMonkey Apps
G-Suite has an email audit api where admin can create an audit monitor on the source user. All the emails TO and FROM source user will be forwarded to destination user in MIME format. Does outlook also have any such API's to audit emails? I went through the documentation and looks like it's just audit logs but not email forwarding. I am pretty new to outlook and this feature is very critical to developing our Add-in.
Any help around this is greatly appreciated.
Currently the feature you requested, is not a part of the product. We track Outlook add-in feature requests on our user voice page . Please add your request there. Feature requests on user-voice are considered when we go through our planning process.
When you open a dialog using the office.js Dialog API from your add-in, apparently the page opened has to be from your add-in's domain. It can however immediately redirect to a page in another domain.
How would you recommend carrying out such a redirection?
Is anyone redirecting to another domain from such a dialog? If so how are you doing it and what have been your results?
Thanks.
How you do it depends on the framework you are using. This ASP.NET MVC sample does it in a controller with a call to the ASP.NET Redirect method.
This single page add-in sample uses the JavaScript window.location.replace property.
When opening dialog from my add-in using Outlook Web App on iOS, I receive an error. In Windows the solution is to add the site as trusted but how do I do this in iOS? The help link redirect to help for IE 11
You need to add the domain to the AppDomains section of your add-in's manifest file.
<AppDomains>
<AppDomain>https://www.northwindtraders.com</AppDomain>
</AppDomains>
Fixing this in your manifest should resolve this issue across every client. You shouldn't need separate manifests for each platform, add-ins are designed to be cross-platform by nature.
Outlook on the Web for iOS and Android (any Mobile browsers) currently supports API Requirement Set 1.3 and Office.context.ui.displayDialogAsync() is in API Requirement set 1.4. Outlook on the Web in desktop browsers supports API Requirement set 1.5. It is a known issue that Outlook on the Web on mobile browsers is reporting the wrong requirement set support.
Mark, I have configurated the AppDomain but the problem continue. When I try open the login dialog with Office.context.ui.displayDialogAsync
manifest
The dialog is opened in safari but the addin in owa show the picture previous. The dialog after that send user and password should be closed but this not succedd.
I think this happens because of the message I have in the addin. In IE I happened this same but I could configure it with the help page, but in OWA for IOS I do not know how to do it
I have a SharePoint 2010 web application migrated to SharePoint 2013. this is a classic mode web application, we are not using claims, my client doesn't wants it ( Don't ask why?).
I had other web application migrated as same process but i can add users in them.
but in this i am not able to.
I can add users and find users in the web application in central administration. But not in the web application itself.
I am not sure what changes i have to make so that it starts picking or finding users from the people picker. any ideas.
it was because of the asp.netvalidation=2.0 not present in the httprequest line in webconfig. there was no validation for the input provided in any input box.
once we added the asp.net validation it worked fine.
It is a browser compatible issue as well whereas in new browser like IE 10 and other latest browsers it doesn't play well.
we updated the
In short the fix is to edit the pickerdialog.master file in notepad and add a meta data tag, , to the header section.
well keep in mind always save a local copy of your original master page.
it is recommended not to update any original files, we can run the site in compatible mode too.