Table of Contents |
---|
Manifest configuration
You should now have a working OC website. Please visit the URL of the installed site in a browser and check that the OC loads.
...
Note that it is not required to configure both manifest files.
The two files are both located in the "wwwroot"-folder of the installed OC. Alternatively, the files are similar to the followingmanifest files must follow the format as follows:
View file | ||
---|---|---|
|
View file | ||
---|---|---|
|
...
Replace all references to localhost [MM_URL] with the MM site reference. E.g. if MM is installed at mm.digizuite.com, then replace localhost with [MM_URL] with mm.digizuite.com/oc. (Make sure to append /oc add the end of the mm site reference)
Change the ID to a new, random GUID.
Change the "DisplayName" (title) and the "Description" appropriately. The "DisplayName" is the title in the top of the add-in pane (red line below),
Change each “bt:Image" element if the user wants to use a different icon than the default provided (Make sure to append the image extension to the MM site reference e.g. https://mm.digizuite.com/icon.png)
Go through the labels in the manifest file and ensure that they have the desired values. In particular, the "residOpenButtenText" is the displayed title for the ribbon (blue line below).
...
Manifest deployment
To deploy the manifest and thus make the OC available for users, go through the following steps with an Office 365 admin account: https://docs.microsoft.com/en-us/microsoft-365/admin/manage/manage-deployment-of-add-ins?view=o365-worldwide
...
If an issue is encountered while deploying, please validate your manifest file with the tool at: https://github.com/OfficeDev/Office-Addin-Scripts/tree/master/packages/office-addin-manifest
Updating the manifest file
After updating the manifest file (NOTE: not after updating the website itself), a user might not see the effects of the update immediately.
...