Readme File for the
Panagon IDM Desktop
and
Panagon Web Services
3.0.0 Release (12/99)
Update 5
Updates to this file are listed below and formatted in blue text throughout the file. Note the new section “Important Information for Developers,” which was added because many programming issues apply to both the desktop and web.
09/29/00 As
of IDM 3.0.0 – 6, you can use MDAC 2.5 in your IDM Desktop and Web Environments.
09/29/00 WAL
Trace Files
09/29/00 The Viewer causes GPF errors on Win 9x Systems
04/20/2000 Authoring application must be installed to recognize links
05/01/2000 Workaround for problem after removing IS components from web server
05/01/2000 Cannot co-locate Web Services with DS server component
05/01/2000 Site Server integration preference not supported in Web Services
05/02/2000 Another workaround for web client checkin error
03/17/2000 Important notice for users of DS libraries with Oracle databases
04/03/2000 Clarification of support for Powerbuilder development environment
04/04/2000 Use new ArchiveEx method to specify archive disposition
04/04/2000 Workaround for web client checkin error
04/04/2000 Lotus Notes integration is supported for IS
04/04/2000 Printer settings to improve printing of stamp annotations
04/05/2000 Patch 300-1 fixes FRs 16299, 19205, 19206, 19250, and 19297
04/05/2000 Convert
SDM searches to PANAGON stored searches
using VB
04/05/2000 Drag and drop to add one document at a time
04/05/2000 Installing IE 5.0 after installing IDM Desktop
04/06/2000 FRs 17815, 15944, 17327, and 17210 fixed prior to release
02/02/2000 Cannot integrate with application installed on network drive
02/02/2000 Performance over a WAN in terms of ping times
02/02/2000 Updated end user license agreement
02/03/2000 Security requirements for deleting documents
02/03/2000 Downtime when modifying document class with replication
02/03/2000 Must install 3.0.0 web client to access 3.0.0 web server
02/03/2000 Cannot use SQL trace logging on web server
02/04/2000 Integration when Outlook is installed without Office
02/09/2000 Unified logon does not work for web clients
02/09/2000 Warnings
for NT with Service Pack 4 can be ignored
02/10/2000 Harmless
script errors using IE 4.01
01/05/2000 Capture users must set prefetching priority to Normal
01/05/2000 DS 4.3 no longer supported on AIX or Solaris platforms
01/19/2000 Updated requirements for Report Manager
01/19/2000 Updated version requirements for Adobe Acrobat Reader
01/19/2000 Performance problems after upgrading to DS 5.1
01/19/2000 Co-locating with DS 4.3 not supported
01/19/2000 Co-locating with Rendition Services not supported
01/19/2000 Saving
a multiple-page IS document using VBScript
01/19/2000 Can’t
print .TXT files to Panagon Print 4.1 printer
01/19/2000 Property
pages hang with Win98 and IE 4.01 SP2
01/19/2000 Can’t
change a replica’s relationships
01/19/2000 Slow
to register DLLs after installation and reboot
01/25/2000 After re-install, hangs registering fnsess.dll if tracing is on
01/25/2000 Limitations of compound documents with UNC paths
01/27/2000 IDM Desktop and Panagon Web Services certified on NT with Service Pack 6a
01/27/2000 Problems with Office 2000, IE 5, and web client
This readme file contains
information for both IDM Desktop and Panagon Web Services.
The 3.0.0 release of IDM Desktop
and Panagon Web Services (12/99) provides support for DS and IS libraries. If
you are upgrading from an earlier release, be sure to review the new features
described in the IDM Desktop User's Help, IDM Desktop Administrator's Help,
Panagon Web Administrator's Help, and the IDM Toolkit Help.
This readme file, in HTML format
and with the latest updates, is available from the FileNET CSS Web site. See Downloading Patches and Files later in
this file for instructions.
IDM Desktop and Panagon Web
Services are Year 2000 compliant. For details on compliance, see the Year 2000
information accessible from the FileNET home page at http://www.filenet.com.
This document provides the
following information:
·
Important notes (with
information such as required service packs)
·
Known software problems and
restrictions
You can
review the new features, requirements, installation and other documentation
from the CD before installing the software. (On Windows 95 systems, accessing
the help directly from the CD might not work correctly. Instead, after
installing IDM Desktop, access the help by pressing Start -> Programs ->
FileNET Panagon IDM -> Help for Users.)
·
For IDM Desktop, refer to the
help file alldoc.hlp in the Docs
folder on the product CD.
·
For Panagon Web Services,
refer to the help file w_alldoc.hlp
in the Docs folder on the product CD.
· IDM Desktop 3.0.0 is delivered on a single CD. Likewise, Panagon Web Services 3.0.0 is delivered on a single CD.
In addition, the Panagon Web Services CD contains directories (FnControls, viewer, and viewer2) that hold the web client software. Web users can install the web client software from the web server, directly from the CD, or from a file server. See the PANAGONWeb Administrator's Help for details.
· Programming information for IDM Desktop
Information about the SDK is provided in the idmsdk.hlp file, which is copied to your system during installation if you select and install the optional Developer Files in Setup. 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 (idmdsktp.hlp).
· Programming information for Panagon Web Services
For information on the Panagon Web 3.0.0 SDK, refer to the help file idmsdk.hlp. This help file provides reference information on the objects, methods, and properties used to develop Panagon Web Services 3.0.0 applications.
The Panagon Web 2.0 application is provided on the Panagon Web Services 3.0.0 compact disk as a sample application and can be installed on your web server. For detailed information on the sample Panagon Web Services 2.0 pages, refer to the idmsdk.hlp file.
IDM
Desktop has been qualified to run on the Windows 95a (Windows 95 with SP1),
Windows 95b, Windows 95c, Windows 98 first and second editions, Windows NT
Workstation 4.0 (SP5 and SP6a), and Windows NT Server
4.0 (SP5 and SP6a) operating systems. All
platforms were qualified with and without Internet Explorer 5.0 installed. When
you install IDM Desktop the following third party products are also installed:
·
MDAC 2.1 (SP2)
(This
version of MDAC includes ADO.)
Beginning
with the application of FileNET IDM software patch IDM 3.0.0-006, MDAC 2.5 can
be used in your IDM environment.
·
DCOM 1.3 for Windows 95
systems
·
Inso Outside-In Viewer
Technology 6.0
See the "IDM Desktop Administrator's Help" for information on SMS compatibility.
For Year 2000 compliance, please install all Year 2000 patches supplied by Microsoft that relate to your operating system and environment.
IDM Desktop
can be used with the following products:
·
Visual Studio 6.0 (SP3)
·
Microsoft Office 97 with SR2
and Office 2000 (Word, Excel and PowerPoint)
·
Outlook 97, 98 and 2000
·
Lotus Notes 4.6.2.a and 5.0
Important
Notes
·
Exit from all programs
including virus protection programs before installing or upgrading.
·
IDM Desktop is supported on NT
Workstation with Service Pack 4, 5, or 6a. When you install IDM Desktop on an
NT workstation, you will get a FileNET warning message if you have not
installed Service Pack 5. You can safely ignore this message. (FR 19228)
·
An upgrade facility is
provided for users who are currently using IDM Desktop 2.0.3 or 3.0.0 FCS 1.1.
This
upgrade facility enables you to install IDM Desktop 3.0.0 without requiring
that you uninstall the old software first.
However,
(1) If
you are using 2.0.3 application integration, you must uninstall it before
upgrading IDM Desktop. See the topic “Uninstall
2.0.3 application integration” in the IDM Desktop Administrator’s Help for
instructions.
(2) An
upgrade resets the SID and Port numbers for Oracle libraries to the default
values of orcl and 0 respectively. If you had
been using other values, after the upgrade completes and you reboot, use IDM
Configure to delete and re-add the libraries with the appropriate values.
·
Sometimes, during
install or upgrade, it is possible you will see a dialog with the following
information:
The ODBC resource DLL
(C:\WINDOWS\SYSTEM\ODBCINT.DLL) is a different version than the ODBC setup dll
(C:WINDOWS\SYSTEM\ODBCCP32.DLL).
You need to reinstall the ODBC
components to ensure proper operation.
Press OK to proceed, CANCEL to
abort.
Prior
to the installing or upgrading your software, other applications may have some
sub-set of the ODBC core DLL's locked. During an install or upgrade, when MDAC
is run, it upgrades the ODBC core, but because some of the files are locked,
they are not committed until after a reboot. After you run MDAC, as many COM
objects as possible are self-registered. If some of them depend on ODBC, this
dialog box will appear. It is a warning, and pressing OK will allow the install
to complete successfully. After you reboot, a second pass at self-registration
is done, so any failed self-registration items are taken care of at that point.
·
If you use the
Notes-based Notes Panagon Integration Administration database, the database
path and filename MUST be"<root Notes data
subdirectory>\FileNETNotesPanagonIntegration\NPIAdmin.Nsf". The
template for this database is available in the Panagon installation path, as
well as in a maintenance subdirectory of the installation media. If copying it
from a CD remember to remove the "read-only"file attribute, so you
can create and save data in it.
·
After
completing an installation or upgrade, you must reboot. During the reboot, the
new DLLs are registered. This can take several minutes. Please be patient and
wait for the registration to complete.
·
If
tracing is on when you upgrade or re-install IDM Desktop or Panagon Web
Services, fnsess.dll will not register and the registration code will hang. To
complete the registration, disable tracing then run fnreg.exe. (FR 19292)
·
If you
install IDM Desktop and subsequently install or upgrade Internet Explorer, you
may experience errors during or after the installation because IDM Desktop
requires a specific version of urlmon.dll (479KB dated 3/16/99) and Internet
Explorer installs a different version. To avoid such errors, install or upgrade
Internet Explorer as follows:
1.
Reboot.
2.
Locate
the urlmon.dll file and rename it to
urlmon.dll.FN.
3.
Install
or upgrade Internet Explorer.
4.
Locate
the urlmon.dll file (newly installed
by IE) and rename it urlmon.dll.IE.
5.
Copy urlmon.dll.FN to urlmon.dll.
6.
Reboot.
If you are upgrading an IDM
Desktop 2.0.3 or IDM Desktop 3.0.0 FCS1.1 environment, the migration path is:
In general, if you are upgrading
an IDM Desktop environment from a release other than 2.0.3 (any patch level) or
3.0.0 FCS 1.1, the migration path is:
1.
Uninstall your existing IDM
software.
2.
Install any applicable
service packs for your operating system.
3.
Install any applicable
service packs for your desktop applications.
4.
Install or upgrade Internet
Explorer (optional).
5.
Install IDM Desktop 3.0.0.
Installing IDM Desktop 3.0.0
automatically installs the components required for the desktop machine to act
as a web client.
It is also important to reboot
your system as directed by the various install and uninstall programs.
If you perform an installation that provides support for DS libraries, client libraries for DS 4.3 and DS 5.1 are automatically installed as a single program group called “FileNet IDM DS Client Libraries 5.1.”
Panagon Web
Services has been qualified to run on the Windows NT Server 4.0 (SP5 and SP6a) operating system
with the 4.0 version of the Microsoft Internet Information Server (IIS).
Panagon Web Services clients must be
using the Internet Explorer 5.0 or 4.01 (SP2) browser on a Windows 95, Windows
98, or a Windows NT (workstation or server) operating system to access the
3.0.0 web application. Additionally, Web clients can access the 2.0 sample web
pages using either the Internet Explorer browsers or Netscape 4.6.1. If you upgrade to Panagon Web Services 3.0, you must also
upgrade the web clients to 3.0 to access the 3.0 web application. 2.0.3 clients
can continue to use the 2.x web application without upgrading.
For Year
2000 compliance, please install all Year 2000 patches supplied by Microsoft
that relate to your browser and operating system.
In addition,
Panagon Web Services installs the following on the web server:
·
MDAC 2.1 (SP2)
(This
version of MDAC includes ADO)
·
Beginning with the
application of FileNET IDM software patch IDM 3.0.0-006, MDAC 2.5 can be used
in your IDM environment.Inso Outside-In Viewer Technology 6.0
To install Panagon Web
Services,
1.
Back up any web applications,
including customizations to the sample application provided with the IDM 2.0.x
release, that you might have.
2.
Remove earlier versions of
the IDM Web Services product and exit from all programs including any virus
protection programs.
3.
Install any applicable
service packs for your operating system.
4.
Install or upgrade Internet Explorer
to at least 4.01 (SP2).
5.
Install Panagon Web Services
3.0.0.
6. If you will be using Panagon Web Services on a
multiprocessor web server with DS Oracle libraries, FileNET recommends that you
downgrade your Oracle client software to 7.3.4. Oracle is currently researching
the issue requiring this downgrade. Note that
the downgrade instructions on the Oracle CD are incomplete. You can download
complete downgrade instructions from the FileNET Web site; see the Product
Release Notes for DS 5.1.
It is also important to reboot your system as directed by the various install and uninstall programs. Installing Panagon Web Services on your NT server also installs the components required to enable your NT server to act as a web client.
Panagon Web Services is supported
on NT Server with Service Pack 5 or 6a. However, when you install Panagon Web
Services, you will get a Microsoft IIS warning message if you have installed
Service Pack 5 or 6a. Microsoft has qualified IIS with Service Pack 4 and has
not yet qualified IIS with the newer service packs. In FileNET testing, IIS
functions correctly with Service Packs 5 and 6a. (FR 19224)
If tracing is
on when you upgrade or re-install IDM Desktop or Panagon Web Services,
fnsess.dll will not register and the registration code will hang. To complete
the registration, disable tracing then run fnreg.exe. (FR 19292)
Silent installation facilities are
provided for the three web client options. A new upgrade process supports
upgrades from 3.0.0 FCS 1.1 and 2.0.3 (any patch level).
During the
installation of PANAGONWeb Services, if you click on the help button, an error
might display informing you that the system cannot locate the file admin_w.hlp.
If this message displays, use the Browse button on the message pop-up to locate
the file, which is in the root directory of the CD.
This version
of the Panagon IDM Desktop and Web Services 3.0.0 product has the following
restrictions.
·
IDM products do not support
the following items created with SDM: smart folders, document references, renditions, and compound documents. See
the DS Upgrade Notes for information on how to convert smart folders to stored
searches.
·
Panagon products do not
support stored searches created with the @mezzanine API.
·
To install software on a
Windows NT operating system, the user must have Administrator privileges.
·
The DS 5.1 option for using the Document ID as the file
name for a checkout or for a copy operation is not supported.
·
If you make regular use of
Adobe Acrobat PDF files, FileNET recommends that you use Adobe Acrobat Reader
4.0 to view the files. You can install the Adobe Acrobat Reader from the
Acrobat directory on the IDM Desktop and Panagon Web Services CDs. If you use
extended characters, see the DS Installation Guide for possible client-side
configuration requirements. If you need to display Report Manager Documents,
see the Report Manager requirements in this readme file.
·
If you are using Windows 95
systems that access libraries that support the Euro character, you must install
the Microsoft patch that provides support for this character. The patch is
available at http://www.microsoft.com/windows/euro.asp.
· There is a known Oracle8i problem that may require you to downgrade your Oracle client software to version 7.3.4 after you have installed or upgraded certain clients that must connect to Oracle-based library systems. Note that this downgrade does NOT need to be done on library system servers where you've installed DS 5.1. The problem occurs only in high-volume, multi-threaded environments (for example, on web servers running your customized applications or an application such as Panagon Web Services). You can download a readme file containing complete downgrade instructions from the FileNET Web site; see the Product Release Notes for DS 5.1. Please refer to the updated readme instead of the readme.htm file on the Oracle 7.3.4 Client Files CD-ROM included with your Document Services shipment.
· You can deploy IDM Desktop and Panagon Web Services with Microsoft's Systems Management Server (SMS). Information on SMS is provided at the end of this readme.
· If a stored search against an IS library includes dates with 2-digit years (such as 04/09/99), you must edit the search, enter a 4-digit year (such as 04/09/1999), and re-save the query.
·
If you are a previous SDM user
and you experience performance problems after upgrading the library to DS 5.1,
the library administrator should run the VUPDATE utility. The utility is
installed with the DS library software.
· IDM Desktop and Web Services 3.0.0 is qualified with Outlook 97 with SR2, Outlook 98, and Outlook 2000. It is expected that using other MAPI-compliant email systems will work. However, if a problem arises with a MAPI-compliant email system, the problem must be replicated in a supported version of Outlook before FileNet can commit to resolving the issue.
·
IDM Desktop supports
application integration for applications installed on the user’s local hard
drive. The entire application must be installed locally. If you attempt to
install application integration for an application installed in whole or in
part on a remote network drive or on a CD, the installation will fail but may
not report an error. (FR 19494)
·
Replication does not support
stored searches. If placed in replicated
folders, stored searches will not produce the expected results. In future releases, stored searches will not be replicated. (FR 18401).
·
You cannot change a replica’s
relationship with other objects. This means you cannot publish a replica; you
cannot add or delete the components of a replica of a compound document; you
cannot add or delete a replica’s annotations. (You can replicate a published
document; you can check out and check in compound document components; and you
can modify existing annotations.)
·
For satisfactory performance
in production environments, we recommend connections that produce ping times
(round trip) of 30 milliseconds or less. You can expect 5 to 10 second delays
when ping times exceed 50 milliseconds; if ping times exceed 100 milliseconds,
performance will be unacceptable.
If you
are using Panagon Web Services in a WAN environment, optimize performance by
locating the web server and the DS or IS server on the same Local Area Network
(LAN).
·
To detect OLE links in
compound documents, the file's authoring application must be installed on the
workstation. Note also that OLE links in documents created with Office 97
through Office 2000 can be detected using a later version of the authoring
application. Documents created with an Office version prior to Office 97 must
be updated to Office 97 format (or a later version) to detect OLE links.
·
IS supports the dates 1/1/100
through 3/10/9999. However, using IDM Desktop and Web Services:
(1) The
Date Control only supports dates 1/1/1400 through 12/31/2400
(2) When
entering a date directly into a field, the earliest date you can supply is
1/2/100.
·
When using IS, the document
property pages
(1) Do
not detect that the date 3/11/9999 is invalid. (FR 18456)
(2) Do
not always detect invalid dates when you tab in and out of fields. (FR 18462)
(3) Do
not prevent users entering more than 4-digit years. The extra digits are
ignored. (FR 18460)
(4) Do
not accept 2-digit dates. The 2-digit dates are automatically changed to the
current year if you are setting a new date value, and automatically revert to
the previous date if you are updating an existing value.
Avoiding Misinterpretation of Date Information on IDM
Desktop and Panagon Web Services
To avoid confusion when performing
searches:
·
Set the date format on your
client to show 4-digit years.
·
Use 4-digit years when
entering dates in search criteria.
Dates are entered, interpreted, and displayed as determined by the web server's date format setting. In browse mode, dates in columns are displayed according to the web server’s date format setting. Likewise, the properties pages display date information using the web server’s date format settings.
You cannot delete a document from
a DS 4.3 library. To delete a document from a DS 5.1 library, you must have
access rights to the document equal to or greater than the Minimum Delete
Access Level, which the system administrator sets on the server (typically, it
is set to Owner). Note the following exception: you must have Administrator
access rights to delete a child component of a compound document if the child
has a strong link to the parent.
You must drag and drop individual
documents to add them to libraries. Note that multiselect was supported in
earlier releases but is not supported in 3.0.0. (FR 19676)
If
you are printing stamp annotations to an HP4 or HP5 printer from a Windows 95
or 98 PC, we recommend the printer settings below.
·
On the Graphics tab, select:
Dithering:
Fine
Intensity: 99
Use Raster Graphics
·
On the Fonts tab, select Print
TrueType as Graphics.
·
On the Device Options tab,
select RET – Printer Default.
In addition, if the stamps are
rotated, we recommend a dark text color.
If you are using WAL 3.4.0 or
earlier, the WAL error trace files are located on your desktop in the directory
...\FileNET\Fnsw\Client\tmp. If you are using WAL 3.5, the error trace files
are located in the directory …\fnsw\client\logs\...
Searching
·
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.
· The Find application has new icons. You won’t see the new icons after you upgrade to IDM Desktop 3.0.0, however, because the old the Find application icons remain in Window's icon cache file. To display the new application icons, you must delete the cache file. Windows rebuilds it automatically. Delete the icon cache file as follows:
(1) Double click the Display icon in the Control
Panel.
(2) Choose Icon from the Appearance tab.
(3) Change the icon size from 32 to 33, and then click Apply.
(4) Change the icon size back to 32 and click Okay.
Viewer
For satisfactory display of PDF
documents, we recommend that you install either Adobe Acrobat Reader 3.02 or
Adobe Acrobat 4.0 (but not both; the two versions are incompatible). Adobe
Acrobat Reader 4.0 is preferred. If you need to display both standard PDF
documents and Report Manager documents, be sure to also review the information
on Report Manager in this readme file.
Netscape Servers and Browsers
Netscape
servers cannot be used with Panagon Web Services. The Netscape 4.6.1 browser
can be used with the 2.0 sample application provided with the release. The use
of any Netscape browser with the 3.0.0 application is not currently supported.
Compound and Published Documents
· Using a web client you cannot add, checkin or checkout a compound document.
·
You cannot add a published
document.
Searching
You cannot
create stored searches or templates from an Panagon Web Services client.
However, from the Panagon Web Services client you can access searches and
templates that are stored in an DS library or on the web server. The stored
searches and templates can be used to query both IS and DS libraries.
Run Applications in Main Server Process (IIS 4.0)
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.
Security
Setting Requirements
The IIS Basic Authentication security setting is not supported. This version of Panagon Web Services supports Anonymous Access, NT Challenge/Response (NTC/R), and Secure Socket Layer (SSL).
Use of Office 2000
If you are
using the Panagon web client with Office 2000 applications and Internet
Explorer 5, you will have problems opening documents. We recommend that you
request and install on each web client a hotfix from Microsoft. To get the
hotfix, contact your Microsoft representative and ask for the QFE associated
with Knowledge Base article Q185978.
Note that the text in the Knowledge Base article is for a different
problem, but Microsoft will supply the correct hotfix if you ask for the QFE
associated with Knowledge Base article Q185978.
The qualified development environment is Visual Studio 6 with Service Pack 3. In addition, note the following:
·
We support any fully
COM-compliant development environment but we validate only with Visual Basic
and Visual C++. Note that we do not validate PowerBuilder application
development. If a problem occurs in a PowerBuilder development environment and
you can reproduce it in a validated development environment, please contact
Customer Support.
·
The IdmDocCurVerTruncFile
property is no longer supported. Use idmVerFileName instead.
·
In an
IS numeric mask, the hash (#) sign suppresses all leading zeros. If an IS
fpnumber property value is zero and the hash mask is used, the property field
will show the zero when it is selected, but will appear to be empty when the
focus is not on the cell. If you want
to retain the zero after formatting, use a mask of ‘0’.
·
If you specify the
idmDeletePrevious option on the QueueQuerySpecification.Fetch call when more
than one entry was previously retrieved, only the last of the previously
retrieved entries is deleted. (FR 6629)
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.
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.
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
run time.
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 comparison operators on multivalue custom properties
return multiple instances of items.
Action Grid Control
Selections
made in the Effects section of the Grid's properties page (checkboxes to
select/deselect Grid props including ShowHorizontalLines, ShowRowHeaders, and
ShowTreeViewLines) do not update the corresponding rows on the Grid properties
list when Apply is pressed.
Command Objects
When
executing the method ShowOptionsDialog, the Options Dialog that appears is
always modal regardless of whether the Modal parameter of the method is passed
a value of True or False.
Normally, to
save an IS multiple-page document, you create an array, populate it with the
page data, then pass the array to the IDM call. However, using an array in
VBScript with Panagon Web Services can cause unexpected results. The following
code snippet shows one way of successfully saving a multiple-page IS document
using VBScript (as in the ASP environment):
‘Create multiple-page document using VBScript
Set oDoc = oLib.CreateObject (idmObjTypeDocument, “SampleDocType”)
FileName01 = “C:\Temp\Anno1.tif”
FileName02 = “C:\Temp\Anno2.tif”
ODoc.SaveNew Array(fileName01, fileName02), idmDocSaveNewKeep
ADO
Mishandles Connection Strings
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")).
You can
specify an archive disposition when archiving a version using the ArchiveEx
method:
Sub ArchiveEx([DispName As String])
Member of IDMObjects.Version
...where
DispName is the name of an archive disposition.
Please note the following updated licence agreement:
FileNET End User Software License
READ
CAREFULLY BEFORE INSTALLING. IF YOU DO NOT AGREE WITH THESE TERMS AND
CONDITIONS, OR THE TERMS AND CONDITIONS IN YOUR SOFTWARE LICENSE AGREMENT WITH
FileNET, DO NOT INSTALL THE SOFTWARE. BY INSTALLING THE SOFTWARE, YOU AGREE TO
BE BOUND BY THE TERMS OF THIS LICENSE.
1.
Authorization of End User
A.
Each Software product, including any documentation relating to or
describing such Software, such as, but not limited to, logic manuals, flow
charts and improvements or updates provided by FileNET (collectively called
"Software"), is furnished to End User under a personal,
non-exclusive, nontransferable license solely for End User's own internal use
in compliance with this License and all applicable laws and regulations. End
User agrees that this License does not permit End User to: (1) use the Software
for a service bureau application or (2) transfer the Software without prior
written consent from FileNET.
B.
End User may make one copy of the Software, (with the proper
inclusion of FileNET's copyright notice and any other proprietary notice and/or
trademarks on such Software), for End User's own backup purposes; however, the
End User may not otherwise copy or reproduce the Software except to install the
Software on a single hard drive for use by End User in accordance with this
License.
C.
If End User is unable to operate the Software on the computer
equipment due to an equipment malfunction, the Software may be transferred
temporarily to other computer equipment during the period of equipment
malfunction.
D.
Title to and ownership of the Software and all of its parts (or any
modifications, translations, or derivatives thereof, even if unauthorized) and
all applicable rights in patents, copyrights and trade secrets in the Software
shall remain exclusively with FileNET. Software provided hereunder is valuable,
proprietary, and unique, and End User agrees to be bound by and observe the
proprietary nature thereof as provided herein. End User agrees to take diligent
action to fulfill its obligations hereunder by instruction or agreement with
its employees or agents (whose confidentiality obligations shall survive
termination of employment or agency) who are permitted access to the licensed
Software. Access shall only be given on a need-to-know basis. Except as set
forth herein or as may be permitted in writing by FileNET, End User shall not
use, provide or otherwise make available the Software or any part or copies
thereof to any third party. Unless prohibited by law, End User shall not
reverse engineer, decompile or disassemble the Software or any portion thereof,
nor otherwise attempt to create or derive the source code. End User
acknowledges that unauthorized reproduction, use, or disclosure of the Software
or any part thereof is likely to cause irreparable injury to FileNET, who shall
therefore be entitled to injunctive relief to enforce these restrictions, in
addition to any other remedies available at law or in equity.
E.
FileNET agrees that affiliates of End User may use the Software;
provided that prior to any affiliate's use of the Software: (1) each affiliate
shall sign and deliver to FileNET a mutually agreeable appendix to this License
certifying its License to be bound by the terms herein; and (2) such use by
such affiliate shall be subject to the following: (i) End User accepts
responsibility for the acts or omissions of such affiliates as if they were End
User's acts or omissions; (ii) End User shall indemnify FileNET against losses
or damages suffered by FileNET arising from breach of this License by any such
affiliate as if effected by End User; and (iii) such use shall not constitute
an unauthorized exportation of the Software or documentation under U.S.
Government laws and regulations.
F.
FileNET shall defend any action, suit or proceeding brought against
End User so far as it is based on a claim that the use of any Software
delivered hereunder constitutes an infringement of any patent, copyright or
other intellectual property right, provided that FileNET is promptly notified
by End User of the action and given full authority, information and assistance
for the defense of the action. FileNET shall pay all damages and costs finally
awarded against End User, but shall not be responsible for any compromise made
without its consent. FileNET may at any time it is concerned over the
possibility of such an infringement, at its option and expense, replace or
modify the Software so that infringement will not exist, or request the End
User to remove the Software involved and refund to End User an amount as
established by FileNET.
G.
FileNET shall have no liability to End User under any provisions of
this Section, if any claim is based upon the use of the Software in combination
with software not supplied by FileNET, or in a manner for which the Software
was not designed, or if the claim of infringement would have been avoided but
for End User's use of Software other than the latest unmodified release made
available to End User.
2. Types of Software Licenses
A. For purposes of this License, the following definitions shall
apply:
1.
Server Software is a copy of
Software residing on a server or multiple servers.
2.
Clients are personal
computers, minicomputers, mainframes, workstations and terminal devices that
interact with Server Software.
3.
Client Software is a copy of
Software residing on a Client that interacts with Server Software.
B. End User agrees to license the Software as follows:
1.
For Client Software - one copy
of Client Software for each Client that accesses any Server Software.
2.
For Server Software - one copy
of Server Software for each base system. In addition Concurrent User Licenses
in accordance with FileNET's then-current version of the Concurrent User
Guidelines which consist of concurrent Dedicated User, Shared User, and
e-Business User Licenses. These Concurrent User Guidelines measure persons and
programmatic operations that interact with the Server Software directly or
indirectly from a Client.
a. For Dedicated User
Licenses - a copy of Client Software and a copy of Server Software where the
ratio of licensed Clients to the number of concurrent Dedicated User Licenses
on the Server is one to one (1:1).
b. For Shared User
Licenses - a copy of Client Software and a copy of Server Software where the
ratio of licensed Clients to the number of concurrent Shared User Licenses on
the Server does not exceed ten to one, (10:1).
c. For eBusiness User
Licenses - a copy of Client Software and a copy of Server Software where the
ratio of licensed Clients to the number of concurrent eBusiness User Licenses
on the Server does not exceed one hundred to one, (100:1).
C. In the event End User
elects to access Server Software by the use of a gateway or concentrator
multiplexing methodology, the number of Concurrent User Licenses, is determined
by the maximum number of Clients in front of the multiplexer which have access
to the Server Software at any given point in time. The then current version of
FileNET's Concurrent User Guidelines will be used to determine the number of
required Concurrent User Licenses.
D. FileNET may audit
the End User's Software usage remotely or on-site during service calls or upon
reasonable notice during standard business hours. The audit shall determine
Software usage by server for the number
of concurrent Dedicated, Shared and/or eBusiness User Licenses required for
each server. Should an audit determine that Customer's usage has exceeded the
number of Concurrent User Licenses, or
that End User's deployment of Software on Clients exceeds the contracted ratio
of Clients to Concurrent User Licenses, End User agrees to purchase additional
licenses in compliance with this Software Schedule. For a server with a
combination of concurrent Dedicated,
Shared and/or eBusiness User Licenses, any use beyond the total aggregate
number of all Concurrent User Licenses (including previously acquired SLU type
licenses) will require additional
Concurrent User Licenses to be purchased. The highest ratio Concurrent User
License identified on the End User's configuration and its applicable fee will
be invoiced accordingly.
3. Termination
Notwithstanding the foregoing,
FileNET shall have the right to terminate End User's authorization to use the
Software if End User fails to comply with the terms and conditions of the
License. Upon notice of such termination, End User shall immediately destroy
the Software and all portions and copies thereof and, if requested by FileNET,
shall certify in writing as to the destruction of the same.
4. Disclaimer and
Limited Warranty
FileNET warrants the media on which
the Software is furnished to be free from defects in materials and workmanship
for a period of ninety (90) days from the date of purchase. FileNET's entire
liability and End User's exclusive remedy as to media shall be atFileNET's
option, either the return of the amount paid for the Software or replacement of
the media that does not meet FileNET's limited warranty and which is returned
to FileNET with a copy of the receipt.
EXCEPT AS EXPRESSLY PROVIDED ABOVE,
THE SOFTWARE AND DOCUMENTATION ARE PROVIDED "AS IS", FILENET DOES NOT
MAKE ANY AND HEREBY DISCLAIMS ALL WARRANTIES OF ANY KIND, EITHER EXPRESSED OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
The entire risk as to the quality,
accuracy and performance of the Software and the Documentation is with End
User. FileNET does not warrant that the functions contained in the Software
will meet End User's requirements or that the operation of the Software will be
uninterrupted or error free.
FILENET SHALL NOT BE LIABLE UNDER
ANY CONTRACT, NEGLIGENCE, STRICT LIABILITY OR OTHER LEGAL OR EQUITABLE THEORY
FOR ANY INDIRECT, CONSEQUENTIAL OR INCIDENTAL DAMAGES (INCLUDING DAMAGES FROM
LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION,
PROCUREMENT OF SUBSTITUTE GOODS OR TECHNOLOGY, AND THE LIKE) ARISING OUT OF
THIS LICENSE OR THE USE OF OR INABILITY TO USE THE SOFTWARE EVEN IF FILENET HAS
BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
5. Permitted Uses
This Software and the Documentation
are licensed to you, the End User, and may not be transferred to or used by any
third party for any length of time without the written consent of FileNET. You
may not modify, adapt, translate, reverse engineer, decompile, disassemble, or
create derivative works based on the Software or the written materials. Interface
information necessary to achieve interoperability is available from FileNET on
written request and payment of FileNET's then current fee.
6.
Government Restricted
Rights
The Software is commercial software
and the Software and Documentation are provided with Restricted Rights. Use,
duplication or disclosure by the Government is subject to restrictions as set
forth in paragraph (c) (1) (ii) of the Rights in Technical Data and Computer
Software Clause at DFARS 252.227-7013 or subparagraphs (c) (1) and (2) of the
Commercial Computer Software Restricted Rights at 48 CRF 52.007-19, as
applicable. Contractor/Manufacturer is FileNET Corporation, 3565 Harbor Blvd.,
Costa Mesa, California 92626.
7.
Export
Regardless of any disclosure made
by the End User or licensee to FileNET of the ultimate destination of the
Software, End User shall not export or re-export, whether directly or
indirectly, the Software to anyone outside the United States of America without
first obtaining an export license from the United States Department of Commerce
or any other agency or department of the United States Government as
required.
8. Miscellaneous
This License is governed by the
laws of California, without regard to its conflicts of laws, provisions, or the
United Nations Convention on the International Sale of Goods and will be deemed
a contract under seal. If any provision
of this License shall be held by a court of competent jurisdiction to be
contrary to law, that provision will be enforced to the maximum extent
permissible, and the remaining provisions of this License will remain in full
force and effect. This License is not assignable or transferable by End User
without prior written consent of FileNET; any attempt to do so shall be void.
Any notice, approval or consent required hereunder shall
be in writing. The parties agree that a material breach of this License by End
User would cause irreparable injury to FileNET for which monetary damages would
not be an adequate remedy and that FileNET shall be entitled to equitable
relief in addition to any other remedies it may have hereunder or at law,
Section 4 shall survive any termination of this License.
Windows 95 and 98
·
After a period of inactivity,
a Windows 98 system may go into standby mode and power down the monitor and/or
the hard disk. If IDM Desktop is running and a Windows 98 system goes into
standby mode and then becomes active again, IDM Desktop might display error
messages. If this situation occurs, you must exit from all IDM applications and
then restart them. (FR 12219)
· On Windows 95 and Windows 98, an Explorer view doesn't always refresh correctly unless version 4.01 of Internet Explorer or greater is installed.
FileNET Neighborhood (Explorer Integration)
Closing Explorer does not log you off from the library. You must manually log off from the library. If other applications are connected to the library, you must close those applications to complete the log off process.
Properties
Supplying
more decimal places than defined for an IS property generates an error when
trying to save the property changes, even though the display is correctly
updated by rounding the number to the correct number of decimal places. (FR
17729)
Searching
·
Do not place IDM Desktop
stored searches in Replication folders. Any associated custom properties in the
searches may not map correctly to comparable custom properties in the other
library systems; the replicated searches will return unexpected results.
·
If multivalued custom
properties are included in a search that uses an operator other than equals
(=), the search results will contain erroneous blank values for long text
properties.
·
On a DS library, all values
in an Oracle database are case-sensitive.
·
Incorrect
results are returned when a search condition queries data from a Document Class
that has a property type of "MENU" and the value of the field is one
character in length.
·
If you
have a stored search with a 2-digit year in an IS server, and your regional
settings are set to 4 digits, ADO will return an error. If you are using IDM
Desktop 2.0.x, the search succeeds. IDM Find does not convert 2-digit year to
fit the regional setting when opening a legacy stored search.
Date Handling
·
In Advanced Find, if you are
entering dates in the Text grid, be sure to use a format that matches your
regional settings. Errors are not always returned for incorrectly formatted
dates. (FR 11790)
·
The FileNET menus and tool
bars in Office Integration might not display properly with some graphics cards.
(FR 17815, fixed before
3.0.0 release)
· You cannot add the FileNET toolbar in the same PowerPoint 2000 session in which it was removed. (FR 15944, fixed before 3.0.0 release)
· Switching applications during a FileNET Open or Add operation while a Save As dialog is displayed, appears to freeze the display. Use Alt-Tab to bring focus to Save As and continue working. (FR 17327, fixed before 3.0.0 release)
·
Occasionally, the
FileNET Menu option does not appear. Extend.dat is not being recreated by
Outlook and causes this issue. To get the menu options to appear:
1.
Open up the Outlook
Tools \ Option dialog, and then select each of the tabs.
2.
Press OK.
3.
Exit the dialog
box, and then restart Outlook. The FileNET menus options appear. If they don't,
you can delete the extend.dat file and repeat these steps. Extend.dat should be
recreated and the FileNET Menu Option should appear.
· Compound documents cannot be added or opened from a library using Outlook integration.
·
To use Outlook integration
when Outlook 98 is installed without other Microsoft Office applications, you
must:
1. Configure and run Outlook. Verify that Outlook does not
display messages indicating that it is not ready to use.
2. Install IDM Desktop.
3. Before running Outlook, copy c:\Program Files\FileNET\IDM\idmoutl.ecf to c:\Program
Files\Microsoft Office\Office\Addins.
(FR 19297 was fixed in patch 300-1 and verified against Outlook
98. The problem does not affect Outlook 2000.)
·
While adding a new document
in Word or Excel, you can choose to overwrite a checked out document. If you do
this, the Add operation stops after the file has been overwritten. Use the Save
As functionality to rename the document, and then restart the Add operation.
Caution: When
you check in the document, the document is added to the existing version line.
(FR 17210, fixed before
3.0.0 release)
·
We recommend that you avoid
using the FileNET Open and FileNET Save commands for Excel
templates (.xlt files). Instead, use the Checkout
and Open and the Check in
commands from the shell. (FR 12820)
·
Uninstalling Excel
integration causes the Excel File Save As menu to be inoperable. To workaround
this problem, perform the following steps:
(1) On the Tools menu, click Customize.
(2) The Customize dialog box must remain open; however, you
do not use it. You might need to move the dialog out of your way.
(3) On the main application toolbar, right-click the menu
you want to restore, and then click Reset on the shortcut menu.
The Reset command restores the built-in menu to its
original image, commands, and submenus. (FR 12365)
·
While adding a new document
in Word or Excel, you can choose to overwrite a checked out document. If you do
this, the Add operation stops after the file has been overwritten. Use the Save
As functionality to rename the document, and then restart the Add operation.
Caution: When
you check in the document, the document is added to the existing version line.
(FR 17210)
·
IDM Desktop supports Lotus
Notes operations for both IS and DS libraries. From within Lotus Notes, IS
users can access library documents, add documents to a library, copy documents
to Notes records, and create links to library documents. Using a link, users
can display a document's properties, display it in the Viewer, open it in its
registered application, print it, and copy it.
·
The design of the FileNET
Notes Panagon Administrator database must be updated in order to leverage new
configuration options specific to working with IS libraries. To complete this
task, refresh or replace the design of the Administration databases in use
using the FileNET Notes Panagon Administration database included on the IDM
Desktop CD. The template name is NPI10N4P3AdminNTF.
This task
should be executed by a Notes Administrator. Items to note during this process
include:
(1)
Designer access is required to all databases that are being updated.
(2)
Design elements configured "Do not allow Design Replace/Refresh to modify.
. ." will not be updated.
(3)
Unselect "Do not allow Design Replace/Refresh to modify. . . " on the
"Using this Database" and "About this Database" documents
so that they can be updated.
·
If you copy the FileNET Notes
Panagon Administration database from the "Maintenance" subdirectory
of the installation media, you must manually remove the read-only attribute
from the NPIAdmin.nsf file before using address.
(1) In an
Explorer window, locate the NPIAdmin.nsf file in <drive>:<Notes data
directory>\FileNETNotesPanagonIntegration.
(2) Right
click on the file and select Properties.
(3)
Deselect the Read-only attribute.
(4) Click
on OK.
·
On certain systems, when the
screen color settings are set to True Color or to 16 colors, the colors of the
bitmap representing an embedded OLE object copy or checkout appear inverted
from the usual, or even black. TO avoid this problem, set the screen color
display to greater than 256 colors.
·
During Notes Integration
installation, you are prompted to specify or confirm the Notes.ini file
location. The installation process attempts to predefine this information as
follows:
(1) If
Notes 5.x is installed on your system, the installation process searches for
the Notes.ini file in the Notes program subdirectory, and if it finds it, the
program path is displayed.
(2) If
Notes 4.x is installed on your system, the installation process searches for
the Notes.ini file in the Windows program patch, and if it finds it, the
program path is displayed.
With both
Notes 5.x and Notes 4.x, if the Notes.ini file is not found in the default
location, the installation process displays the path \Notes.ini and you must
enter the appropriate path before the back slash (\).
·
The Notes Integration
installation amends the Notes.ini associated with Notes in the system registry.
To enable another Notes installation with Notes Integration, make sure that the
new installation path is listed in the system path, and add the value
"<PanagonInstallationPath>\FnNPIAddIn.Dll" to the Notes.ini
variable "AddInMenus" (multiple values for this variable should be
separated by commas). Be aware that you must use an eight-character
abbreviation for any part of the installation path longer than eight
characters.
·
On Windows 98 systems, if you
switch to another application while a Panagon Link in the form of a Notes
button is active (that is, the Link properties are displayed) and then switch
back to Notes, the IDM Link Properties display is not visible and Notes appears
to be "locked up". This problem is caused by changes in Windows
regarding modal window control. The recommended solution is to minimize the
other application windows switched to and then switch back to the Notes
application window.
·
If you do not have edit
rights to a controlled access section, a Panagon OCX Link in that section, when
activated with the Notes record in edit mode, is launched in a separate
application window. There is no known solution.
·
When selecting a version
through the Versions tab of the Properties dialog, a right-click on the version
displays the standard Open, Copy and Checkout options instead of the expected
Notes Link, Notes Copy, and Notes Checkout options. To resolve this issue,
select versions through the menu option Display Versions that is displayed when
you click on the Commands and Settings button on the toolbar of the FileNET
Open dialog.
·
Existing Panagon links
created as Notes buttons will not function after upgrading from FCS1.1 to GA.
OCX links will function correctly.
·
Older Msvcrt.dll
files may exist in your Notes program subdirectory if you are using Lotus Notes
4.6, 4.64 or any releases between those two, and must be manually deleted.
Those releases mistakenly copy the Msvcrt.dll to the Notes program subdirectory
instead of to the Windows system directory. This problem has been documented in
the Lotus Notes Knowledgebase. The existence of this older dll causes Notes
Panagon Integration to malfunction or even crash Notes. Notes Panagon
Integration installation copies a newer version of this dll to the Windows
system subdirectory.
·
Creating
a Notes Copy of an IS document as an embedded OLE object fails. The problem
occurs when there is an attempt to create an embedded OLE object associated
with the IDM Viewer, which does not support embedded OLE objects. This
situation arises when a Configuration Profile in the Administration database
specifies that Notes copies be created as embedded OLE objects. It also
identifies IS document classes or file name extensions for which the copy to be
created should be associated with in the IDM Viewer, such as an .FNI filename
extension. The Copy creation process detects this conflict and generates an
error message. The recommended solution is to select the option “embedded OLE
object if possible else file attachment” in the Configuration Settings for
creating Notes copies.
·
During
a checkin from Lotus Notes do not select the "Checkin and Checkout"
Check box on the Checkin Options dialog accessed through the command ellipses
on the final page of the Document Wizard. Checking this option, checks in the
document and immediately checks it back out again. However, the document is not
actually copied to Notes or to a local directory. If this option is
inadvertently checked, you must cancel the check out. (FR 18037)
Checkin and Checkout
After checking out/in numerous versions of a document from an 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:
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.
Drag and Drop, Cut, Copy and Paste
·
The paste operation fails if
the copy was done in a process that is no longer running. 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.
·
Cut is not supported for any
objects in Explorer, IDMTreeView, or IDMListView.
·
Copy/paste or drag of a local
file from Explorer into a library residing in a Visual Basic application's
IDMTreeView or IDMListView does not work unless you are logged on to the
library.
Compound Documents
·
Deleting a parent document
does not automatically delete all child documents. You must manually remove any
child documents that were linked to an old version of the parent document but
that are not linked to the current version of the parent document.
To identify child documents that will
not be removed when the parent document is removed use the Explore Links on the property sheet for each
version of the parent document and look for any child documents that are not
represented in the latest version of the parent document. Each of these
unrepresented child documents must be deleted manually.
·
The following OLE linked
structures cannot be added via Application Integration and must instead be
added using Explorer:
(1) A Power Point 97 parent that contains a Power Point 97
child and/or an Excel 97 child.
(2) An Excel 97 parent that contains a Power Point 97
child.
·
You cannot update a compound
document component unless it has a local path:
1. When creating or modifying a compound document, you can add
a child that resides on a mapped drive. However, the child is added with a UNC
file path, and this means you cannot check out the child document. (FR 19205, fixed in patch 300-1)
2. You can check out a compound document component to a mapped
drive. However, the child is checked out to a UNC file path, and checking it in
will create a new document instead of a new version. (FR 19206,
fixed in patch 300-1)
·
A general DBI error is thrown when attempting to
archive a child that has a checked out parent. (FR 18017)
·
Compound documents that make
use of complex links, such as circular or triangular links can only be built
using OLE‑linked documents. These types of compound documents cannot be
built using manual links.
A circular compound
document is one in which a child document has a link that leads back to the
parent document. A triangular compound document is one in which a parent
document and a child document both directly link to a third document.
·
Archiving circular
compound documents are not supported and will fail. The DS server prevents a
child from being archived unless its parent has also been
archived. In the case of a circular compound document, it doesn't matter which
document is archived first. The document will always be a child of another
document which has not been archived. Archiving a circular compound document
will fail with the failure description "The archive operation failed because
the parent is not archived."
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.
Viewing
·
You might see the message
"Error in dispatch method" when viewing a document. This error is
benign and can be ignored.
·
The Viewer does not display
form fields and special characters in Microsoft Word documents. Microsoft Word
documents containing form fields and special characters should be opened in
Word. (FR 4925)
·
The Viewer does not support:
(1)
Scrolling using the Microsoft mouse thumbwheel with Inso documents. You can use
this facility with native FileNET documents. (FR 15986)
(2)
Display of 1-bit color bitmaps. (FR 18398)
·
Using the Internet Explorer's
Save as command to save a PDF file that is being viewed, results in an empty
file being saved.
·
When there is no printer
configured, the print dialog does not display when you select the IDM Viewer's
Options/Print item on the context menu of an Inso document. Defining a default
printer, resolves this issue.
·
Printing PowerPoint documents
in landscape mode might cause the printing status dialog to hang and for
clicking on the cancel button in the print status dialog to cause the Viewer
screen to turn blank. These issues occur with a limited set of postscript
problems only.
·
The Print Annotation/Use
Transparency option under the Print dialog prints annotations accurately.
However, the image quality is downgraded, and the time and resources required
to print is increased.
·
In the Local Print dialog,
the Print Option's default setting "Use Original Document formatting, if
available" is always disabled.
·
You cannot print .txt
documents to a FileNET printer via Panagon Print 4.1.
·
If the image of a Microsoft
Office documents appears to be cut off from the right or does not print in
landscape mode when appropriate, right click on the document inside the viewer,
then click the Options/Print on the context menu, and check the 'Use Original
document Formatting if available' checkbox.
·
The scale factor is not
always available programmatically when a database or spreadsheet has many
columns.
·
After adding a custom property
to a document class on the source library, users cannot log into the target
libraries until after two replication cycles. During the first replication
cycle, the source library is accessible but the target libraries are not. All
libraries are inaccessible during the second replication cycle.
Removing IS Support from Web Server
If you
remove IS library support from a web server, you will not have access to
libraries until you run the following command using the Windows run command: regsvr32 fndoc.dll. (FR 20262, fixed in 300-2)
Internet
Explorer
Accessing
Help
During the installation of Panagon
Web Services, if you click on the help button, an error might display informing
you that the system cannot locate the file admin_w.hlp. If this message displays,
use the Browse button on the message pop-up to locate the file, which is in the
root directory of the CD.
Bookmarking
Facility
Use the bookmarking facility
provided with the Panagon Web Services application rather than the IE Add to
Favorites option. Using the IE Add to Favorites to bookmark application pages
can lead to unexpected results.
Context
Menus
If you right click on an item in
the Panagon Web Services application, the Internet Explorer 4.01 context menu
displays. The items on the menu are not integrated with the Panagon Web
Services 3.0.0 application and their use produces unexpected results.
You
cannot use SQL trace logging on a web server at the current time. When SQL
trace logging is on, you cannot reboot the server and restart the necessary
services. (FR 19310) To recover:
1. Turn off SQL trace logging.
2. From the Control Panel, choose
Services, stop the World Wide Web Publishing Service.
3. Reboot the web server.
Web clients can access the web
server after these steps complete.
The Panagon Web Services
application makes extensive use of frames, as a result using the Internet
Explorer Back button can produce unexpected results.
Color
Scheme
The out of the box applications do
not use the color scheme configured on your desktop.
Display
of Pop-up Windows
Each pop-up window can be
minimized and maximized. However, if you maximize the pop-up window, the
display of some of the fields and titles might not be altered in proportion.
A web client with Author access
rights to a document will receive the following error when checking in the
document:
"An invalid value was entered
for a property. The property was <document class control property>. The
value was <document class>. The document has been checked in
successfully."
To work around this problem, the DS
system administrator can either:
·
Change the Author privileges
field in the document class control object's custom property from read (the
default) to read/write.
·
Give Owner access rights to
the web client. (FR 19711)
Checking
Out a JPEG Document
If you check out a .JPG document
using the sample 2.0 web pages, then use Save As to save the file, the result
will be an HTML page pointing to the .JPG file, which is saved in a new folder
named <name>_jpeg_files.
Opening
Multiple Internet Explorer Windows
If greater than 100 pop-up windows
have been opened, your system might run out of resources. To regain the
resources, stop and restart Internet Explorer. Microsoft has documented this
problem with knowledge base article Q235674, available at
http://support.microsoft.com/support/kb/articles/q235/6/74.asp
A patch to Internet Explorer is
available from Microsoft by following the directions in the article.
On Windows 98 systems, you can use
the Resource Manager to obtain automatic notification when resources are
running low. Go to Start->Programs->Accessories->Tools->Resource
Manager to turn on the Resource Manager.
Searching
·
If you use the Add Document
facility from search mode, the document is always added at the root level. To
move the document to a particular folder, search for the document and then use
the copy facility.
·
Searches that were created
using 2.0.x software and that are stored in a library can be successfully
executed using the Panagon Web Services 3.0.0 application. However, storing
these searches on the web server and executing them from the search drop down
list is not supported.
To make the searches available on the web server, you must
open them using the Find Application and then resave them on the web server.
Web Preferences and Library Configurations
The
following features, which are accessible via the Configure program on the web
server, have limitations:
·
No checking is performed on
the guest user account to ensure that the specified account is a valid DS user
name.
·
Unified logon does not work
for web clients. The “Use operating System
Credentials for Logon” preference is ignored for all libraries. (FR 19250, fixed in 300-1)
·
Some of the preferences, for
example the library preferences affect the web clients and the use of the IDM
Desktop applications on the web servers. Other preferences, for example checkin
and checkout preferences, affect only the use of the IDM Desktop applications
on the web server.
You can alter the default columns
seen in browse mode by the web clients and you can decide whether an icon
marking that a document has annotations should be displayed on the web client.
Both of these options are available using the Desktop integration on the web
server.
To alter the columns, on the web
server:
1. From the Desktop Explorer, log on to the appropriate IS or
DS library.
2. Select View -> Options from the drop down menus.
3. Make the appropriate the column selections.
4. Apply the changes.
5. Web clients will pick up the change when they restart their
browser session.
By default, web clients will not
see an icon identifying that a document has annotations. To turn on the option
so that web clients can see which documents have annotations, perform the
following procedure:
1. From the Desktop Explorer, log on to the appropriate IS or
DS library.
2. Select View -> Options from the drop down menus.
3. Select the option Show Annotations.
4. Apply the changes.
5. Web clients will pick up the change when they restart their
browser session.
Note that turning on the “Show
Annotations” option can negatively impact performance.
ASP Timeouts
If you
receive an ASP timeout, use the browser’s Refresh button. This action resets
the web application and enables you to continue working normally.
Opening Microsoft PowerPoint Files
If you do
not have Microsoft PowerPoint installed on your web client, opening a
PowerPoint file fails with the error "Access to the specified device,
path, or file is denied." This is a Microsoft issue. This problem does not
affect your ability to view PowerPoint files. (FR9528)
Opening Documents When the Native Application Is Not
Installed on the Web Client
On the web client, if the native application doesn't exist
and the Open button on the task bar is used to open the document, the error
"filename string invalid" displays if the file you are trying to open
has a space in its name. If this situation occurs, use the View button to look
at the document. (FR12731)
Administration for Panagon Web Services on IIS Servers
In order to
run the Panagon Web suite under Microsoft IIS and Active Server Pages, a set of
out-of-process Panagon 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 components after making a change to the NT user account, a
Web client might receive the following error message when trying to access the
Panagon Web suite:
Server object error 'ASP 0177:80080005'
Server.CreateObject Failed
<Drive>:\INETPUB\WWWROOT\IDMWEB\GLOBAL.ASA, line 122
The call to
Server.CreateObject failed. The requested object instance cannot be created.
To reconfigure the Panagon
components on a primary domain controller, enter the following from a command
window:
FnLogSvr
/RegServerDCOM <domain\username> <password>
To reconfigure the Panagon
components on a stand-alone server, enter the following from a command window:
FnLogSvr
/RegServerDCOM <machinename\username> <password>
Panagon
Web Pages and Viewing on the Web Client
·
If you try to view a file,
which has a file type that the IDM Viewer doesn't recognize, then you will be
asked twice if you want to open the document. If you answer yes to the
questions, then the document is opened using an appropriate tool on the web
client.
·
If you make regular use of
Acrobat PDF files, FileNET recommends that you use Adobe Acrobat Reader 4.0 to
view the files. The Adobe Acrobat Reader can be installed from the Acrobat
directory on the Panagon Web Services CD.
·
Using the Internet Explorer's
Save as command to save a PDF file that is being viewed, results in an empty
file being saved.
·
Printing PowerPoint documents
in landscape mode might cause the printing status dialog to hang and if you click
on the cancel button in the print status dialog, the Viewer screen might turn
blank. These issues occur with a limited set of postscript printers only.
· If you display a document’s properties from the Viewer application, you must use the mouse to navigate between tabs and to fields; the tab and arrow keys are not supported.
·
In the Local Print dialog,
the Print Option's default setting "Use Original Document formatting, if
available" is always disabled.
·
If the image of a Microsoft
Office documents appears to be cut off from the right or does not print in
landscape mode when appropriate, right click on the document inside the viewer,
then click the Options/Print on the context menu, and check the 'Use Original
document Formatting if available' checkbox.
·
The scale factor is not
always available programmatically when a database or spreadsheet has many
columns.
·
The print option in the IDM
Viewer may sometimes be grayed out even through the document is printable. This
an Internet Explorer issue. To work around the problem, use Ctrl-P or the print
button on the tool bar.
·
To save a document so that it
can be opened directly by the viewer running on the desktop rather than through
a browser session:
(1) View the document in the normal fashion from a web
client.
(2) When the document displays in the browser, select and
copy the document.
(3) Paste the document into Paint and then save the file
with a .FNI extension on your web client machine.
(4) Initiate the idmview.exe application.
(5) Open the file
·
The
Viewer causes GPF errors on Win9x systems
If you
use the Viewer Control available in the 2.0 sample pages on a Windows 9x
client, a GPF error might occur when you close the Internet Explorer browser.
The
problem is caused by a Microsoft limitation in which the MFC assumes that it is
always executing in the same thread and on Win9x machines, this assumption is not always true and, as a result,
causes the Internet Explorer to crash on closure.
The
following Microsoft article documents this issue:
ID:
Q271208
Title: BUG: Crash in MFC42(d).DLL During Process Exit on
Win9x
Microsoft
has stated that this issue cannot be resolved in the current release as the
release is tied to the MFC's architecture. They are considering fixing this
problem in a future release. However, at this time, FileNET does not have a
workaround or solution for this problem. (FR 20897)
Changing
IS Library Passwords
If you change an IS password from
a web client, you must log off the IS library and log back on again before
continuing with your web client session. (FR16299, fixed in patch 300-1)
Using
NT Challenge/Response (NTC/R) To Secure Web Sites
If Panagon Web Services is
installed on a web server that uses NTC/R, all the sites on the web server must
be secured with this level of security. You cannot access Panagon Web Services
with anonymous access if another site on the web server is using NTC/R.
(FR14496)
Supplying more decimal places than defined for an IS property generates an error when trying to save the property changes, even though the display is correctly updated by rounding the number to the correct number of decimal places. (FR 17729)
When
using the Panagon web client with Internet Explorer 4.01 with Service Pack 2 on
Windows 98, tabbing between property pages may hang. (FR 19350)
Compatibility/Coexistence
with Other FileNET Products
The following information provides
details on the compatibility between the 3.0.0 release of IDM Desktop and
Panagon Web Services and other FileNET products.
IS
and DS Services
IDM Desktop and Panagon web
clients are certified for access to the following libraries:
IDM Desktop 3.0.0 can be
co-located with DS 5.1 and DS 5.1 System Administration Tools on the same Windows NT server.
IDM
Desktop 3.0.0 cannot be co-located with DS 4.3 or the DS 4.3 administrative
tools.
IDM
Desktop 3.0.0 cannot be co-located with Rendition Services.
Panagon Web
Services includes its own web client and administrative tools. Do not install
IDM Desktop, IS, DS, or any DS server component (such as a remote Storage
Manager) on the same machine with Panagon Web Services.
Using Panagon web client on the
same server as IS or DS is not supported.
Compatibility with @mezzanine 2.0.1
The products @mezzanine 2.0.1 and
Panagon Web Services are not compatible and cannot be installed on the same
server. Rendition Services cannot be run on the same server.
WorkForce
Desktop (WFD) 5.03
IDM Desktop can coexist on the
same PC with WFD 5.03. However, FileNET does not support the coexistence of IDM
Desktop and WorkFlo Controls for Visual Basic within the same application.
Saros
Document Manager (SDM)
IDM Desktop coexists on the same
PC as Saros Document Manager (SDM). IDM Desktop does not support the following
legacy features: SDM smart folders, document references, and stored searches
saved using Mezzanine or the Mezzanine API.
Panagon
DS Capture Desktop
IDM Desktop and Web Services 3.0.0
can be used with the FCS version of Panagon DS Capture Desktop.
Before you install Panagon DS
Capture Desktop, you must first install IDM Desktop and set the prefetching priority as follows:
Currently IDM Desktop and Web
Services is not qualified to run with Panagon Capture Professional.
PWP
Station
Panagon Web Services cannot be co-located on the same
system as PWP Station.
Panagon
Print, Panagon Fax, WorkFlo/Print
IDM Desktop cannot be co-located on the same PC
with Panagon Print, Panagon Fax, or WorkFlo/Print. Likewise, Panagon Web
Services cannot be co-located on the same PC with Panagon Print, Panagon Fax,
or WorkFlo/Print.
Panagon
Visual WorkFlo
IDM Desktop can be used on the same system with Panagon Visual WorkFlo 2.01, 3.0, 3.01, and 3.02.
Panagon
Integrated Workflow 1.2.4 (Ensemble)
Panagon Integrated Workflow does not support the use of IDM Desktop stored searches and stored search templates.
IDM Desktop and Panagon Web
Services 3.0.0 are integrated with Report Manager 4.0. This means you can use the IDM Viewer to display Report
Manager documents cross-cataloged to IS libraries. Before you can do this,
however, you must set up one of two Adobe Acrobat environments:
Effective 5/1/2000, Panagon Web
Services no longer supports the Site Server integration preference.
Downloading
Patches and Files
After you install Panagon IDM
Desktop or Panagon Web Services, check the FileNET Customer Support site for
the latest information and software patches. The ftp site from which you
download the patches contains readme files describing the fixes contained in
each patch.
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 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 ensure 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 files/fixes - FTP link.
5. Select the directory client_fixes.
6. Select the file IDMdesk-web.html to list the releases that have available patches.
7. Select the directory for the Panagon 3.0.0 release.
8. Select the directory for the software patch. This lists the software executables and text files in the patch.
9. Review the readme file for installation instructions and information on the fixes provided in the patch.
To
download the readme file
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 ensure 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 Product Release Notes link.
5. Scroll to the heading Panagon Desktop – Web Services.
6. Select Panagon IDM Desktop/Web 3.0.0 Readme.
SMS 2.0 can be used to deploy IDM Desktop and Panagon Web Services client packages to computers without end user intervention. All silent install features supported by IDM Desktop and Panagon Web Services can also be used with SMS 2.0.
SMS 2.0 can be used to install IDM Desktop 3.0.0 as an initial installation on client computers, and can also perform upgrade installations on client computers that are running IDM Desktop 2.0.3 or IDM Desktop 3.0.0 FCS1.1. You can also install patch releases for IDM Desktop 3.0.0 via SMS 2.0.
After completing the installation of IDM Desktop 3.0.0, import the IDM Preference files by creating another SMS package. See the specifications at the end of this document for the SMS Package Definition File (PDF) input.
Currently, IDM Desktop does not support a silent mode process for adding IDM Desktop components, or for uninstalling the product. You can use SMS Installer 2.0 to accomplish these tasks.
The installation of the Panagon Web Services client packages (Viewer, Viewer2, FnControls) to web client computers is supported with SMS 2.0. SMS 2.0 can be used to install Panagon Web Services 3.0.0 client packages as initial installations, or as upgrades from 2.0.3 or 3.0.0 FCS1.1 releases. The installation of server side Panagon Web Services software is not supported
To deploy IDM Desktop or
Web Services using SMS 2.0, you must create Systems Management Services packages. Below is a sample SMS Package Definition
File (PDF) that can be used to create your SMS client packages.
Refer to the IDM Desktop
and Panagon Web Services Administrator online help for information on quiet
installs and configuration files syntax.
[PDF]
Version=2.0
[Package Definition]
Publisher=FileNET
Name=IDM Web Client
Version=3.0
Language=English
;******* Comment optional:
;Comment=
Programs=ViewerInstall, Viewer2Install, ViewerUpgrade, Viewer2Upgrade, FncontolsInstall, FncontrolsUpgrade
;MIFVersion=
[ViewerInstall]
Name=ViewerInstall
CommandLine=Viewer\Viewer.exe -s -a -iC:\idm\MyConfig.ini -s -f1setup.iss
AdminRightsRequired=True
UserInputRequired=False
DriveLetterConnection=False
AfterRunning=SMSRestart
CanRunWhen=WhenUserLoggedOn
SupportedClients=Win NT (I386), Win 9x
Win NT (I386) MinVersion1=4.00.0000.0
Win NT (I386) MaxVersion1=4.00.9999.9999
Win NT (I386) MinVersion2=5.00.0000.0
Win NT (I386) MaxVersion2=5.00.9999.9999
Win 9x MinVersion1=0.00.0000.0
Win 9x MaxVersion1=99.99.9999.9999
[ViewerUpgrade]
Name=ViewerUpgrade
CommandLine=Viewer\Viewer.exe -s -a -s -f1setup.iss
AdminRightsRequired=True
UserInputRequired=False
DriveLetterConnection=False
AfterRunning=SMSRestart
CanRunWhen=WhenUserLoggedOn
SupportedClients=Win NT (I386), Win 9x
Win NT (I386) MinVersion1=4.00.0000.0
Win NT (I386) MaxVersion1=4.00.9999.9999
Win NT (I386) MinVersion2=5.00.0000.0
Win NT (I386) MaxVersion2=5.00.9999.9999
Win 9x MinVersion1=0.00.0000.0
Win 9x MaxVersion1=99.99.9999.9999
[Viewer2Install]
Name=Viewer2Install
CommandLine=Viewer2\Viewer2.exe -s -a -iC:\idm\MyConfig.ini -s -f1setup.iss
AdminRightsRequired=True
UserInputRequired=False
DriveLetterConnection=False
AfterRunning=SMSRestart
CanRunWhen=WhenUserLoggedOn
SupportedClients=Win NT (I386), Win 9x
Win NT (I386) MinVersion1=4.00.0000.0
Win NT (I386) MaxVersion1=4.00.9999.9999
Win NT (I386) MinVersion2=5.00.0000.0
Win NT (I386) MaxVersion2=5.00.9999.9999
Win 9x MinVersion1=0.00.0000.0
Win 9x MaxVersion1=99.99.9999.9999
[Viewer2Upgrade]
Name=Viewer2Upgrade
CommandLine=Viewer2\Viewer2.exe -s -a -s -f1setup.iss
AdminRightsRequired=True
UserInputRequired=False
DriveLetterConnection=False
AfterRunning=SMSRestart
CanRunWhen=WhenUserLoggedOn
SupportedClients=Win NT (I386), Win 9x
Win NT (I386) MinVersion1=4.00.0000.0
Win NT (I386) MaxVersion1=4.00.9999.9999
Win NT (I386) MinVersion2=5.00.0000.0
Win NT (I386) MaxVersion2=5.00.9999.9999
Win 9x MinVersion1=0.00.0000.0
Win 9x MaxVersion1=99.99.9999.9999
[FncontolsInstall]
Name=FncontrolsInstall
CommandLine=fncontrols\fncontrols.exe -s -a -iC:\idm\MyConfig.ini -s -f1setup.iss
AdminRightsRequired=True
UserInputRequired=False
DriveLetterConnection=False
AfterRunning=SMSRestart
CanRunWhen=WhenUserLoggedOn
SupportedClients=Win NT (I386), Win 9x
Win NT (I386) MinVersion1=4.00.0000.0
Win NT (I386) MaxVersion1=4.00.9999.9999
Win NT (I386) MinVersion2=5.00.0000.0
Win NT (I386) MaxVersion2=5.00.9999.9999
Win 9x MinVersion1=0.00.0000.0
Win 9x MaxVersion1=99.99.9999.9999
[FncontrolsUpgrade]
Name=FncontrolsUpgrade
CommandLine=Fncontrols\Fncontrols.exe -s -a -s -f1setup.iss
AdminRightsRequired=True
UserInputRequired=False
DriveLetterConnection=False
AfterRunning=SMSRestart
CanRunWhen=WhenUserLoggedOn
SupportedClients=Win NT (I386), Win 9x
Win NT (I386) MinVersion1=4.00.0000.0
Win NT (I386) MaxVersion1=4.00.9999.9999
Win NT (I386) MinVersion2=5.00.0000.0
Win NT (I386) MaxVersion2=5.00.9999.9999
Win 9x MinVersion1=0.00.0000.0
Win 9x MaxVersion1=99.99.9999.9999