Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

The Wedia Office 365 is a web application that contains dedicated code that handle interactions with an Office 365 host software, such as Word, Powerpoint and Outlook.

The Office 365 Content Picker is only available on

  • Window 10,

  • Windows 11,

  • MacOS X.

Please note that we require Microsoft 365 version published after the version 16.0.13530.20424 released on Mar 09, 2021.

Please note that you will need to complete one installation for Word / Excel / Powerpoint, and another one for Outlook, as they don’t share the same manifest.xml structure.

But both manifests point to the same code and configuration files, it is just the manifest that changes format.

To use the Office 365 Content Picker, system integrators must make sure that the Wedia server is set to :

  • REST API : Cookie same site option must be set to none

  • in the HTTP SECURITY HEADERS options : make sure that in the Framed options, the xframedOptions.enabled is set to unchecked for the following urls :

  • /office-picker/office-asset-picker.html

A complete documentation for system integrators is available here : Content Picker Microsoft Office 365 Configuration

To use the online version of Office 365 with the Wedia Content Picker, please make sure that the browser your users will be using accept third party cookies. Please note that on most browser, the “incognito mode” is rejecting third party cookies : you will not be able to log in to the Wedia Content Picker in that case

In order to give access to your internal users, you need to install the Wedia Add in in your Office 365 Tenant.

You will need proper rights to follow the installation process.

Step 1 — Connect to your tenant administration Add-In management page

Here is the link to follow : https://admin.microsoft.com/AdminPortal/Home?#/Settings/AddIns

You can also find the Add-ins option in : Settings / Add-ins menu.

Step 2 — Follow the Deploy Add-in Wizard.

Click on the “Deploy Add-in” button

Click “Next” to get past the welcome screen.

We’ll be using the “Upload custom apps” option : the Wedia Content Picker is unique to your organization, and is running in a dedicated container in the Wedia infrastructure.

When clicking on this option, you will be prompted to upload the manifest file :

Please ask your project manager at Wedia to get your personalized manifest XML file, and to upload it by choosing the first option “I have the manifest file on this device”.

There are two different manifest.xml files, one for Outlook, and another one for Word / Excel / Powerpoint. You will have to follow this process twice in order to install the two add-ins.

Wedia project managers can find the manifest.xml files in the /samples/office-picker-confi-sample directory in our internal git directory. Please ask to Product team for any question related to configuration of these xml files.

Users with a git access can follow this link. https://bitbucket.org/wediaproduct/portal/src/master/samples/office-picker-config-sample/manifest-dev-club-wed.xml

If the upload is successful, a recap screen will show you this plugin screen :

In that screen, you can choose who will see the plugin in their Office 365 toolbar (see Wedia Office 365 Content Picker for user installation)

The deploy can take some time :

If the deploy is successful, a message inviting you to test the installation will appear :

Updating who can see the plugin in their Office apps :

To change who will see this application in their Office ribbon, you can click on the Plugin line to change the visibility options :

This can also be used to disable the add-in completely.

Validate the manifest.xml

You might encounter an error when deploying manifests if they are not valid. You can get detailed explanations to know how to correct your manifests.

Given node is installed on your machine, you can run the following command:

npx --ignore-existing office-addin-manifest validate <PATH_TO_YOUR_MANIFEST_FILE>

Detailed explanations can be found at https://docs.microsoft.com/fr-fr/office/dev/add-ins/testing/troubleshoot-manifest

  • No labels