Product Documentation
Abstract
This technote describes known problems in IBM Document Manager Version 8.5.
Content
Support for IBM Content Manager Version 8.4.3
An IBM Content Manager fix is required to properly integrate IBM Document Manager with IBM Content Manager 8.4.3. For more information, see Article 1515225.
The IBM Document Manager Client API, which is 32-bit, is not supported on 64-bit hardware unless it is called from a 32-bit process
By default, .NET applications are built to run under the native environment of the system they are installed on. This means that a .NET application built using the default setting Platform target: Any CPU will load as a 32-bit process on 32-bit hardware, and as a 64-bit process on 64-bit hardware.
The IBM Document Manager Client API is only supported on 64-bit hardware if it is called from a 32-bit process. You can enforce this in .NET applications by changing the default setting to Platform target: x86 in the project.
The cursor position cannot be controlled in a Microsoft Outlook item
The Microsoft Outlook API that IBM Document Manager uses to implement Microsoft Outlook integration does not support control of the cursor position for placement of attachments in a Microsoft Outlook item.
Invalid class attribute causes IBM Document Manager operation to fail
If you specify a value that is not valid for a document's class attribute in the Power Modify window, any IBM Document Manager operation that needs to read the class configuration will fail. The document might become unusable. If this happens, use the Power Modify dialog window to reset the class value.
Long file names are truncated
When a user adds a document to the repository, IBM Document Manager removes a portion of the document file name that is longer than a certain number of characters. The maximum number of characters varies from 166 to 214, depending on the operating system of the IBM Document Manager server and the connection protocol between the IBM Document Manager client and server.
Complex search queries with a large number of conditions can result in an error
When users perform complex search queries, IBM Document Manager sometimes returns a General Internal Error. This occurs only in some circumstances when a single query contains a very large number of conditions. For example, if users combine many OR conditions and LIKE operators in a single search query, the action can result in low search performance or an error.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27019920