This document describes known issues and restrictions in the 3.2.0a and 3.2.0b releases of the IDM Desktop, Web Services, and Open Client. It includes workarounds and information on fixes, when available, and corrects errors in the documentation. Patches are released periodically, which may include documentation updates. See the readme file for information on how to download patches from the FileNet FTP site, and see the patch readme file for a description of the patch contents and how to install it.
As of 9/8/03, all FRs were assigned a new DTS defect number. Except for problems fixed before 9/8/03, problem report numbers in this document now include the associated Failure Report (FR), a colon, and the new defect number. Please use the new defect for reference and tracking.
Known issues are grouped as follows:
Windows and Internet Explorer Issues
SDM and Mezzanine Support Limitations
Installation and Configuration Issues
Known Problems in Web Services
Known Problems in ActiveX Client and HTML Samples
Known Problems in Web Services Application Integration
Known Problems in Open Client with eProcess
Known Problems in IDM Desktop Application Integration
To perform any of the following installations on Windows NT, Windows 2000, and Windows XP systems, the user must have local Administrator rights on the machine:
· Web Services
· ActiveX Clients, including support for IDM Viewer
· Web Services application integration
· IDM Desktop and any of its components
· IDM Desktop application integration
After installation, you must reboot before using IDM Desktop, Web Services or any of the web services ActiveX Clients or before installing other software. Installation is not complete until the system is rebooted and the components are registered. The user who initiated the installation must log in after the reboot so that the registration completes correctly.
These security limitations do not apply to customers using Web Services Open Client and Java Viewer.
At runtime to use any of the Web Services or IDM Desktop components, users must have permissions that allow them to access the Windows Registry. The rights required for registry access vary depending upon the operating system.
Windows 2000 includes a security template, compatws.inf, for modifying the ACLs of legacy applications. The template is located in the %windir%\security\templates directory. You can modify the security template for users in a manner consistent with the requirements of most legacy applications. You cannot disable the built-in permissions allotted to Power Users. The following articles provide more information on setting security for applications:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/confeat/securcon.asp
http://www.microsoft.com/TechNet/prodtechnol/winxppro/proddocs/sag_SCEdefaultpols.asp
After installing updates to Windows or Internet Explorer, you will get an "HTTP 404 - File not found" error when accessing Web Services if the web server has an underscore in its name, such as web_server. This problem is not exclusive to Web Services.
Cookies on Active Server pages (ASP) are blocked if the server name contains characters that are not supported by Domain Name System (DNS). For example, you cannot use underscore characters (_) in the server name. This behavior is by design.
This issue occurs after installing any of the following items:
· Q316059 MS02-005: February 11, 2002, Cumulative Patch for Internet Explorer
· Q319182 MS02-015: March 28, 2002, Cumulative Patch for Internet Explorer
· Q321232 MS02-023: May 15, 2002, Cumulative Patch for Internet Explorer
· Q323759 MS02-047: August 22, 2002, Cumulative Patch for Internet Explorer
· Internet Explorer 6 Service Pack 1 (SP1)
· Windows 2000 Service Pack 3 (which includes Internet Explorer 5.01 Service Pack 3)
To work around this issue, do the following:
· Use only characters that are supported by DNS when naming your web server.
· Use the IP Address of the web server when accessing the web server.
Support is not provided for the following items created with SDM: smart folders, document references, renditions, and compound documents. See the CS Upgrade Notes for information on how to convert smart folders to stored searches.
Support is not provided for stored searches created with the @mezzanine API.
If you are a previous SDM user and you experience performance problems after upgrading the library to CS 5.1.1, the library administrator should run the VUPDATE utility. The utility is installed with the CS library software.
Multi-page TIFFs in a multi-page IS document are not supported. IS supports multi-page TIFFs in a single-page document and single-page TIFFs in a multi-page document.
If a stored search against an IS library includes dates with a 2-digit year (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.
· IS supports the dates 1/1/100 through 3/10/9999. However, using Web Services and IDM Desktop:
o The Date Control only supports dates 1/1/1400 through 12/31/2400
o 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:
o Do not detect that the date 3/11/9999 is invalid. (FR 18456:34452)
o Do not always detect invalid dates when you tab in and out of fields. (FR 18462:34454)
o Do not prevent users entering more than 4-digit years. The extra digits are ignored. (FR 18460:34453)
o 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.
Web Services and IDM Desktop installation includes WAL 3.5 modules. If you are using IS servers, please ensure you have installed the latest WAL patches on all your IS servers.
Supplying more decimal places than defined for an IS property generates an error when trying to save the property changes. However, the display is correctly updated by rounding the number to the correct number of decimal places. (FR 17729:34094)
The IS library preference, "Maximum IS folders to display," is not available after upgrading from 3.1 to 3.2. (DTS 43920, 43712)
The CS 5.1.1 option for using the Document ID as the file name for a checkout or for a copy operation is not supported.
· 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.)
· 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.
The Windows 98 operating system does not support cross-domain trust relationships. As a result, to use the Direct Shelf Access (DSA) feature from a Windows 98 desktop, your client machine must exist in the same NT Domain as the CS server.
· 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 2000 and Office XP can be detected using a later version of the authoring application. Documents created with an Office version prior to Office 2000 must be updated to Office 2000 format (or a later version) to enable the detection of OLE links.
· A general DBI error is thrown when attempting to archive a child that has a checked out parent. (FR 18017:34239)
· 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 is not supported and fails with the error, "The archive operation failed because the parent is not archived." The CS 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.
· When you check out a compound document, with a child document that needs to be checked out to a nonexisting directory, the software creates a new directory and checks out the child document into that directory. When you check in the document and choose to remove the local copies, the child document will be deleted. The directory is not deleted. (FR 15666:33113)
· After adding or checking in a compound document using the custom recognizer plug in, the child action displays a failure status. (FR 23361:39357)
External Documents and Archived Documents
To open external and archived documents, you must browse to the document or execute a search. You cannot open external or archived documents by entering a document ID in the address line.
You must delete the ODBC Data Source before uninstalling IDM Desktop. If you uninstall IDM Desktop first, you will need to reinstall it in order to delete the ODBC Data Source.
Unified logon is not compatible with the Windows NT Scheduler service, which performs scheduled tasks. The scheduler logs on to the desktop as a specific user. Before the scheduler logs on, unified logon works as expected. After the scheduler runs, the incorrect user is logged onto FileNET libraries.
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 Web Services in a WAN environment, optimize performance by locating the web server and the CS or IS server on the same Local Area Network (LAN).
Poor response times can occur when browsing IS libraries with a very large number of folders. If you experience performance issues, consider redesigning the folder structure or avoid folder browsing.
Normally, Open Client's Setup program creates a virtual directory, which becomes part of the URL used to access the Open Client web site. After applying Windows 2000 SP3 or SP4 and a Microsoft security updates to a web server, Open Client installation will abort if Setup cannot create the virtual directory.
If you have not yet installed, you can work around this problem by creating the installation directory and the virtual directory before installing Open Client, as follows:
Create the installation directory. The default is C:\Program Files\FileNET\IDM\Web\FNOpenClient.
Right-click My Computer, and then select Manage.
Expand Services and Applications, Internet Information Services, and Default Web Site.
Right-click on Default Web Site, select New, and then select Virtual Directory.
In the Virtual Directory Creation Wizard, click Next.
Enter the name of the virtual directory, and then click Next.
Enter or browse to the installation directory you created in step 1, and then click Next.
Check the first two access permissions ("Read" and "Run scripts"), click Next, and then click Finish.
Install Open Client.
If you tried to install Open Client and Setup aborted, delete any virtual directory that Setup created and create a virtual directory using steps 2 through 8 of the procedure above. If Open Client still does not work correctly after this, uninstall it and use the procedure above.
In the IDM Desktop Administrator's Help and in the Web Services Adminstrator's Help, in the topic "Configure ODBC Data Source for each CS database server," make the following update to step 5. The update adds information on configuring access to a CS 5.3 library with an Oracle database on a Solaris server.
Enter the Data Source Name and the server name:
- For a CS 5.3 library with an Oracle database on a Solaris server, the Data Source Name and server name entered here, and the server name entered in IDM Configure, must match the VCatServerName, which is the Network Service Name entered during Content Services installation.
- For all other CS libraries with an Oracle database, enter the Data Source Name (use the server name), and enter the server name again.
If you attempt to upgrade an earlier release to 3.2 on a Windows 95 machine, which is not a supported platform for 3.2, the upgrade will start and then hang. (FR 36254:38694)
Using IDM Configure, you can choose the folder to use for cached files. Always assign a folder that is used exclusively for caching files. When you uninstall Web Services or IDM Desktop, the cache folder and its entire contents are deleted. (FR 23511:37752)
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.
Preferences
Preference files created in earlier versions of Panagon Web Services and IDM Desktop cannot be imported into the 3.2.0 environment.
Netscape servers cannot be used with Web Services. See the 3.2.0a Platform Requirements for information on browser support.
If you are printing stamp annotations to an HP4 or HP5 printer from a Windows 98SE PC, we recommend the printer settings below.
· On the Graphics tab, select:
Dithering: Fine
Intensity: 99
· Use Raster Graphics
o On the Fonts tab, select Print TrueType as Graphics.
o On the Device Options tab, select RET - Printer Default.
In addition, if the stamps are rotated, we recommend a dark text color.
The Print Annotation/Use Transparency option under the Print dialog prints annotations accurately to match the display. However, this degrades image quality and increases the time and resources used to print.
The following issues occur on a limited set of Postscript printers:
· Printing PowerPoint documents in landscape mode can cause the printing status dialog to hang.
· Clicking on the cancel button in the print status dialog can cause the Viewer screen to turn blank.
Printing fax images in scale to width, scale to height, or whole mode does not always function correctly.
· You cannot print .txt documents to a FileNET printer via Panagon Print 4.1.
· The scale factor is not always available programmatically when a database or spreadsheet has many columns.
· Use the Enhance mode with multipage G3 Fax TIFF images. Other modes do not work properly.
· If certain virus protection software is running on a server where Web Services is located, then that virus protection software may cause errors when users try viewing asp pages. Refer to the Microsoft Knowledge Base article Q248013 for more information. To work around this issue, add the global.asa file in the IDMWeb and in the IDMWS directories to the list of files that your virus checker does not scan.
· Slow installation can occur if Virus Checking Services are running.
· If you are currently using McAfee Virus Scan and your current virus definition dat file is 4165 on a client machine, you may get a false positive virus warning on the IDMLaunch.exe file. This occurs on Windows 98SE and NT4 client machines. Update your dat file before installing Panagon.
To use anonymous authentication for access to libraries through Web Services in conjunction with secure sites on the same web server, you must edit the registry as follows:
1. Run regedit.
2. Open HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Internet Settings.
3. Add the DWORD value "DisableNTMLPreAuth" and set it to 1.
Web Services supports 128-bit SSL with the following exception: Documents are not viewable through the IDM Viewer. To view documents in an SSL environment with the IDM Viewer, you must:
Set IIS to ignore certificates.
On the web client, have a valid client certificate installed.
Web sites that use SSL cannot be accessed via application integration. During setup, supplying a URL that starts with https:// displays an empty FileNET neighborhood when you try to open a document. Attempts to set a URL from within Word, PowerPoint, Excel, or Outlook that starts with https:// results in an "invalid URL" message being displayed. (FR 23524:37758, fixed in patch 1)
In order to run the Web suite under Microsoft IIS and Active Server Pages, a set of out-of-process IDM components must be configured using the administrative NT user account as explained below. If you make changes to this account, such as a password change or account expiration, you must reconfigure the IDM components.
If you do not reconfigure the 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 IDM components on a primary domain controller, enter the following from a command window:
FnLogSvr /RegServerDCOM
<domain\username> <password>
To reconfigure the IDM components on a stand-alone server, enter the following from a command window:
FnLogSvr /RegServerDCOM
<machinename\username> <password
When a Web Services client is installed on a Windows XP machine, the system PATH environment variable is not always updated correctly. As a result, you might experience problems such as not being able to add documents to an IS server when the document class contains numeric properties. To work around this problem, manually update the system path to include the location of the Web Services software. (FR 37164:40868, fixed in patch 4)
For correct operation, the Microsoft VM (Java Virtual Machine) must be installed on the web client. ActiveX Client users on Windows XP workstations must install the VM. See the readme file for instructions.
The Web Services application uses frames, and as a result, using the browser's Back button can produce unexpected results.
Each pop-up window can be minimized and maximized. However, if you maximize a pop-up window, the display of some of the fields and titles might not be altered in proportion with the window.
When you check out a .JPG document using the HTML Samples, the document opens in the browser. If you then use the browser's Save As option to save the file, the file is saved as an HTML page pointing to the .JPG file, which is by default renamed <file name>_jpg.
If a user opens more than 100 pop-up windows, the user's workstation can 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/q235674.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.
Searches that were created using 2.0.x software and that are stored in a library can be successfully executed using the ActiveX Client. 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.
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.
· 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. (FR 12731:32173)
· 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. (FR 9528:45181)
· PowerPoint documents accessed from the ActiveX pages do not open correctly in a browser. The Microsoft Knowledge Base article Q314535 has been written to address this issue. At the time this document was posted, the Knowledge Base article was not generally available. Please refer to the Microsoft Support Database or contact Technical Support for more information.
· After you download and run viewer.exe to install the ActiveX Client, you must reboot the machine before viewing documents through the HTML Sample pages. (FR 36835:40761)
· The error "Unable to retrieve documents with this format" may occur when a user tries to retrieve and view documents with the HTML Sample pages. The problem seems to occur primarily on machines running Office XP and IE 6. To work around this problem, view documents using the ActiveX Client. (FR 36821:40756)
·
Using the Internet Explorer's Save
As command to save a PDF file that is being viewed, results in an empty file
being saved.
· To save a document so that it can be opened directly by the IDM 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.
· Web Services application integration does not support LDAP log on. (FR 36469, fixed in patch 4)
· You can open only the first page of a multiple page IS document using application integration. (FR 23012:37594)
· The tabbing order is incorrect on some document property pages. (FR 21497:37104)
· The Open command does not always work in Outlook XP running on a Windows 98SE machine. (FR 37247:40912)
Be sure to also check for Installation and Configuration Issues related to Open Client and add-ons.
With JRE1.4, Euro characters and some extended characters do not work correctly. You can work around the issue for the Euro character by using the Windows Character map. To workaround the issue for extended characters, press Shift + "{" or Shift +"[" to input the extended characters. (FR 41804:42501)
IS and CS drop-down boxes for CVL and EVL property lists display a maximum of 1000 values.
To run Open Client 3.2 and McAfee NetShield Anti-Virus Software on Windows 2000 Server, NetShield v4.5 with Service Pack 1 for NT and Windows 2000, or a later version, is required.
If you experience poor response times when using the Open Client, and you have virus-checking software on your web server, update your virus checker setup to prevent it from scanning the directory in which you installed the Open Client software.
Once you log in to a FileNET library from a Netscape browser, additional Netscape browser windows retain the same login status. For example, if you start Netscape and log in to a FileNET library, then open another browser window, the new window accesses the same library without having to log in again. If you log out from the library from either window, then the same library will also be logged out from the other window as well.
This behavior is unlike that of Internet Explorer, where each browser window has its own login session to the FileNET libraries. From one Internet Explorer window, whatever you do to the FileNET library won’t affect the other existing Internet Explorer window.
If you are loading the Open Client project into Visual Studio .NET GA and attempt to recompile the project, you may encounter errors if a virtual directory name other than FnOpenClient is selected during the Open Client installation process. The following are steps that should resolve these errors:
1. Create a virtual directory named FnOpenClient that points to the Open Client Installation directory.
2. Locate the Open Client project file (FnOpenClient.vbproj) in the Open Client installation directory and open the file in Visual Studio .NET GA.
3. Make your changes.
4. Recompile the project. In rare cases, missing references to IDMObjects and JiGlue may cause the compilation to fail. If this occurs, use the project browser to remove IDMObjects and JiGlue from the project references, manually re-add them, and recompile the application. You can locate IDMObjects and JiGlue in the BIN subdirectory within your Open Client installation.
5. To debug the application, set the default.aspx page as the initial page.
OpenClient grants full control access for the aspnet_wp account in the following registries and their subkeys. Note that HLM is used as a short cut for HKEY_LOCAL_MACHINE:
1. [HLM/SOFTWARE/ODBC]
This setting is required to support CS content search functionality.
2. [HLM \SYSTEM\CurrentControlSet\Services\Eventlog]:
This is required for event logging.
In addition, Open Client creates the following registry keys:
3. [HLM \SYSTEM\CurrentControlSet\Services\Eventlog\Application]: RestrictGuestAccess=0
This setting allows OpenClient to log error events.
4. [HLM \SYSTEM\CurrentControlSet\Services\Eventlog\Application]: InstallDir = C:\Program files\FileNET\IDM\Web\FnOpenClient JavaDir= C:\Program files\javaSoft\JRE\<Version Number>\ Version=04.00.0000.0130
These key values identify the install and java directory and the OpenClient version.
NTFS settings for OpenClient
The ..\Program Files\FileNET\IDM\FnOpenClient directory and its sub-direories and files should have these following NTFS settings:
|
Administrators = Full Control |
|
Power Users = Modify|Read|Write|Execute |
|
System = Full Control |
|
Terminal Server User = Modify|Read|Write|Execute |
|
Users = Read|Write|Execute |
The ..\Program Files\FileNET\IDM\Shared\DATA_SS directory is the only one that has a slightly different NTFS setting for Open Client:
|
aspnet_wp account = Full Control |
|
Administrators = Full Control |
|
Power Users = Modify|Read|Write|Execute |
|
System = Full Control |
|
Terminal Server User = Modify|Read|Write|Execute |
|
Users = Read|Write|Execute |
Note that this is similar to other OpenClient directories. The only difference is that it has full control for the aspnet_wp account, which is required to support the CS search functionality.
Aspnet_wp account
This account is automatically created by the .NET runtime framework. It belongs to the Users group and assumes all the security settings for that group. By default, all the .NET web applications run under this account. This also applies to Open Client. On the other hand, all the legacy asp web applications run under the IUSR_<machine name> account.
The Java environment, JRE or JVM, determines whether a user sees the "Save annotations?" prompt when closing the Java Viewer window.
In a JRE environment, the Java Viewer does not prompt to save annotations. Unsaved annotations are lost.
In a JVM environment, the Java Viewer prompts the user to save annotations.
The following error occurs when trying to connect to a CS Oracle Library from Open Client.
"The Oracle(tm) client and networking components were not found. These components are supplied by Oracle Corporation and are part of the Oracle Version 7.3 (or greater) client software installation.You will be unable to use this driver until these components have been installed."
The error appears because the ASPNET user did not have sufficient access to several files in the Oracle home directory (for example, C:\Oracle\Ora92). The problem is resolved by granting ASPNET Full Control access to the directory, and propagate the permissions to all the child objects.
To use Open Client with eProcess you must have a supported eProcess workflow server available. Open Client can be used with either eProcess 4.2.2 (Hot Fix Pack 5 or later) or eProcess 5.0.0 workflow servers. The FileNET software on the Open Client web server and the eProcess workflow server must be kept in sync. When an eProcess hot fix pack or new release is made available, complete the following steps to bring the Open Client web server up to the same software level.
Notes
·
Web Workflow 4.2.2 and Open Client cannot be collocated on the same
web server and cannot use the same eProcess 4.2.2 workflow server.
Clients can access both eProcess Web Workflo 4.2.2 web sites and Open Client
web sites. However, Open Client and Web Workflo workflows are separately managed,
which means Open Client users cannot participate in Web Workflo workflows
and Web Workflo users cannot participate in Open Client workflows.
Improper installation and configuration of the Open Client could possibly
damage your existing production system configuration. It is imperative you
take into account these restrictions prior to attempting to install Open Client.
· eProcess 4.2.2-Hot Fix Pack 5 has not been released yet. A preliminary version of the hot fix pack for Windows 2000 workflow servers is available on the Open Client FTP site. Once the official Hot Fix Pack 5 is released, please update your workflow servers with the released version of the hot fix pack. eProcess 5.0.0 is scheduled to release during September 2002. Note that Image Services 3.6 SP2 must be installed on the server running WorkFlo Services. In addition, SCR 159723 is required for updated error tuples and SCR 160103 is required for Oracle.
1. Update the workflow server following the instructions provided in the eProcess Hot Fix Pack Readme.
2. Stop any routers and eProcess services running on the Open Client Web Server.
3. Copy the files in the Hot Fix Pack Open Client directory to the matching locations on the Open Client web server.
4. Reboot the web server.
Web WorkFlo 5.0.0 and Open Client can be co-located on the same web server and can use the same eProcess 5.0 workflow server.
For details on how to install or upgrade an Open Client environment for use with eProcess 5.0.0, refer to the eProcess 5.0.0 readme on the eProcess 5.0.0 Web WorkFlo CD. One restriction on the Open Client and eProcess 5.0 environment is that custom Web WorkFlo launch and step processors cannot be processed using the Open Client Personal Work Manager. This restriction will be removed with the release of Open Client, Hot Fix Patch 1. (9/26/02)
1. Stop any routers and eProcess services running on the Open Client Web Server.
2. Install Web WorkFlo.
3. Ensure all routers and eProcess services are still stopped.
4. Copy the pw.jar file from the ...\IDM\Web\IDMWS\Redist\WF_Extras\pw.jar directory to the ...\IDM\Web\FNOpenClient\eprocess\DownLoad directory.
5. Verify that the routers previously configured are still available, if not reconfigure them.
6. Restart the eProcess services and any routers.
1. Stop any routers and eProcess services running on the Web Workflo web server.
2. Install Open Client using the Complete option.
3. Ensure all routers and eProcess services are still stopped.
4. Copy the pw.jar file from the ...\IDM\Web\IDMWS\Redist\WF_Extras\pw.jar directory to the ...\IDM\Web\FNOpenClient\eprocess\DownLoad directory.
5. Verify that the routers previously configured are still available, if not reconfigure them.
6. Restart the eProcess services and any routers.
If Open Client and Web WorkFlo are co-located, uninstalling one package will prevent the other package from functioning correctly. To work around this issue, use the following procedures when uninstalling:
1. Use Add/Remove Programs in the Control Panel to uninstall Web WorkFlo.
2. Use Add/Remove Programs in the Control Panel to repair the Open Client installation.
3. Verify that your routers are still configured, if they are not reconfigure them.
1. Make backup copies of the following files and directories:
..\IDM\vwidmcom.dll
..\IDM\vwntutil.dll
..\IDM\PWBIN
2. Stop all routers and eProcess services.
3. Uninstall Open Client.
4. Re-run the Web WorkFlo installer.
5. Reinstall the files from the backup copies you made in step 1.
6. Restart the eProcess services.
7. Reconfigure the routers.
In an Open Client with eProcess system, we recommend confirming the JRE version installed on a web client prior to accessing the eProcess applets from that client (go to Start\Settings\Control Panel\Java Plug-In to see the version). Open Client with eProcess requires either JRE 1.3.1 or 1.4.0; accessing the applets with any other JRE version is not supported, nor is having multiple JRE versions installed on a web client. Depending on the installed JRE version, take the appropriate actions:
· If no JRE exists and you are using Internet Explorer, no actions are required prior to accessing the eProcess applets. You will be prompted to download JRE 1.4.0 when you access an eProcess applet; be sure to uncheck both the Netscape 6 and Internet Explorer options on the Select Browsers screen during installation.
· If no JRE exists and you are using Netscape, you must install JRE 1.4.0 or 1.3.1 prior to accessing an eProcess applet. After Open Client installation, the JRE 1.4.0 setup package is available on the web server in the ..\FileNET\IDM\Web\FnOpenClient\eProcess\Download directory. FileNET does not supply JRE 1.3.1 with Open Client. See below for considerations when selecting a JRE version.
· If JRE 1.4.0 exists, verify that the Internet Explorer option on the Java Plug-In\Browser tab is not selected prior to accessing the eProcess applets. If you are using Netscape 6, make sure the Netscape option is selected.
· If JRE 1.3.1 exists, no actions are required prior to accessing the eProcess applets.
· If a JRE other than 1.3.1 or 1.4.0 exists, do not access the eProcess applets until you replace the existing JRE(s) with version 1.3.1 or 1.4.0. See below for issues to consider prior to uninstalling existing JREs.
Before uninstalling an existing (non-1.3.1 or 1.4.0) JRE or choosing between 1.3.1 and 1.4.0 consider the following:
· Any issues uncovered during Open Client testing with both JRE versions are covered in this document.
· JRE 1.4.0 introduces certain localization issues; if the web client is a non-English language machine, it might be preferable to run JRE 1.3.1.
· Other applications running on or accessed by the web client might require a specific version of the JRE. If a client has dependencies on JRE versions other than 1.3.1 or 1.4.0, you must decide which applications you will run on or access from that client.
(FR 41896:42525)
Viewing a public work queue that contains a large number of work items fails with a server timeout. For example, a returned page may say "Server Application Unavailable." This server timeout occurs when the public work queue holds 24,000 items. (FR 41021:42290)
When you are setting up a new workflow server, the first step is to initialize a region. To complete this step, click on the Configuration Console link on the Tools page. If you try to use the Log in to workflow server link prior to initializing the region, the login fails. (FR 40557:42112)
· On the library Browse or Search page, open a workflow definition by selecting the radio button, and then the Open toolbar item. Clicking on the Open link beside the workflow definition name does not initiate the Designer applet. (FR 38004:41172)
· If you attach a workflow definition to a workflow, the user launching the workflow or processing the step receives the error "XML page cannot be displayed" when opening the workflow definition attachment.(FR 41382:42389, FR 41016:42287).
· In Netscape 6.2.4, an exception is thrown if an integer or float value in an invalid format is entered into an HTML step processor. (FR 40644:42151, FR 40650:42153)
· Float data fields with multiple precision do not display correctly.
· In Netscape 6.x, you cannot open a UNC attachment. When you select the UNC attachment and try to open it using the Open toolbar button, nothing happens. (FR 41877:42517)
· By default, when a user returns to the Process page from an HTML step processor, the list of items in the queue is automatically updated. The updated list includes new items that have entered the queue and leaves off items no longer in the queue.
If you experience slow web server performance and users are accessing the web server with HTML step processors, you might improve performance by disabling automatic queue updates. When you disable this feature, the list of items in the queue is updated only if the user took a specific action in the HTML step processor. The actions that can trigger an automatic update vary based on the queue the step processor is working in:
|
Queue |
Actions
that can trigger automatic update |
|
Inbox |
Complete,
Reassign, or Return |
|
Tracker |
Delete |
|
any
work queue |
Complete,
Reassign, Move to Inbox |
Take the following steps to enable or disable automatic queue updates.
1. From a text or XML editor, open the SitePreferences.xml file, located in the Preferences subdirectory of your Open Client installation directory.
2. Locate the following XML section. In the position shown in bold below, enter Yes to enable automatic updates or No to disable automatic updates.
<setting name="UpdateQueueAfterProcessingStep" label="Update
queue after processing step" description="Triggers data retrieval
from server after performing an operation in the Step Processor">
<value default="No" type="string">No</value>
<options>
<option label="Yes">Yes</option>
<option label="No">No</option>
</options>
<uiType>DropDownList</uiType>
<visible>true</visible>
</setting>
You cannot open folders which have extended characters in their names. (FR 41628:42462)
If you are using JRE 1.4.0, you receive a warning message when you assign UNC attachments to Java step processors in Netscape. (FR 41977:42539)
If you log in directly to an eProcess Java applet using LDAP credentials, you may also be prompted to log in to IS and CS libraries. To avoid this problem, do one of the following before accessing an eProcess Java applet:
· Log in to the library.
· Log in to the eProcess Java applet using the Log in to workflow server option on the Tools page.
· On the Macintosh platform, the file download operation triggered by Copy Local or Checkout sometimes does not work correctly. (FR 37333:43921, FR 40798:42204)
· The Linker applet hangs on Macintosh in IE 5.1. (FR 42498:42645)
· Uninstalling CS 5.2 client DLLs prior to IDM Desktop 3.2 does not display a warning. (FR 36401:40610)
· During installation, a command console may appear over your install screen. The console is harmless and will eventually shut down.
· If you do not have an automatic reconnection to the IDM Desktop setup directory, upgrading to IDM Desktop 3.2 fails after the client DLLs are uninstalled and the machine is rebooted.
An IDM Desktop upgrade requires you to reboot the machine several times, so it is important to do the following:
o Log in as the same user each time.
o
If you are installing from the network, you must have an automatic reconnection
to that setup directory after rebooting.
· If you are trying to install IDM Desktop from a UNC path, the install will fail if there are spaces in the path name. To work around this, you can map a drive or remove the spaces from the path name. If you get the following error message "setup.exe cannot be found," do not click OK in the error dialog box. Clicking OK will hang your system and you will need to end the task in your Task Manager.
Refer to Microsoft Knowledge Base article Q191690 for more information. (FR 37141:40861)
After modifying the properties of a CS folder, the security access assigned to the folder reverts back to the following default settings: Admin:Owner and General Users:Viewer. (FR 36781:40741)
For an Integer String property type, the maximum value is 2147483647. This is a limitation of OLE. Entering a value greater than the maximum value results in an invalid data type error. (FR 35645:40440)
Using the IDM Desktop Maintenance program to remove connectivity to CS libraries does not work correctly and future access to CS libraries is not removed. (FR 36695:40712)
On Windows 2000 and Windows XP systems, users must have access to the registry to view documents such as .pdf, .doc and .xls.
On Windows 98SE, an Explorer view doesn't always refresh correctly unless Internet Explorer 4.01 or higher is installed.
Using Windows XP, the plus (+) and minus (-) signs in a FileNET Neighborhood tree view disappear when a library is highlighted. Refer to the Microsoft Knowledge Base Article Q315976 for more information.
The owner of a document cannot publish the document if another user has administrator rights to the same document.
· In Windows XP, if you select Search from the Start menu, the Find FileNET Documents menu option does not appear in the Search submenu. Refer to the Microsoft Knowledge Base article Q316307 for more information. (FR 35151:40332)
· Although the Title property in the Item object accepts a value as long as 254 characters, the CS API currently has a maximum length of 80 characters defined for searchable values (via the SPI_MAXLEN_QUERY_VALUE define). As a result, if you use the IDM Find application in IDM Desktop to search for documents based on the Title property, an error occurs if any of the retrieved documents have titles longer than 80 characters.
· 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.
· 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. IDM Find does not convert the 2-digit year to fit the regional setting when opening a legacy stored search.
· When logged on to a non-default library switching from Simple Find to Advanced Find can require you to log on to the default library. If you cancel the log on dialog for the default library, the Find Application crashes with a runtime error. This problem occurs when all of the following statements are true:
o The Find Application is initiated from the FileNet Neighborhood.
o You are not currently logged on to the default library.
o You select a folder using the Browse for folders button on the Simple Find screen prior to switching to Advanced Find or New Search.
· 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.
· If the image of a Microsoft Office document appears to be cut off from the right or does not print in landscape mode, right click on the document in the viewer, then click the Options/Print on the context menu, and check the 'Use Original document Formatting if available' checkbox.
· A Virtual Memory error occurs if you are searching in a large document, such as a Report Manager document. Increase your paging file size to resolve this error. (FR 36053:40531)
· 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:28779)
· The Viewer, when using the Outside In technology, does not support scrolling using the Microsoft mouse thumbwheel. You can use the thumbwheel to scroll FileNet imaging formats. (FR 15986:36539)
· 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 a document displayed by Outside In. Define a default printer to resolve this issue.
· The following issues occur on a limited set of Postscript printers:
o
Printing PowerPoint documents
in landscape mode might cause the printing status dialog to hang.
o
Clicking on the cancel button
in the print status dialog to cause the Viewer screen to turn blank.
· The Print Annotation/Use Transparency option under the Print dialog prints annotations accurately to match the display. However, this degrades image quality and increases the time and resources used to print.
· You cannot print .txt documents to a FileNET printer via Panagon Print 4.1.
· The scale factor is not always available programmatically when a database or spreadsheet has many columns.
· Use the Enhance mode with multipage G3 Fax TIFF images. Other modes do not work properly.
· With MDI: the customized settings persist after you close a document or the viewer. With MTI, the customized settings do not persist after the viewer window is closed down and reopen. (FR 22394:46407)
· If you try to view a file with 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 the registered application, if there is one.
· If you are viewing Report Manager PDF files, there are additional Acrobat requirements. Please refer to the Report Manager documentation for these requirements.
· 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.
· 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 is an Internet Explorer issue. To work around the problem, use Ctrl-P or the print button on the tool bar.
·
Integrating Outlook 2002 (Outlook XP) with IDM Desktop fails. First make sure
IDMOUTL.ECP is in c :\program files\microsoft office\office10\addins. (FR
43369; 10/9/02) To resolve this problem if it is not:
1. Copy the IDMOUTL.ECP from c:\program files\filenet\idm to c:\program files\microsoft office\office10\addins
2. In Outlook, from the Tools menu, click Options, and then select the Other tab.
3. From the Other tab, under General, click Advanced Options.
4. In the Advanced Options dialog box, click Add-in Manager.
5. In the Add-In Manager dialog box, click Install.
6. Select the IDMOUTL.ECP file, and then click Open.
7. Make sure the FileNET IDM Outlook Integration item checkbox is selected.
8.
Click OK three times to get back to Outlook, then open the File
menu to confirm Outlook integration is now installed.
·
The Save As functionality may appear broken in Microsoft Office applications
after Application Integration is uninstalled. This occurs predominantly in
Excel and Word. To correct the problem, follow these steps:
1. Open the application.
2. From the Tools menu, click Customize.
3. Leave the Customize dialog box open.
4. Right-click the File menu, and then click Reset.
5. Close the Customize dialog box, and then close the application.
When the application is opened again, the Save As functionality will work correctly. (FR 12365; 4/26/02)
· The application integration preference "Prompt to update properties on checkin" allows the user to decide whether to update properties on checkin. When you turn on this option, the item properties are updated but the version properties are not (because the version does not yet exist). You may either edit the document's version properties or update the version properties during the next checkout.
If you are using an IS-only installation, prior to selecting FileNET Add, use the native PowerPoint Save As functionality to name the document. Selecting FileNET Add on a new, unsaved document causes PowerPoint to crash. (FR 23637:37787)
·
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 should appear. If they don't, delete the extend.dat file and repeat these steps to recreate the Extend.dat file.
· Compound documents cannot be added or opened from a library using Outlook integration.
· The Lotus Notes snapshot is not created during an Add procedure when Lotus Notes is not active. (FR 36290:40576)
·
The Snapshot printer is not installed if Lotus Notes is installed in quiet
mode. Without the Snapshot printer, the default settings for adding an entire
record to a CS library may fail. Refer to the following steps for manually
adding a Snapshot printer:
1. Open your Printers folder, and then select Add Printer.
2. In the Add Printer Wizard, click Next.
3. From the Local or Network Printer dialog box, select Local printer, and then Next.
4. From the Select the Printer Port dialog box, select Create a new port. Leave Local port as the port type, and then click Next.
5. In the Port Name dialog box, enter port name in a form of full path\file name.
The port name should include a short form of the Panagon installation path, and then "\Temp\Notes\fnsnap.tif". For example if Panagon is installed in the "Program files\FileNET\IDM" folder on D: drive, the port name should be: d:\progra~1\filenet\idm\temp\notes\fnsnap.tif
6. In the Add Printer Wizard, click Have Disk.
·
In the Install
from Disk dialog box, click Browse.
·
From the Locate
File dialog box, select your Panagon installation path, such as d:\Program
files\FileNET\IDM subfolder, from the Look in list. The fnsnap.inf
file name should appear in the list.
·
Select this file,
and then click Open.
·
From the Install
from Disk dialog box, click OK.
·
In the Add Printer
Wizard, click Next.
·
From the Name your
Printer dialog box, click Next.
·
From the Printer
Sharing dialog box, select Do not share this printer, and then
click Next.
·
In the Print Test
Page dialog box, click No, and then click Next.
·
Click Finish.
(FR 37075:40849)
· The design of the FileNET Notes Panagon Administrator database must be updated in order to leverage new configuration options specific to adding and retrieving Notes records. To complete this task, refresh the design of the Administration databases in use using the FileNET Notes Panagon Administration database template, the NPIAdmin.nsf file, located in the \Maintenance folder on the IDM Desktop software CD.
This task should be executed by a Notes Administrator. Items to note during this process include:
1. Designer ACL access is required to all databases that are being updated.
2. Design elements with the attribute "Do not allow Design Replace/Refresh to modify. . ." will not be updated.
3.
Clear "Do not allow Design Replace/Refresh to modify. . . " on the
"Using this Database" and "About this Database" documents
so that they can be updated, unless you have specific reasons not to.
·
If you copy the FileNET Notes Panagon Administration database from the "Maintenance"
subdirectory of the installation media, before using it 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, which by default is 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.
·
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 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 (\).
·
To install Lotus Notes integration during a quiet install of IDM Desktop,
the configuration file must specify the Lotus Notes component and the location
of the Notes.ini file. A sample configuration appears below. The ComponentsToAdd
key must include 11 (this code identifies the Lotus Notes integration component)
and the [Notes] section must provide the Notes.ini file location. The NotesConfigFile
entry is optional; if specified, it appears in the [Notes] section as shown
in the sample.
1. For Lotus Notes 5, set NoteINIFile=<drive>:\<Notes 5 Notes.ini path and filename>. In Notes 5, the Notes.ini file must be in the Notes 5 program path.
2. If you are using a file with pre-set configuration information, specify its path, set NotesConfigFile=<path>.
Sample configuration file:
[General]
TargetDir=C:\Program Files\FileNET\IDM
ComponentsToAdd=0,1,4,5,6,7,8,9,10,11
[Notes]
NotesINIFile=C:\Lotus\Notes\notes.ini
NotesConfigFile= <-- This line is optional.
· 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 98SE 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.
· 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:34248)
Automatic logon
Automatic logon using idmLogonOptServerNoUI is supported only in the Windows
2000 MTS/COM+ environment. It is not supported in ASP, ASP.NET, or .NET Framework
development environment in general.
· 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.
· When using the Document object function GetNativeFile, retrieving the native file of an IS Publish and Display Document can leave an additional file in the IDM Cache directory. The file is removed from the IDM Cache directory when the PC is rebooted. (FR 23199:37653)
· Using Document.SaveNew in a multithreaded application sometimes fails because the LocalDB was not intended for use with multithreaded applications.
Errors and unexpected behaviors can occur if you add objects to collections using the ObjectSets returned from Panagon IDM automation interfaces (for example, Folder.SubFolders). Instead, create an empty ObjectSet in your VB application and add objects to this ObjectSet.
ADO logs an unknown error when the connection to the database is being made. This error cannot be trapped with an error handler and is simply added to the ADO object's error collection. The error can be seen using Visual Basic's Locals Window at run time.
Advanced searches for CS documents using comparison operators on multivalued custom properties return multiple instances of items.
The following list describes the behavior of some of the IDMQuery controls in Visual Basic's Object Browser:
· ColumnHeaderString
Double-clicking on the property name twice in a row causes an error. Double-clicking once doesn't cause an error unless you immediately single-click in the value field and then single or double-click on the property name again.
The expected behavior in this case is to be able to click on the Property name and value fields as many times as you want to without seeing an error dialog box.
· DocumentClasses
Exhibits the same behavior as ColumnHeaderString.
· KeyCondition
Exhibits the same behavior as ColumnHeaderString.
· SearchAllVersions
Double-clicking on the property name or selecting the property name from the drop-down list doesn't change the value. And, no error dialog box is displayed.
· SearchType
Double-clicking on the property name, or selecting the property name from the drop-down list doesn't change the value. In this case, the Visual Basic error dialog box does display.
· ShowAnnotations
Exhibits the same behavior as SearchAllVersions.
· ShowCheckOut
Exhibits the same behavior as SearchAllVersions.
· WhereClause
Exhibits the same behavior as ColumnHeaderString.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. (FR 22502:37420)
The following code worked in IDM Desktop 3.0 and does not work in IDM Desktop 3.2.
‘Create a
Stored Search object.
Set oStSrch
= oLibrary.CreateObject(idmObjTypeStoredSearch, "")
qname = "QCS_"
+ CStr(k) + "_" + CStr(maxRet) + "_" + CStr(j)
queryCond
= whereClause(k)
oStSrch.ADOCommand.ActiveConnection
= connection
oStSrch.ADOCommand.CommandText
= "SELECT " + colSpec + " FROM FNDOCUMENT WHERE " + queryCond
oStSrch.ADOCommand.Properties("Maximum
Rows") = maxRet
oStSrch.Label
= qname
oStSrch.SaveNew
idmStoredSearchSaveNewNoUI, CustomApp.Text
To workaround this problem, call SaveNew as shown in the following example:
‘Create a
Stored Search object.
Set oStSrch
= oLibrary.CreateObject(idmObjTypeStoredSearch, "")
oStSrch.SaveNew
idmStoredSearchSaveNewNoUI, CustomApp.Text
qname = "QCS_"
+ CStr(k) + "_" + CStr(maxRet) + "_" + CStr(j)
queryCond
= whereClause(k)
oStSrch.ADOCommand.ActiveConnection
= connection
oStSrch.ADOCommand.CommandText
= "SELECT " + colSpec + " FROM FNDOCUMENT WHERE " + queryCond
oStSrch.ADOCommand.Properties("Maximum
Rows") = maxRet
oStSrch.Label
= qname
oStSrch.Save
'Save whatever values has been set to the AdoCommand.
(FR 22755:37497)
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 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
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.
If the SupportsObjSet property of the Command Object is not set, the Fields property of the Record Set is not initialized with the Object Set. When the SupportsObjSet property of the Command Object is set to true, the Fields property of the Record Set should have the Object Set when the RecordSet is reopened again. But the Fields property does not have the Object Set. To work around this issue, get the Object Set from ADORecordSet.Properties("ObjSet").Value. (FR 23451:37732)
Documents in the IDMListView's Report View layout do not always display the desired properties.
If you add the documents to the IDMListView layout window while the IDMListView.View property is set to any of the options (such as, idmViewIcon, idmViewSmallIcon and idmViewList) other than idmViewReport, the requested properties of the newly added documents do not display even if you later change the IDMListView.View property to idmViewReport.
To have the properties of the existing documents displayed under the proper column headers, you must restore the PropertyDescriptions objects and so on. (FR18497:34472)
In a collocated environment (Open Client and Web WorkFlo 5.0.0 installed on the same web server), you might receive "Page Not Found" errors when trying to access help through Open Client. As a workaround, access the help through the idmws pages (ActiveX Client) instead. (FR 41876:42516)
Open Client Administrator's Help
See the topic "Create stored searches and search templates" in the Web Services Administrator's Help for information on how to make searches availalbe to web clients. By default, all web clients have access to the same set of searches. However, for Open Client, the local search path preference can set a different search path to make different searches available to Open Client users. If you change Open Client's local search path to a path other than the one used for Web Services, you will need to create the search folders manually. Due to a software problem in 3.2, you must create an extra IS folder (\IS\IS) to access searches for specific IS libraries.
The Download Web Client Components topic incorrectly states that the file name for the Panagon Microsoft Application Integration setup option is fncontrols.exe. The correct file name is PanagonAppInt.exe. (FR 43001:42687)
Please note the following corrections to the LDAP Settings book
(Web Server Setup > Preference Guide > Libraries > LDAP Settings):
· For all LDAP settings, changes take effect when saved. (FR 36894; 9/26/02)
Please not the following corrections to the Security Overview
topic:
· The Security Overview topic states that Web Services supports Windows NT Challenge/Response authentication (NT C/R) on NT servers. This is incorrect. Web Services no longer supports Windows NT as a web server.
· Integrated windows authentication is supported on Windows 2000 web servers.
The following information replaces the existing explanation of unified logon to IS and CS libraries:
To use unified logon, set the preference "Use operating system credentials for logon" and configure the web server to use Integrated Windows Authentication. When the user accesses the web server, the following occurs:
o The user's NT Domain credentials are validated by the web server. If the user is not recognized, the web server will prompt the user for valid NT credentials. Once the credentials are validated, the user is given access to the web site.
o When the user clicks on a library, his NT domain credentials are passed to the library to be validated. If the user is recognized, he is logged on to the library. If the user is not recognized, the library log on screen is displayed. The "Use operating system credentials for logon preference" is set on a per library basis.
The "Use operating system credentials for logon preference" is set on a per library basis. For instructions on how to set up unified logon, see the Set up Unified Logon topic.
(FR 26593, fixed in patch 4)
The documentation for the Active Requests per User preference incorrectly states that the preference applies to IDM Desktop. This preference applies only to the Web server and the Web client. This topic is in both the IDM Desktop Administrator’s help and Web Administrator’s help (Add Libraries and Preferences > Preference Guide > Libraries > CS Library Name > Active Requests per User). (FR 43820; 10/28/02)