To WorldWide Support | Right Click to Bookmark

Introduction

This document describes conditions and issues you should be aware of when installing, configuring, and using the IDM Desktop 2.0.1 software. The standard operation of IDM Desktop is described in the online help that accompanies the software.

Users of the IDM Desktop 1.0 product should refer to the "What's New" sections of the online help for information on new features and other significant changes to the product.

Users of the IDM Desktop 2.0 product should refer to the "Changes Since 2.0" section of this document for information on changes incorporated into the 2.0.1 version of IDM Desktop.

Changes Since 2.0

Installation of IDM Desktop no longer requires the presence of Microsoft's Internet Explorer product. However, when running on Windows 95 without Internet Explorer installed, actions such as copy, paste, rename, or drag and drop, might not be reflected in the Windows Explorer interface until you press the F5 refresh key.

Modifications have been made to the setup program to make the installation and configuration of IDMIS catalogs more intuitive.

Closing all applications on a workstation now properly logs the user off of the IDMIS catalog.

Support for the following file formats has been added for viewing documents stored in IDMIS library systems:

Corel Draw versions 3, 4, 5, 6, and 7

Micrographx Designer

Autocad drawing versions 12 and 13

IGES drawing

Adobe Illustrator postscript

Document retrieval will no longer fail with the error 0x4d00000a "<77,0,10> CSM: No such object" if the alternate server cache is specified to be on a different IDMIS Server than the one containing the document.

IDM Desktop no longer unexpectedly converts Date property values entered in dd-mm-yyyy format to display in mm-dd-yyyy format for any of the first 12 days of any month. For example, IDM displayed 06-02-1998 (6 February, 1998) as 02-06-1998, even though the user had his machine set to display in dd\mm\yyyy format and the library system database stored the date as 06-02-1998 as expected. This problem did NOT occur for any date later than the 12th day of any particular month.

IDM Desktop no longer fails with an "Invalid Page Number" errors when retrieving documents.

Multiple problems related to large (greater than 10 digits) FPNumbers have been corrected.

The ListView OCX will correctly format numbers with a large number of digits.

If calling PropertyDescription.FormatValue(), passing in a double type, the number will be correctly formatted up to the precision allowed by a double.

Note that since FPNumbers can provide greater precision than can be represented in a double, you should program using the IDM FnFPNumber object if you require a large number of digits for a particular field (greater than 15 digits). In particular, simply calling the Value property of a Property object will return a double type that may lose precision:

val = oDoc.Properties("bignum").Value

Instead check if the property is an FPNumber and access it as an FnFPNumber object:

Set oProp = oDoc.Properties("bignum")

if oProp.PropertyDescription.GetState(idmPropSupportsFPNumber) then

set oFPNumber = oProp.FnFPNumber

' access FPNumber ...

end if

A user can now enter as many characters as specified as the maximum for a user defined string field in the Document Properties.

The following corrections have been made for COLD documents:

The right side of COLD mixed documents were truncated in IDM Viewer and local print output.

COLD file templates and data did not always match when printing.

 

General

IDM Desktop has been qualified to run on Windows 95 and Windows NT Workstation 4.0 operating systems. Information on required enhancements for Windows 95 and Windows NT 4.0 environments is listed in the Admin_D.hlp file. This help file is located on your IDM Desktop CD.

IDM Desktop 2.0 has been certified with ActiveX Data Objects (ADO) version 1.5 only, not with ADO 2.0. The installation process will automatically install ADO 1.5. Any projects that use IDM objects that reference an ADO object will require recompilation. Please refer to the "What's New" topic in the IDM Toolkit Help (npocx.hlp) for further details.

If you are using Visual Studio (Visual C++, Visual Basic, etc.) to develop applications, install Visual Studio 97 Service Pack 3.

IDM Desktop has not been qualified to run on the same machine as IDM Image Services or IDM Document Services.

 

IDM Server Services (IMS and Mezzanine)

Information for server software requirements is covered in the Admin_D.hlp help file. This file is located on your IDM Desktop CD. Here are some updates to that information:

IDM Desktop 2.0.1 is certified against the following IDM Document Services (IDMDS) versions:

IDM Desktop 2.0.1 English

IDMDS 4.1.3

IDMDS 4.2

IDM Desktop 2.0.1 French and German

IDMDS 4.1.3 (English only)

IDMDS 4.2.2 Windows NT, MS SQL Server edition (French, German, Japanese, Korean)

The IDM Desktop Setup program has been modified to allow easier selection of the database client type(s) to communicate with IDMDS 4.1.3 and/or IDMDS 4.2.x library systems. You may select multiple database client types for IDMDS 4.2.x library systems only. Depending on the library system version(s) and database type(s) you select, Setup for the English IDM Desktop 2.0.1 installs the IDMDS 4.1.5 and/or 4.2.1 client library files. Setup for the French and German IDM Desktop 2.0.1 installs IDMDS 4.1.5 (English only) and/or 4.2.2 client library files.

When you create and save searches in IDM Desktop, the IDM Document Services (IDMDS) library system saves them as Item objects in the database, not as Search objects (as is the case for stored searches in Saros Document Manager and FileShare). As a consequence, when you use IDMDS utilities such as SRDELETE or ARCHDATE, you may inadvertently affect the Item objects that store IDM Desktop search information as well as the Item objects that store typical document information. Likewise, programmers using the IDMDS API must be aware that a delete operation on Item objects may also delete IDM Desktop searches.

As stored searches are saved with the current servername and systemname, changes to the IMDDS systemname will cause to the stored search to fail. Users will need to recreate the stored search using the new systemname and servername.

WorkForce Desktop (WFD)

IDM Desktop can coexist on the same PC as WFD 5.02. FileNET does not support the coexistence of IDM Desktop and WorkFlo Controls within the same application. WFD must be installed first; otherwise the WFD setup program unconditionally installs older DLLs on top of newer versions that were installed by IDM Desktop.

Saros Document Manager (SDM)

IDM Desktop can coexist on the same PC as Saros Document Manager (SDM). IDM Desktop does not support SDM smart folders, Document References, and legacy Mezzanine stored searches. Stored searches saved using the Mezzanine API cannot be accessed via IDM.

Panagon Capture

Panagon Capture release 2.0 is required for coexistence and cohabitation with Panagon IDM 2.0.1. Coexistence means that both products are running on the same PC as native independent applications. Cohabitation means that controls from both products are embedded (i.e. "living together") in the same application.

Panagon Print, Panagon Fax, WorkFlo/Print

IDM Desktop 2.0 has been qualified with the Panagon Print 4.0 and Panagon Fax 2.0 products.

FileNET WorkFlo/Print 3.0.3 is also qualified with IDM Desktop; however, this version does not properly print stamp, arrow, and pen annotations. Contact the FileNET Customer Support Center for the latest software updates.

Cross-catalog remote printing is not supported.

Replication Services

IDM Desktop supports IDM Replication Services that installs with IDM Document Services 4.2. Use Saros Document Manager 4.2 to administer IDM Replication Services.

Panagon Visual WorkFlo

You may use IDM Desktop and Visual WorkFlo (2.0 and 3.0) to develop custom applications. IDM 2.0 has been qualified to coexist on the same platform as Visual WorkFlo 2.0 and 3.0 client products. IDM 2.0 and Visual WorkFlo 3.0 now utilize a shared logon mechanism to Panagon IDMIS libraries.

IMS Connect

In a client-server environment, IDM Desktop 2.0 includes support for IMS (IDMIS) documents that have been linked (cross-cataloged) to a Mezzanine (IDMDS) library system, via the IMS Connect for Mezzanine product. When a document link within the Mezzanine library system is opened, the target document from the IMS catalog will be retrieved and displayed. Web access to these document links is not currently provided.

Upgrading from IDM Desktop 1.0

If you are installing on a machine that currently has the IDM Desktop 1.0 product, you must first uninstall IDM Desktop 1.0. Failure to do so will result in the following errors:

During installation, you will encounter "Error 401. String variable not large enough for string. Check the string declaration".

When attempting to logon to a catalog, you will encounter "Unable to logon, error <id>.

When invoking the Viewer Application, it will fail with "This program has performed an illegal operation and will be shut down."

To uninstall IDM Desktop 1.0, close all active programs or reboot the system. Use the Add/Remove Programs utility from the Windows Control Panel to remove the following:

FileNET Mezzanine Client Libraries (for clients with DS Services only)

FileNET Panagon IDM Desktop

Reboot the system before installing the IDM Desktop 2.0 product.

Note: The uninstall process will remove the library server configurations on the desktop. They will need to be reconfigured after installing IDM Desktop 2.0.

If you are installing on a machine that currently has the IDM Desktop 2.0 product, you must first uninstall IDM Desktop 2.0. To accomplish this, close all active programs or reboot the system. Use the Add/Remove Programs utility from the Windows Control Panel to remove the following:

FileNET Panagon IDM Desktop

FileNET IDM DS Client Libraries 4.1.3

FileNET IDM DS Client Libraries 4.2

Reboot the system before installing the IDM Desktop 2.0 product.

Before installing IDM Desktop on a client PC, make sure the PC can communicate over the network with the machines that will act as IDM servers. You can use Ping tools to verify these connections.

Before running the Setup program, shut down all active programs, including virus protection software and the Microsoft Office Toolbar.

Run the Setup program on the IDM Desktop CD.

If the IDM Document Services files were previously installed in your system directory or in a folder on your path, Setup will prompt you to remove the following files from that location:

srs3mapi.dll

srs3sys2.dll

srs3mez2.dll

srs3bsi2.dll

srs3db2.dll

srs3sni2.dll

Responding "No" to the any of the prompts will terminate Setup.

If you select use with Document Services (IDMDS) in the installation, Setup will display a Specify Databases screen. Select the version(s) of IDMDS library systems you want to access. Select one or more database types for the 4.2.x Document Services servers to which you will connect. Setup will install the database software selected. If it detects that the selected database software is already installed on your system, it will attempt to update it if required. You can select only one database type for use with servers running Document Services 4.1.3. This selection will allow connection to Document Services of this single database type only.

I

If setup detects older versions of both Oracle and Microsoft SQL Server database client files, you may be forced to exit and remove the Microsoft SQL Server files. This will occur only when you select a database type other than Microsoft SQL Server.

Before uninstalling IDM Desktop 2.0.1, close all active programs or reboot the system. Using the Add/Remove Programs utility from the Windows Control Panel, remove the following:

FileNET Panagon IDM Desktop

FileNET IDM DS Client Libraries 4.1.3

FileNET IDM DS Client Libraries 4.2

If you should ever need to reinstall IDM Desktop, make sure to uninstall it first.

Users can configure multiple IDM Document Services 4.1.x library systems only if all systems have the same underlying database type. If an attempt is made to reinstall IDM Desktop and configure a library system that has a different underlying database type, access to those previously configured library systems will be disabled.

IDM integrated application examples are provided in the \Office97 directory on the IDM Desktop 2.0 CD-ROM. You can use them to integrate IDM Desktop functionality into Microsoft Office 97 applications.

Refer to the Office97\readme.doc for more information on application integration and installation.

For supported file formats, refer to the IDM Viewer help (idmdsktp.hlp).

To view the end user help files as standalone help (not from within an application), choose Help from the FileNET Panagon IDM menu (on the Windows Start menu). To view the SDK help files as standalone help (not from within the VB object browser), open the Npocx.hlp file.

When running Setup, selecting the Developer installation option installs sample applications.

The Visual Basic samples require Visual Basic 5.0 and Service Pack 3. The C++ samples require Visual C++ 5.0 and Service Pack 3.

The Visual Basic HRDemo sample requires the Panagon Integrated Workflow (Ensemble) product to be installed.

Software Problems and Restrictions

When installing IDM Desktop on a Windows 95 system, you may encounter the message: "Version conflict MFC40.DLL Your version = 4.1.6139. Keep your version? Y/N?" You should reply Yes to retain the more recent version of the MFC40.DLL. If you respond NO, an older version of MFC40.DLL will be installed.

When installing the IDM Desktop Developer environment, you may encounter the error: "The ordinal 6451 could not be located in dynamic link library MFC42.DLL". This will happen if the Visual Studio Service Pack 3 was not previously installed.

After checking out/in numerous versions of a document from an IDM Document Services library system, Windows 95 clients may automatically reboot. This problem was experienced only on machines with a 3Com Fast Ethernet XL PCI card running Windows 95 v4.00.950b(OSR 2). Remedy this problem by installing the latest drivers from 3Com. The 3com web site for the drivers is http://support.3com.com/infodeli/tools/nic/Fast_EtherLink_XL.htm. Similar problems may occur with other drivers. Contact the card manufacturers for updated drivers.

Applications

When you use the IDM Configure program to add or remove libraries, your changes will not appear in FileNET Neighborhood until you press F5.

When running on Windows 95 without Internet Explorer 4.01 (or later) installed, creating a new folder, or actions such as copy, paste, rename, or drag and drop, might not be reflected in the display until you press the F5 key to manually refresh the Windows Explorer.

If you delete the local copy of an IDM Document Services document on checkin, or if you cancel the checkout, you need to refresh the display by pressing F5 before you can view documents using IDM View from the shortcut menu.

You can file documents that are in the library but not in a folder from the Find Application by copy/paste or drag/drop from the search results.

If a user is concurrently logged into a library via Explorer and other applications, they will not be successful in logging off the library through Explorer until the other applications are closed.

Viewer Application

Depending on the image type, the background color of an image might appear slightly different from the color selected.

For documents displayed using the INSO Outside-In technology, annotations and splitter bars are not supported. In addition, landscape documents might sometimes appear in portrait mode.

Objects

Annotation Object

On the Web client, newly created stamp annotations use <webuser> instead of the IS logged on username.

GranteeType for annotation permissions always returns 0.

Annotation permission settings are not validated until the annotation is saved.

Permissions settings for annotations created on the client/server are the same settings as for the default group for the currently logged on user. On the Web, the default security is set to (ANYONE).

Document Object

For IDM Document Services documents, checking out documents from the Versions tab will not refresh the checked-out icon shown in the Explorer right pane or in IDMListView. In Explorer, select F5 or View Refresh to update the icon.

When using the idmSendWithUI option, users will have to enter their passwords. When using the idmSendNoUI option, the call will fail if the user is not logged on to the mail system

The Document SendTo Automation method does not support the "BCC" option in email.

From the Versions tab of the Document Properties dialog, clicking on Properties from the context menu of one of the versions brings up the same Properties dialog. Any modifications to properties on the second dialog might not be reflected in the IDMListView or Explorer right pane. In Explorer, select F5 to update the view.

IDM Image Services (IMS) 3.4 provides enhanced support for storing and launching non-image data types. A new system index, f_docformat, stores the original filename and extension of files. This is used to launch the native application when the Open menu is selected.

On IDM Document Services, the collection returned by Doc.FoldersFiledIn will include all folders, even if the current user does not have security access to some of the folders. In IDM Desktop 1.0, these folders were not included in the collection.

 

ObjectSet Object

ObjectSets returned from Panagon IDM automation interfaces (e.g., Folder.SubFolders) let you add an object to the collection, but adding an object to the collection can cause errors. If your VB application creates its own empty ObjectSet you can add objects to it.

Property Object

IDM Document Services date/time properties are not validated against their CVLs.

Query using ADO

When querying IDM Image Services libraries, you are restricted to a single query per process. Within your application, you must complete the first query by either calling RecordCount, requesting an ObjSet, or destroying the ADO object.

ADO is logging an unknown error when the connection to the database is being made. This error is not trappable with an error handler and is simply added to the ADO object's error collection. The error can be seen using Visual Basic's Locals Window at design time.

Queue Objects

Refer to the "What's New" section of the online help for information on several new features relating to Queues.

Controls

IDMListView Control

The IDMListView's "in-place rename" triggers a DoLabelEdit event. From that event, creating a modal dialog box will cause the application to hang. As a workaround, you can display a message box.

IDMTreeView Control

Using the right mouse to select an item in the IDMTreeView might result in the appearance of multiple items being selected.

IDMQuery Control

Advanced searches for DS documents using comparative operators on multivalue custom properties will return multiple instances of items.

Currently, invoking the Simple Find Stop button will only function if it is invoked within 5 to10 seconds after initiating the query.

 

IDMViewerCtrl Control

When you add a document from the IDM Viewer to an IDM Document Services library, the document will get added but removing the local copy will fail.

When viewing COLD documents with a background image, the scroll bar is not usable. You can navigate through the document via the page up/down keys or arrow keys.

Miscellaneous

Drag and Drop, Cut, Copy and Paste

The paste operation fails if the copy was done in a different process. For example: run a Visual Basic application and copy a folder object to the clipboard. Shut down the Visual Basic application, then start it again and attempt to paste. The paste operation will fail.

Explorer does not support moving documents or stored searches with drag and drop or cut and paste. Copy operations are supported.

Cut is not supported for any objects in Explorer, IDMTreeView or IDMListView.

Copy/Cut/Drag of a local file from Explorer into a library residing in a Visual Basic application's IDMTreeView or IDMListView will not work unless the library is logged on.

Ensemble Integration

Routing a document using a workflow that contains Panagon documents will fail with the following message if you have not logged on to the libraries. "Ensemble Author detected workflow errors. Click Cancel to exit this wizard. You must run Ensemble Author to correct these errors." To avoid this error, you must log onto the libraries prior to running the workflow.

Error Handling

For objects that have been implemented to support dual interfaces, two similar error records might be placed on the error stack.

IDM Launch Application for IMS Connect

Documents that are cross-cataloged from IDM Image Services servers to IDM Document Services servers using IMS Connect have a file extension of .ims. When viewing .ims documents from the IDM Viewer application, use the "Open" command from the context menu to open the documents. The IDM View option from the context menu and "double-click" features are not supported with .ims documents, and will only display the .ims file content instead of the actual image.

When viewing properties of .ims documents from IDM Viewer, be aware that they are not write-protected by the current application. Any user that has the proper access rights can go into the Properties tab and change the values of the document's properties. The same is true of document annotations. They can be added, modified, or deleted while users are logged on to the IDM Document Services server from an IDM Viewer desktop.

When printing .ims documents from the IDM Viewer application, first display the document using the "Open" context menu item, and then select File/Print to print the document. The "Print" context menu item is not supported with .ims documents. Selecting the print command from the context menu will print the .ims file content rather than the image.

Documents of .ims type are not stored in the Recent File list in the IDM Viewer after they have been opened. To toggle between .ims documents that are currently active, go to the Window dropdown menu and select a document from the list located at the bottom of this menu.

Local Cache

The local cache for viewed documents is not always cleared when logging off all applications.

It is recommended that your cache size be at least as large as all of the documents being viewed at the same time within the IDM Viewer or native applications.

Local Printing

Printing fax images in 'scale to width', 'scale to height', or 'whole mode' might not print properly.

Logging Off

A workstation might still be logged on even if all IDM processes have been logged off. Use the "Close all programs and logon as a different user" command from the Start/Shutdown menu in Windows to ensure that no logon sessions remain open.

Logging

It is possible to configure logging such that several thousands of messages get generated. When this occurs, the environment may appear as though it has stopped responding. The environment will eventually respond. This situation can be avoided by selectively enabling the logging options.

Multiple Selection

Multiple selection operations in IDMListView, IDMTreeView and Explorer are not supported.

^© 1998 FileNET Corporation USA. All rights reserved.