To WorldWide Support | Right Click to Bookmark

Introduction

IDM Desktop has been qualified to run on the Windows 95 and Windows NT Workstation 4.0 (SP3 or SP4) operating systems. The 2.0.2 version of the IDM Desktop product includes some new features and all the changes provided in the IDM 2.0.1-1 through IDM 2.0.1-11 patch releases.

For information on installing the IDM Desktop product, refer to the "install IDM Desktop" topic in the Admin_D.hlp file. The Admin_D.hlp file is in the root directory of the product CD. Before installing the new software you must remove any existing version of the software that might be on your system.

You can install sample applications when you run the IDM Desktop setup program. The Visual Basic samples require either Visual Basic 5.0 with Service Pack 3, or Visual Basic 6.0. The Visual C++ samples require either Visual C++ 5.0 with Service Pack 3, or Visual C++ 6.0. The Visual Basic sample called HRDemo also requires the Panagon Integrated Workflow (Ensemble) product to be installed.

The Admin_D.hlp file also provides detailed information on hardware and software requirements, and administrative functions. Information about the SDK is provided in the file Npocx.hlp which is copied to your system during installation. You can open the file directly or view it through Visual Basic. For a complete listing of the documentation supplied with the IDM Desktop product, refer to the topic "About documentation" in the IDM Desktop help file (idmdsktp.hlp).

This document provides the following information:

Download software patches

Changes since the 2.0 release

Refer to this section for information on changes incorporated into the 2.0.2 version of Panagon IDM Desktop.

Critical notes

Refer to this section for information such as required service packs.

Software problems and restrictions

Refer to this section for information on known software problems and restrictions for the Panagon IDM Desktop 2.0.2 release.

The standard operation of the Panagon IDM Desktop product is described in the online help that accompanies the software.

Post release software updates and documentation are available at the following ftp site: ftp://ftp.css.saros.com or ftp://192.112.1.4. Send email to bvtechsupp@filenet.com to request an account.

Download Software Patches

After you install Panagon IDM Desktop or Panagon IDM Desktop Web, check the FileNET Customer Support site for the latest software patches. The ftp site from which you download the patches contains readme files describing the fixes contained in each patch.

To download patches

1. Go to the following URL: http://www.css.filenet.com/.

2. If you have a user name and password, click Login Now and go on to step 3. Please note that your login and password are case sensitive. If you require assistance, send e-mail to crg@filenet.com.

If you are a new user, click New User.

As a new user, you need to insure that the following conditions have been met before attempting to log on to the Web site:

Your Company has a support contract with FileNET CSS

You are an authorized customer contact for this account

You will also need your System ID (CID) Number. You can find this number on FileNET correspondence, such as packing lists and invoices.

3. Click the Troubleshooting link.

4. Click the Download fixes/fixes - FTP link.

5. Select the directory client_fixes.

6. Select the file IDMdesk-web.html.

A list of IDM release levels for which patches are available displays.

7. Select the directory for the Panagon IDM release level that you are running.

8. Select the directory for the software patch. A directory containing software executables and text files displays.

9. Review the contents of the readme file for information on the fixes provided in the patch and the procedure for installing it.

 

Changes Since The Panagon IDM Desktop 2.0 Release

This section provides the following information:

Features introduced in the 2.0.2 release

Fixes made to the product in the 2.0.2 release

Features introduced in the 2.0.1 release

Fixes made to the product in the 2.0.1 release

The Panagon IDM Desktop 2.0.2 product introduces the following new features:

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).

The Visual Studio 6 product (Visual C++ 6.0, and Visual Basic 6.0) is supported, in addition to the Visual Studio 97 (SP3) product.

You can copy a portion of the 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. Refer to the "What's New" section of the online help for details.

Improvements have been made to the handling of TIFF documents (FR 2452, 2701, 2928, 2322, 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 when a document is loading in the IDM

Viewer. This new feature indicates more clearly that an action is in process.

- A new property, F_MULTIPAGETIFFPAGENUMBER has been implemented to store the page number on which an annotation appears in a multipage TIFF document.

For improved readability of PDF documents, the Abobe Acrobat Reader is more closely integrated into the IDM Desktop products (FR 2165). Refer to the topics "Document formats supported by the Viewer" in the IDM Desktop online help (idmdkstp.hlp) and "Download Adobe Acrobat Reader" in the IDM Desktop Administrator's Handbook (admin_d.hlp), for more information.

You can now specify a print range for a document (FR 2815).

To access this feature in IDM Find and FileNET Neighborhood, select FileNET Print/Fax from a document's shortcut menu. To access this feature in IDM Viewer, select FileNET Print/Fax from the File menu.

The new Automation method PrintDocumentWithUI in IDMObjects displays the new dialog box for this feature.

The following problems have been resolved since the IDM Desktop 2.0.1 release:

From the Versions tab of the Document Properties dialog, selecting Properties from the context menu of one of the versions brings up the Properties dialog for that version.

DS folders that contain stored searches open more quickly (FR 3103, 3235).

Corrections for handling large FPNumbers on IDMIS libraries (FR 2288, 2290).

Various problems with COLD image documents have been resolved (FR 2866, 2915, 3038).

- You can now print a COLD Document's overlay image to a local printer using the

IDM Web client.

- From IDM Desktop, you can now view the last line in a COLD document.

- You can now view COLD compressed images.

- Improvements have been made to the zoom functionality.

You can now open an image document from the FileNET Neighborhood when a different image document is already displayed in the IDM Viewer with Thumbnails enabled as the default display setting (FR 2515).

You can now use the Properties>Annotations>Open command from one page of a displayed document to view an annotation on a different page (FR 2626).

You can more easily select or access IS print services located on a server other than an application server (that is, a root index OSAR server). Detailed information about this feature is provided in the IDM Desktop online help. Refer to the topic "Print to a FileNET printer" in the file idmdsktp.hlp (FR 2434).

The memory leak and access violations which occurr when network-wide lists of libraries are generated from the IDMObjects.FnEntireNetwork's Libraries property have been resolved (FR 2738).

SQL logging statements are no longer truncated to 256 characters in the Trace application (FR 3000).

The position and size settings for the IDM Viewer window are retained when you resize or reposition, close, and then reopen the IDM Viewer window from IDM Find, FileNET Neighborhood, or via the Launch method of a Document object (FR 2029).

The IDM Viewer time out problems that occurr when you repeatedly start and stop the Viewer from IDM Find have been reduced (FR 2240).

The list of available printers is now displayed for non-default printer services (FR 2434).

Check out information for a document now displays correctly on the General tab in the document's Properties screen for all display languages (FR 3483).

In the Find Application, the user and group drop down lists are loaded the first time they are used. The information is also stored in cache for later use (FR 4304).

Images with 203 x 96 dpi resolution are now rendered correctly (FR3017).

You can now use Simple Find with document types that have more than 10 custom properties (FR 2951).

Pressing the Delete key in the Find Results dialog box no longer deletes the item from IDM DS (FR 3395).

The QSample program can now be used to query for numbers with more than 8 digits (FR 2735).

You can now modify document properties after the index has been removed from the document class (FR 3298).

A memory leak triggered by loading and unloading documents with annotations in the Viewer control has been corrected (FR 3179).

Modifying the Viewer.Pane.ScrollPositionX and the Viewer.Pane.ScrollPositionY property values no longer sets random values (FR 4249).

When viewing documents, you no longer get a "Server Busy" error (FR 3192).

The Panagon IDM Desktop 2.0.1 product introduced the following new features:

Various installation improvements (FR 2124, 1896, 2138, 2139) were made as described below.

- You can install IDM Desktop without Microsoft's Internet Explorer product being available on your system. 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 libraries more intuitive.

- The IDM Desktop setup program now provides easier selection of the database client type(s) to communicate with DS 4.1.3 and/or DS 4.2.x library systems.

Support for viewing the following file formats was added (FR 2239):

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

- Micrographx Designer

- Autocad drawing versions 12 and 13

- IGES drawing

- Adobe Illustrator postscript

The annotation limit of 700 characters is more strictly enforced (FR 2965).

For example,

- If you are typing text into the annotation text box, the cursor stops at the 700th

character position.

- If you paste text of more than 700 characters into a new annotation, only the first

700 characters are accepted.

IDMIS 3.4 provides enhanced support for storing and launching non-image data types. A new system index, f_docformat, stores the original file name and extension of the file. This information is used to launch the native application when the Open menu is selected and to print via the native application when the Print command is selected.

The following problems were resolved in the IDM Desktop 2.0.1 release:

Documents that show generic icons in Explorer can be viewed and retrieved (FR 2081).

In the IDM Desktop 2.0 release, some files did not have the correct icon associated with the file. Attempts to retrieve these files failed with the error "Retrieve Segment (document content) failed". This problem has been resolved.

Various improvements were made to the handling of IS libraries (FR 2482, 2136, 2258).

- Closing all applications on a workstation now properly logs you off of the IDMIS library.

- When retrieving documents on IS libraries, IDM Desktop no longer fails with an "Invalid Page Number" error.

- You can now enter the maximum number of characters specified in a user-defined string field in the Document Properties.

A correction was made to the IDMIS Alternate Cache feature (FR 1817).

If the alternate server cache exists on a different IDMIS Server than the one containing the document, retrieval of the document no longer fails with the error 0x4d00000a "<77,0,10> CSM: No such object".

DS date property format conversions were corrected (FR 2128).

Previously, for any dates with a day value of less than 13, IDM Desktop displayed Date property values entered in dd-mm-yyyy format in mm-dd-yyyy format. For example, IDM Desktop displayed 06-02-1998 (6 February, 1998) as 02-06-1998. This problem occurred even though the user machine was 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 dates with day values greater than 12.

The handling of large FPNumbers on IS libraries was corrected (FR 2288, 2290).

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

- The ListView 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).

Calling the Value property of a Property object as follows, returns a double type that might lose precision.

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

Instead check to see whether the property is an FPNumber and then 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

Various corrections were made to the handling of COLD image documents (FR 1407, 2157, 2158, 2159).

- 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.

Critical Notes

IDM Desktop 2.0.2 has been certified with ActiveX Data Objects (ADO) version 2.0. 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. 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 either Visual Studio 97 Service Pack 3 or Visual Studio 6.

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

You can select multiple database client types for DS 4.2.x library systems only.

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.

As stored searches are saved with the current server name and system name, changes to the DS system 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 print outs of COLD documents are aligned incorrectly.

Multiple file 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 the IDM desktop product. After the installation completes, add the information from the old TNSNAMES.ORA file to the version of the file generated during the installation.

Compatibility/Coexistence with Other FileNET Products

The following information provides details on the compatibility between the IDM Desktop 2.0.2 product and other FileNET products.

Information for server software requirements and a complete certification matrix is provided in the Admin_D.hlp help file. This file is located in the root directory of the IDM Desktop CD.

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

4.1.3 and 4.2.x DS

3.3.1 and 3.4.x IS

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.2. When both products are installed on the same PC, they execute as native independent applications. However, controls from both products can be embedded in the same application.

IDM Desktop 2.0.2 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, or multipage TIFF documents. Contact the FileNET Customer Support Center for the latest software updates.

IDM Desktop 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.

In a client-server environment, IDM Desktop 2.0.2 includes support for IMSdocuments that are linked (cross-cataloged) to a DS (Mezzanine) library system through the IMS Connect for Mezzanine product. When a document link within the DS library system is opened, the target document from the IMS library is retrieved and displayed. Web access to these document links is not currently provided.

IDM integrated application examples are provided in the Office97 directory on the IDM Desktop 2.0.2 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.

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

- The message: "Version conflict MFC40.DLL Your version = 4.1.6139. Keep your version? Y/N?". Reply Yes to retain the more recent version of the MFC40.DLL, otherwise an older version of MFC40.DLL is installed.

- The error: "The ordinal 6451 could not be located in dynamic link library MFC42.DLL". This problem occurs if you are using Visual Studio 97 and Service Pack 3 is not installed.

IDM Desktop installation is an interactive process, there is no silent installation for this product.

If you are using Capture 2.0.1 and IDM Desktop 2.0.1, when you upgrade to IDM Desktop 2.0.2 you must reinstall the Capture product.

Check In/Check Out

After checking out/in numerous versions of a document from an IDM Document Services 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

http://support.3com.com/infodeli/tools/nic/Fast_EtherLink_XL.htm

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

Explorer Integration

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

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 check in, or if you cancel the check out, refresh the display by pressing the F5 key.

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

If you are concurrently logged on to a library via Explorer and other applications, you cannot log off the library through Explorer until the other applications are closed.

Inconsistencies can occur in the state of the Logon/Logoff entry in the context menu popup 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.

Find Application

To avoid difficulties loading the Find application, launch the application from the Viewer or the FileNet Neighborhood rather than from the Panagon IDM menu.

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.

When viewing INSO documents, some special characters, for example the check mark symbol are not displayed. This problem is caused by a limitation of the INSO viewer.

To prevent color distortions when using the Viewer, displays must be configured with a color palette of greater than 256 colors.

Documents can have multiple pages. The pages are usually stored in separate files but they can be stored in one file. Multifile documents must be a supported image type. FileNET supports the following image types:

- Single-page TIFF (G4, G3, Raw)

- FileNET Banded

- FileNET Tiled

- PC Forms, DAM Forms

- BMP

- PCX

- DIB

- JPEG in JFIF format, 8-bit grayscale and 24-bit color only (not JPEG in TIFF)

- COLD (with and without background templates)

- WordFlo

The Viewer application can display

- Multipage TIFF documents that are stored in a single file.

- Multiple file documents.

If a document contains more than one multipaged file, the Viewer application displays the first file only.

Printing Multipage TIFF Documents

You cannot print multipage TIFF documents on a FileNET printer.

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

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

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.

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

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.

ObjectSet Object

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.

Property Object

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

When you modify the value of a Required Date/Time single value custom property, the changes will revert to the original value after you reopen and exit from the same document properties page (FR3250).

Query using ADO

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 design time.

The following line causes ADO to mishandle the connection string:

"Prompt=" & idmLogonOptNoUI & ";"

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:

connStr = "Provider=FnDBProvider;Data Source=" & lib.Name & ";SystemType=" & lib.SystemType & ";"

anADOConn.Open connStr

extPropsStr = anADOConn.Properties("Extended Properties")

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")).

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 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 an IDM Document Services 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.

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 does not work unless the library is logged on.

Ensemble Integration

If you have not logged on to the libraries, routing a document using a workflow that contains Panagon documents 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 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. This problem is caused by a Microsoft OLE DB problem for which no fix is currently available.

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. If either one is selected, the IDM Viewer window displays a blank screen rather than an 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 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 causes IDMViewer to display the document and the print request fails with the error message "Run-time error 91. Object variable or With block variable not set."

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 drop down menu and select a document from the list located at the bottom of this menu.

Legacy DS Documents

Documents that are added to legacy DS 3.x systems prior to these systems being upgraded to 4.x will not have a valid Version Filename until they are checked out and then checked back in to the 4.x system. On checkout the user must manually enter the correct filename in the Checkout File To dialog box (FR2576).

Local Cache

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 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 does not always function correctly.

Logging

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.

Multiple Selection

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

Extended Character Sets with DS Library Systems

Currently FileNET does not support the use of extended character sets.

Searches on DS Servers

When performing property searches against IDM DS servers running Oracle, the search will always be case sensitive (FR 3458).

^© 1998 FileNET Corporation USA. All rights reserved.