Updating kutana+brochet office extension to use cloud imanage.com application

How does the extension connect to cloud iManage and the Word msi?

The kutana+brochet office extension uses the iManage SDK. The extension (kutana+brochet application) is pulled down to the users' iManage Plug-ins folder by the iManage Agent.
When Word is opened, the extension hooks up with the kutana+brochet Word add-in. All functionality for iManage is routed through the extension, which handles all the integration.

Do I need a new Word msi and templates?

No, there is no requirement for a new Word msi or templates. The coding behind the office extensions is the same for both the iManage work and cloudimanage.com extensions.

Steps to transition

1. Add the kutana+brochet office extension to the control center at cloudimanage.com

Here is a link to the iManage guide for adding an application to the control center at cloudimanage.com - https://docs.imanage.com/cloud/cc-help/en-US/Adding_an_application.html

Follow the steps to add the kutana+brochet office extension

TIP: When in the applications screen search for 'kutana+brochet office extension', which will then only display the relevant item

NOTE - The download of the relevant plug in files to individual machines can take a number of hours

2. Update the URL in imanwork.config

The transition from imanage.work to cloudimanage.com changes the sign-in URL for iManage Work. The URL setting is set in the imanwork.config file that needs to be updated on all user machines. This file can't be downloaded from iManage Control Center and therefore must be pushed through group policy, a software package, or manually placed on each device.

The following setting in the imanagework.com is changed as follows:

From:

<configuration>
  <SERVERNAME.IMANAGE.WORK>
    <url>https://SERVERNAME.imanage.work/</url>
    <authentication></authentication>
    <restUrl>https://SERVERNAME.imanage.work/api/v2/</restUrl>
    <databases>DATABASE NAME</databases>
    <far_databases>
    </far_databases>
    <user_id></user_id>
    <user_email></user_email>
  </SERVERNAME.IMANAGE.WORK>
  <recent>
    <server>SERVERNAME.IMANAGE.WORK</server>
  </recent>
</configuration>

To:

<configuration>
  <SCLOUDIMANAGE.COM>
    <url>https://cloudimanage.com/</url>
    <authentication>oauth2</authentication>
    <restUrl>https://cloudimanage.com/work/api/v2/</restUrl>
    <pingUrl>
    </pingUrl>
    <databases>DATABASE NAME</databases>
    <far_databases>
    </far_databases>
    <user_id></user_id>
    <user_email></user_email>
  </SCLOUDIMANAGE.COM>
</configuration>

The file is saved to the following location on the user device:

  %APPDATA%\iManage\Work\Configs\user\

NOTE: If you have have already connected and signed in to cloudimanage.com via an iManage service e.g. via Word or Outlook, then you may find this file has both configurations. In this case, remove all of the configuration elements related to SERVERNAME.IMANAGE.WORK so that only those pertaining to SCLOUDIMANAGE.COM remain.

3. Check Registry settings

Ensure that there is a registry key pointing to the location of the office extension configuration file as below (the path is specific to your installation so may not match what is shown below). This may be located at HKEY_CURRENT_USER or HKEY_LOCAL_MACHINE

NOTE: If this registry entry does not exist, it will need to be manually created.

4. Remove existing Plug_ins folder

For each user, the existing office extension plug in (the folder starting 'Brochet Ltd_') will need to be manually removed from the iManage Work Plug-ins folder or you may end up with 2 sets of Plug_ins folders, which could cause a conflict. This can be found at %AppData%\iManage\Work\Plug_ins. See below for examples of each and note the difference in name of the 2 folders.

Wiki