Configuring iManage Software
An issue with iManage Integration for Office, a Word add‑in distributed with some versions of iManage FileSite and DeskSite, can cause Word to temporarily become unresponsive when documents close while using Contract Tools. A solution is available in versions of iManage Integration for Office distributed with FileSite and DeskSite 9.3.5 and later.
When a document closes, iManage Integration for Office sets the property of a range (similar to a selection in Word) to the property’s current value. In computer programming, this is called a self-assignment. A self-assignment typically has no effect, but in this case, it causes Word to perform a time-consuming and unnecessary task with data that Contract Tools uses to sync defined terms, drafting errors, and other items with documents while there are unanalyzed changes. As a result, Word may temporarily become unresponsive.
iManage tracks this issue using reference number NT‑72170. For more information, see Quick Update CSAR-2626 for FileSite and DeskSite 9.3.5 with Office Integration, available at https://imanage.com.
With versions of iManage Integration for Office distributed with FileSite and DeskSite 9.3.5 and later, you can resolve this issue by creating this Registry value:
You create this Registry value in the HKEY_LOCAL_MACHINE hive. The key path of this Registry value depends on whether you use 64‑bit or 32‑bit software.
If you use the 64‑bit version of Windows with 64‑bit versions of iManage software, or the 32‑bit version of Windows with 32‑bit versions of iManage software, the key path is SOFTWARE\Interwoven\WorkSite\8.0\Integration\Options.
If you use the 64‑bit version of Windows with 32‑bit versions of iManage software, the key path is SOFTWARE\WOW6432Node\Interwoven\WorkSite\8.0\Integration\Options.
See Finding Windows Version Information to learn how to find information about your version of Windows.
Use Registry Editor; visit Open Registry Editor in Windows 10 to learn more.
Use a file with the .reg filename extension (known as a REG file, Registry Entry file, Registry Entries file, Registration Entry file, and so on). For example, create a file named iManageRemoveRangeSelfAssignment.reg with the following contents:
Windows Registry Editor Version 5.00
Then, double-click iManageRemoveRangeSelfAssignment.reg in File Explorer to create a Registry value. Visit How to add, modify, or delete registry subkeys and values by using a .reg file to learn more.
Use PowerShell or Command Prompt. For example, enter in PowerShell:
or in Command Prompt:
=HKLM\SOFTWARE\Interwoven\WorkSite\8.0\Integration\Options reg add
%keyPath%/v RemoveRangeSelfAssignment /d Y /f
If you use versions of iManage Integration for Office distributed with FileSite and DeskSite 9.3.4 or earlier, see Closing a Document Takes a Long Time When Using Multiple Add‑Ins for alternatives to creating a Registry value.