Critical Note, added 8/2/99: If your DS library contains documents added using Saros Document Manager or @mezzanine, see the IDMDS 5.0.0-1 patch readme file for information on using the VUPDATE.EXE utility to improve performance when searching for such documents.

This readme file contains information for both IDM Desktop and IDM Web Services.

This readme file, in HTML format and with the latest updates, is available from the FileNET CSS Web site. See Downloading Patches and Files for instructions.

The 2.0.3 SMU consists of the 2.0.2 release with 2.0.2-7 patches and support for DS 4.3 libraries. The release discontinues support for DS 4.1.x libraries and IDM Web Services on IIS 3.0. We recommend that you check for additional patches immediately after installing 2.0.3.

IDM Desktop and IDM Web Services are Year 2000 compliant. For details on compliance, see http://www.filenet.com/solutionsProducts/year2000/index.asp.

For information on installing IDM Desktop, refer to the "Install IDM Desktop" topic in the IDM Desktop Administrator’s Help. You can view this Help in any of these ways:

• By clicking on the Installation Notes button in Setup.
• By running admin_d.hlp from the root directory of the IDM Desktop CD.
• By choosing Desktop Administrator’s Handbook from the FileNET Panagon IDM menu (on the Start/Programs menu) after installation.

The IDM Desktop Administrator’s Help provides detailed information on installation, requirements and administrative functions. The IDM Desktop Help, online Help that accompanies the product, describes the standard operation of the IDM Desktop software.

Information about the SDK is provided in the npocx.hlp file, which is copied to your system during installation. This file contains reference information for the IDM objects' methods, properties, and events, as well as descriptions of the object model and "Working with…" examples. You can open the file directly to have access to all topics, or, from within Visual Basic, you can use the F1 key to access the context-sensitive reference information. For a complete listing of the documentation supplied with IDM Desktop, refer to the topic "About documentation" in the IDM Desktop Help file (idmdsktp.hlp).

You can install sample applications when you run the IDM Desktop Setup program. The Visual Basic samples require either Visual Basic 5.0 with SP3, or Visual Basic 6.0. The Visual C++ samples require either Visual C++ 5.0 with SP3, or Visual C++ 6.0. The Visual Basic sample called HRDemo also requires installation of Panagon Integrated Workflow (formerly Ensemble).

For information on installing IDM Web Services, refer to the "Install IDM Web" topic in the IDM Web Administrator’s Help. You can display this Help in any of these ways:

• By clicking on the Installation Notes in Setup.
• By running admin_w.hlp from the root directory of the IDM Web Services CD.
• By choosing Web Administrator’s Handbook from the FileNET Panagon IDM menu (on the Start/Programs menu) after installation.

The IDM Web Administrator’s Help provides information on installation, requirements, and administrative functions. The standard operation of the Panagon IDM Web client software is described in the online help that accompanies the software.

The Web client development environment includes ASP pages, a query design-time control, and the standard toolkit provided by the IDM Desktop.

For detailed information on the sample IDM Web pages, refer to the idmwbasp.hlp file. The same file contains information on customizing the search criteria and results pages using the design-time control. This file is installed on your system when you install the Web Development environment.

Highlights of Features Introduced in IDM 2.0.3

• Added support for DS 4.3 libraries, and discontinued support for DS 4.1.x libraries.
• A new event on the IDM Viewer, MagnifierWindowSizeChanged, is triggered when the Magnifier Window size is adjusted (FR 4850).
• New methods on the RemotePrintFax object provide the ability to programmatically get a list of print services and print queues for each print service and to allow the user to specify page ranges (FR 4357).
• The IDM Viewer control provides new events to support context menu viewing in IDM Web (FR 4852).
• The MaintainMagnifierSizeOnRotate property is new for the fnviewer.ocx. When used, the Magnifier window will keep its size any time an image is rotated (FR 5492).
• The Viewer includes a new Document Navigation toolbar. The toolbar buttons are Next Document, Previous Document, Next Page, and Previous Page. Paging between documents cycles through the document windows in the Viewer (FR 4386).
• Programmatically, you can now set zoom levels for the Magnifier. The Magnifier zooms independently of the zoom setting selected in the IDM Viewer window (FR 4105).
• Simple Find search results display the property columns configured for the FileNET Neighborhood (FR 4974).

Highlights of Features Introduced in IDM 2.0.2

• IDM Desktop 2.0.2 automatically installs the Microsoft MDAC 2.0 package, including ADO 2.0, OLE DB 2.0, and ODBC 3.51 (FR 1752, 2993).
• Visual Studio 6 (Visual InterDev 6.0), with Visual C++ 6.0, and Visual Basic 6.0, is supported, in addition to the Visual Studio 97 (SP3) product.
• You can copy all or part of an image displayed in the IDM Viewer to the Windows clipboard as a bitmap.
• System and SQL logging statements can be stored. The logging information is written to the file fndslog.txt in the program\files\filenet\idm\temp directory. The System and SQL logging statements cannot be viewed using Log Spy.
• Several new Queue features have been developed. See npocx.hlp for details.
• Improved the handling of TIFF documents (FR 2452, 2701, 2928, 2322, and 2941).
• Annotation of multipage TIFF documents is supported, but the annotations cannot be printed using the FileNET print services.
• Improved display of multipage TIFF documents.
• The text displayed in TIFF fax images with the zoom level set to Page Width in the IDM Viewer is now readable.
• Extra large printing of TIFF fax images works correctly.
• TIFF6 images with color can be viewed.
• The cursor now changes to an hourglass while a document is loading in the IDM Viewer.
• A new annotation property, F_MULTIPAGETIFFPAGENUMBER, stores the page number on which an annotation appears in a multipage TIFF document.
• For satisfactory readability of PDF documents, the Adobe Acrobat Reader is integrated into the IDM Viewer (FR 2165). Refer to the topics "Document formats supported by the Viewer" in the IDM Desktop Help (idmdsktp.hlp) and "Download Adobe Acrobat Reader" in the IDM Desktop Administrator's Handbook (admin_d.hlp) and in the Web Administrator's Handbook, admin_w.hlp, for more information.
• You can now specify a print range for a document (FR 2815).

• The Microsoft NT 4.0 operating system is supported with SP4.
• Performance has been improved for DS sites with a large number of web server users.
• You can view a specific version of a document through the IDM web interface (FR 1780).
• You can print a COLD Document's overlay image to a local printer using the IDM Web View COLD compressed images.
• The syntax for searching for strings using the Advanced Search feature has changed. The new syntax requires the string to be enclosed in percent signs (%). For example, to search for all documents with "Finance" in their titles, use the query title like %finance%.

Critical Notes for IDM Desktop

• IDM Desktop 2.0.2 has been certified with ActiveX Data Objects (ADO) version 2.0 and 2.01. The installation process automatically installs Microsoft's MDAC 2.0 product, which includes ADO 2.0. Any projects that use IDM objects that reference an ADO object must be recompiled.
• If you are using Visual Studio (Visual C++, Visual Basic, etc.) to develop applications, install either Visual Studio 97 SP3 or Visual Studio 6.
• IDM Desktop has not been qualified to run on the same machine as IDM Web Services, IDM Image Services, or IDM Document Services.
• When you create and save searches in IDM Desktop, the DS 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 DS utilities such as SRDELETE or ARCHDATE, you might inadvertently affect the Item objects that store IDM Desktop search information as well as the Item objects that store typical document information. Similarly, be aware that when using the DS API a delete operation on Item objects can also delete IDM Desktop searches.
• Because stored searches are saved with the current server name and system name, changes to the DS server name cause stored searches to fail. You must recreate the stored search using the new system name and server name.
• On Windows 95a systems, you must set the printer font option to "Print true type as graphics" to ensure that COLD documents will print correctly. By default, this printer font option is not set when you configure a printer, and printouts of COLD documents are misaligned.
• Multipage TIFF documents are supported only if all the constituent files contain a single-page image. The files can be different file types.
• To preserve current ORACLE connectivity information, make a copy of the TNSNAMES.ORA file prior to installing IDM Desktop. After installation, add the information from the old TNSNAMES.ORA file to the version of the file generated during the installation.
• To install IDM Desktop on a system running Windows NT, you must be logged on with a usercode with Administrator privileges.

There is no direct migration path for @mezzanine 2.0.1 users to IDM Web.

Running Panagon IDM Web Services on the same server as IS or DS is not supported.

The 2.0.3 release discontinues support for IIS 3.0.

Running IDM Web Services on a multi-processor IIS Web server may require the installation of an IIS 4.0 fix from Microsoft. Details of this fix are available at:

http://support.microsoft.com/support/kb/articles/
q196/6/16.asp?FR=0.

The Microsoft article ID is Q196616.

To enhance web server performance, IDM Web Services caches copies of documents locally on the web server. These documents are stored in a separate directory hierarchy from the IDM Web Services ASP application and from the web server itself. For security reasons, these documents are only accessible through the doccontent.dll that is provided as part of IDM Web Services. Users can access these cached documents only through the IDM Web Services client software, not through the web server directory structure.

To access a document through doccontent.dll, users must be logged on to IDM Web. In addition, they must have sufficient access rights to the document as determined by either IDM Document Services or IDM Image Services. Before a document is transmitted to a user, IDM Web Services checks the permissions collection to make sure that the user has the necessary access rights.

Because IDM Web Services maintains a local file cache on the system, FileNET recommends that you secure the NT web server according to Microsoft's recommendations. For example, the network drives should not be shared and interactive login at the console should be tightly controlled.

Web Browser Requirements

• Running Panagon IDM Web client on the same server as IS or DS is not supported.
• Users of Microsoft Internet Explorer must install the IE 4.01 SP1 (version 4.72.3110.8). You can download the service pack from the following web site:

• Users of Netscape Navigator/Communicator must install version 4.04.
• If the browser's Submit Non-encrypted Data setting is Prompt, Microsoft IE 4.x browsers add a document twice to a DS server. In addition, a dialog box appears stating "It might be possible for other people to see what you are sending. Do you want to continue?"

• Add the web server on which Panagon IDM Web resides to the Trusted Sites zone.
• Set the security level for the current zone to Medium or Low in the Security pane of the Internet Options dialog.
• Set the Submit Non-encrypted Form Data to Enable in the Custom setting.
• There is a known issue in IE 4.01 that causes error messages such as "Server Execution Failed" to appear when retrieving Office 97 documents. Details of the problem are available at the following site:

FileNET recommends that you run custom ASP applications created using the Panagon IDM Foundation Objects in the main process of the Web server. This setting is controlled on a per-application basis in the Microsoft Management Console for the Internet Information Server 4.0. On the Virtual Directory pane of the application properties dialog, verify that the "Run in Separate Memory Space (Isolated Process)" check box is not selected.

If production applications run in a separate memory space, situations can arise where the CPU usage stays at 100% indefinitely, requiring the Web server administrator to restart IIS or the machine.

On Windows 95a systems, you must set the printer font option to "Print true type as graphics" to ensure that COLD documents will print correctly. By default, this printer font option is not set when you configure a printer, and printouts of COLD documents are misaligned.

Installation

• When installing the IDM Desktop on a Windows 95 system, you might encounter the error:

• IDM Desktop installation is an interactive process, there is no silent installation for this product.
• If you install the SQL 6.5 client DLLs, older version of the SQL client DLLs will be overwritten.

After checking out/in numerous versions of a document from a DS library system, Windows 95 clients might 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:

Similar problems might occur with other cards. Contact the card manufacturers for updated drivers.

Using the Internet Explorer’s Save As command to save a PDF file results in saving an empty (0K) file.

A memory usage problem may occur when using the IDM Logon component along with other software. In particular, this problem has been reported when using the Logon component and the Rumba 5.2 OCX on the same Visual Basic form (FR 4878). There are two ways to avoid this problem in VB:

Explorer Integration

• On Windows 95, if you haven’t installed Internet Explorer 4.01 (or later), you must press the F5 key to manually refresh an Explorer window, such as the FileNET Neighborhood, to see changes made to the folder or document lists.
• Inconsistencies can occur in the state of the Logon/Logoff entry in the shortcut menu of the library icons in Explorer and in the FileNET Neighborhood windows. This situation can arise when you log on from one process and then log off from both the Explorer and the FileNET Neighborhood windows. To synchronize the Explorer and FileNET Neighborhood systems, log off and then log back on to your desktop system.
• If you attempt to create a subfolder of a top-level folder in the list view, the new folder appears as a top-level folder. To create a subfolder, open FileNET Neighborhood as an Explorer window and create the folder in tree view (the left pane).

Viewer Application

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

Annotations on multiple-page TIFF documents do not appear on the correct page.

Annotation Object

• 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

• When using the idmSendWithUI option, users must enter their passwords. When using the idmSendNoUI option, the call fails if the user is not logged on to the mail system.
• On IDM Document Services, the collection returned by Doc.FoldersFiledIn includes all folders, even if the current user does not have security access to some of the parents of the folders. In IDM Desktop 1.0, these folders were not included in the collection.

Errors and unexpected behaviors can occur if you add objects to collections using the ObjectSets returned from Panagon IDM automation interfaces (for example, Folder.SubFolders). Instead, create an empty ObjectSet in your VB application and add objects to this ObjectSet.

ADO logs an unknown error when the connection to the database is being made. This error cannot be trapped 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 run time.

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 returns multiple instances of items.
• Currently, the Simple Find Stop button works only if it is invoked within 5 to 10 seconds of initiating the query.

IDMViewerCtrl Control

• When you add a document from the IDM Viewer to a DS library, the document is added but removing the local copy fails.
• When you view a COLD document 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.

Drag and Drop, Cut, Copy and Paste

• The paste operation fails if the copy was done in a different process. To demonstrate this problem, 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 fails.
• IDM Desktop does not support moving library documents or stored searches with drag and drop or cut and paste in an Explorer window. Copy and paste 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 does not work unless the library is logged on.

If you have not logged on to the appropriate library, routing a document using a workflow that contains a library document fails with the message "Ensemble Author detected workflow errors. Click Cancel to exit this wizard. You must run Ensemble Author to correct these errors." To avoid this error, log onto the library prior to running the workflow.

For objects that have been implemented to support dual interfaces, two similar error records might be placed on the error stack. This problem is caused by a Microsoft OLE DB problem for which no fix is currently available.

Documents added to legacy DS 3.x systems will not have a valid Version Filename until they are checked out and then checked back in after upgrading a DS library to 4.x or later. On checkout the user must manually enter the correct filename in the Checkout File To dialog box (FR2576).

The local cache for viewed documents is not always cleared when logging off of all applications. Ensure your cache size is at least as large as all of the documents viewed at the same time within the IDM Viewer or native applications.

Printing fax images in scale to width, scale to height, or whole mode does not always function correctly.

It is possible to configure logging such that several thousand messages are 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.

Searches within a folder using the document property Keywords will not find any matches against DS 4.3 libraries. Such searches must be executed at the library level.

The Find application halts unexpectedly if a user tries to save a stored search to a DS library while the user’s profile has the 'Add Items' privilege set to 'No' (FR 5849). The user can save the stored search in his or her local file system.

You cannot view ZIP files using the Inso capabilities of the Viewer.

If you install the SQL 6.5 client DLLs, older versions of the SQL client DLLs will be overwritten.

In order to run the IDM Web suite under Microsoft IIS and Active Server Pages, a set of out-of-process Panagon IDM components must be configured using the administrative NT user account as explained below. If you make changes to this account, such as a password change or account expiration, you must reconfigure the IDM components.

If you do not reconfigure the IDM components after making a change to the NT user account, a Web client might receive the following error message when trying to access the IDM Web suite:

The following line causes ADO to mishandle the connection string:

In this instance, idmLogonOptNoUI translates to zero which is invalid. When preparing an ADO connection string, use the ADO constants found within ADODB.ConnectPromptEnum, such as adPromptNever, instead of IDM constants.

In addition, ADO parses the connection string and removes items corresponding to properties. This situation is illustrated in the following code:

Prior to ADO 2.0 the Extended Properties string would have included the "SystemType=...". Now, ADO removes this portion of the string and it is only available as a property (for instance, anADOConn.Properties("SystemType")).

You must run Task Manager to stop the idmview.exe process before you can uninstall the IDM Web client software.

If you use extended characters, see the IDM DS Installation Guide for possible client-side configuration requirements.

The following information provides details on the compatibility between IDM Desktop 2.0.2 and other FileNET products. Certification extends to 2.0.3.

IDM Desktop 2.0.3 is certified against the following versions of IS and DS:

• DS 4.2.x and 4.3
• IS 3.3.1 and 3.4.x

IDM Desktop coexists on the same PC as WFD 5.02A. Install WFD first; otherwise the WFD setup program unconditionally installs older DLLs on top of the newer versions required by the IDM Desktop.

FileNET does not support the coexistence of IDM Desktop and WorkFlo Controls for Visual Basic within the same application.

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

Panagon Capture release 2.0.1 can coexist with Panagon IDM Desktop 2.0.3 with patch 203-1 (or any later patch).

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

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

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

IDM integrated application examples are provided in the Office97 directory on the IDM Desktop CD. You can use these sample files to integrate IDM Desktop functionality into Microsoft Office 97 applications.

Refer to the readme.doc file in the Office97 directory for more information on application integration and installation.

The IDMListView OCX correctly formats numbers with a large number of digits.

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

Since FPNumbers provide greater precision than can be represented in a double, use the IDM FnFPNumber object if you require a large number of digits for a particular field (greater than 15 digits).

Programmatically, this enhancement adds the MaintainMagnifierSizeOnRotate property to the fnviewer.ocx. The magnifier window now keeps its orientation any time an image is rotated.

Boolean MaintainMagnifierSizeOnRotate

When this property is set to TRUE, the magnifier will not change its size in response to the image being rotated. The magnifier selector highlights a different area of the image. The default value of the property is FALSE, where there is no MaintainMagnifierSizeOnRotate functionality.

(This feature does not work correctly for multipage TIFF images.)

• Variant GetPrintFaxNames( PrintServerName As String )

Gets a list of available printer queues (for printers and fax servers) of the specified print server. PrintServerName is a three-part printer service name (e.g. PrintService:atlas:FileNet). The Variant returned is an Array of strings that contains the printer and fax server names. In order to get characteristics of a particular printer or fax, set the RemotePrintFax object's PrintFaxName property with the selected printer name.

• Variant GetPrintServerNames( [LibraryName As String] )

Gets a list of available print servers for the specified library. If the LibraryName parameter is omitted, the method gets the print service names for the current library. To get the list of print services for another library, pass in the two- or three-part library name (e.g. "DefaultIMS:atlas:FileNet", or "atlas:FileNet"). The LibraryName passed in must have been configured with compatible user credentials.

The method returns a Variant array of strings for each print service associated with the library. To print to this print service, set the RemotePrintFax object's PrintServerName property to the print service name.

• Long PrintDocumentWithUI( Document As Document )

Displays a dialog to specify the page range of the document to print or fax. Printer queue can be specified using this dialog. From this dialog you can navigate to the preference dialog to set printer preferences. The document is printed after clicking OK. Returns the print request ID assigned by WorkFlo/Print.

• Long PrintDocumentsWithUI( Document As Document )

Displays a dialog to specify the page ranges of the documents to print or fax. Printer queue can be specified using this dialog. From this dialog you can navigate to the preference dialog to set printer preferences. The document is printed after clicking OK. Returns the print request ID assigned by WorkFlo/Print.

• FnContextMenuEx(ContextMenu As Variant, X As Integer, Y As Integer, Reserved As Integer, Handled As Variant)

This event is exactly like FnContextMenu except that the last parameter is a Variant instead of a Boolean. This parameter is a Variant is because VBScript cannot handle ByRef parameters on anything other than a Variant.

• RequestDocumentCloseEx(Document As Object, Cancel As Variant)

This event is exactly like RequestDocumentClose except that the last parameter is a Variant instead of a Boolean. The reason this parameter is a Variant is because VBScript cannot handle ByRef parameters on anything other than a Variant.

• RequestPageUnloadEx(Document As Object, Cancel As Variant)

This event is exactly like RequestPageUnload except that the last parameter is a Variant instead of a Boolean. The reason this parameter is a Variant is because VBScript cannot handle ByRef parameters on anything other than a Variant.