IBM Docs 2.0 CR1 iFix 001 Available

Since a few days Docs 2.0 CR1 iFix 001 is available for download from the Fix Central, it includes the following Fixes:

  • Resolution of broken Korean text input issue in Documents editor
  • Resolution of inconsistent Print function behavior across editors
  • Adding configuration tags to LotusConnections-config.xml during IBM Docs installation to resolve the issue of being unable to preview files

Prior to installing this iFix you need to install CR1 for IBM Docs 2.0.

Official Release Notes to IBM Docs 2.0 CR1 iFix001.

Download

Updated IBM Connections Plug-ins available

Recently, new Versions of Connections plug-ins were released in IBM Greenhouse.

IBM Connections Desktop Plug-in for Windows & IBM Connections for MAC, Version 16.8

The new Version adds a new feature:

(BETA) – a new authentication method called “Web Forms Authentication”

 

IBM Connections Plug-in for Microsoft Outlook, Version 16.8

Adds miscellaneous defect fixes.

IBM Connections Plug-ins for IBM Notes, Version 5.5

Supports the ability to work with both personal and community owned files organized in multi-level nested folders.

Issue with IBM Connections plug-in for Notes

If you have more than four locations configured in Notes with two or more different User IDs, you may experience a rather strange bug in correlation with Notes Connections plug-in.

After the installation of the Connections plug-in for Notes, you will need to enter your connections credentials and save them. So far so good. The Problems start when you save your credentials in four or more Notes locations, involving two or more user IDs. After you change then from one Location to another, changing the ID-File, your client will lose all your saved Connections credentials for Notes Connections plug-in and you will have to type them in all Notes locations again.

This problem was reproduced with IBM Notes 9.0.1 Fix Pack 6 and the latest Version of Connections plug-in for Notes (5.5.0.20160818-0653).

If you are also experiencing this Error, open a PMR and reference the following APAR: “LO89513”.

Hopefully there will be a fix for this problem soon.