top of page

IM Highlights December 2019

iManage Seminar
We recently held Seminars in Perth and Brisbane where we introduced important updates to the iManage solution portfolio designed to help users securely access, share and leverage information while working the way they want to work. 
To check out videos from the seminar click here.
Project Mantis Deliverables
The delivery timeframes for the Mantis feature set has been updated by iManage. Some key features and their target timeframes include:
  • Grid view with sortable columns – GA: Q1 2020

  • Tree View (Navigation only) - Coming soon: Q1 2020 GA: Q2 2020

  • Tree operations (Drag & drop within tree) - GA: Q2 2020

  • Delete multiple documents - GA: Q1 2020

For full detail click here.
Microsoft is retiring TLS 1.0 and 1.1
As of June 2020, Office 365 will begin deprecating TLS 1.0 and 1.1 in worldwide environments.  This means that starting in June 2020, any commercial and Government (GCC clients), devices or services that connect to Office 365 by using TLS 1.0 and 1.1 will not succeed. For more information click here.
How will this impact your iManage environment? As of Work Desktop for Windows, TLS 1.3 has been officially supported. Work Communications Server 9.x/10.x uses TLS 1.2 out of the box. The Work Server and classic desktop clients (FileSite/DeskSite) do not connect to Office 365 and therefore are unaffected. If you want more information about how this may affect other systems within your environment, please contact support. 
Recent iManage Releases
     - Tooltip to toggle between List and Grid view
     - Support for exact phrase searching in Simple Search
     - Setting default scope for simple search to title or keyword
     - Self-hosting product documentation
     - Viewing documents and emails with keywords highlighted
      - Copying the link of a document opened from iManage Work
      - Inserting Custom Fields in the footer in Microsoft Word documents
      - Localised email templates
      - OAuth 2.0 support for authentication (see Tips and Tricks below for more information)
      - Copying and moving Outlook folders to iManage Work supported for client-side filing 
Upcoming iManage Releases
iManage Cloud Quarterly Service Updates and Maintenance 
New iManage Technotes and Known Issues articles available in Help Center
iManage Tips & Tricks
Where has the Local Save As option gone in iManage Work Desktop 10.x?
​With the Classic clients, iManage recommend using the iManage Local Save As, to ensure the iManage file is released once the user does the local save. But starting with Work Desktop for Windows 10, it is no longer required to use the iManage Local Save As in order to save documents locally - users can use the Microsoft Save As button to save documents locally. You can expose the Local Save via the XML files and then add to the QAT if desired, click here.
Alternatively, you can simply educate users to use the native save to save locally.  At this stage iManage have no immediate plans to re-introduce the iManage Local Save back into the Work Desktop application, as the native MS Save As provides the same functionality and the intent is to keep the Work 10 client as simple as possible.
IWL prompt in Chrome upon opening documents from the web interface
When opening a document from the Work 10 web interface, users may receive a prompt to open the IWLNRL protocol.  In earlier versions of Chrome, there was a checkbox available on that prompt so that users only had to accept it once, however in later Chrome versions, this checkbox does NOT appear.  This has been acknowledged as an issue by iManage and raised with Google Chrome.  You can find more information on the following thread.
The following client-side registry key may be a workaround to this issue:
Type: String
Name: 1
Value: iwl:*
OAuth 2.0 support for authentication
The 10.2.2 and higher releases of iManage Work Desktop enhance security by eliminating the need to automatically store the user credentials in the Credentials Manager on Windows by leveraging OAuth 2.0. OAuth 2.0 is a widely used industry standard that enables client applications to use secure tokens instead of a username and password for authentication and authorization. The implementation is transparent, not requiring any action from users or administrators. When authentication is handled by OAuth, you will have to re-login to iManage Work if you restart your computer, to ensure you have the correct authorization token to access content.  If you prefer to use an alternate authentication method, this can be controlled by the PreferredLoginType registry key which is detailed in the iManage Work Desktop for Windows Customization Guide (10.2.4).
51 views0 comments

Recent Posts

See All


bottom of page