Skip navigation FileNet logo
  Open Client Developer's Guide
  Search  |  Index  |  Glossary   |  
Close menu Overview
  About This Guide
  What's New in 4.0.1
  Open menu Introduction to the Toolkit
  Open menu Programming Considerations
Open menu Open Client Architecture
Open menu Developing for Process
Open menu Error and Exception Handling
Open menu Customizing the Framework
Globalization / Localization
Open menu General Information
   

What's New in Open Client 4.0.1

The Open Client 4.0.1 release incorporates the following features:

Implementation of Dispose pattern across Open Client

The implementation of Dispose pattern provides the ability to explicitly release external resources before the garbage collector frees the object. The Dispose() method has been used to place calls to “Marshal.ReleaseCOMObject()” method to clean up unmanaged resources, such as legacy objects (IDM COM objects), network connections, and files. For more information regarding how to use "Marshal.ReleaseCOMObject()” method, refer to Open Client Guidelines.

Robust Error Handling

The error page format is similar to rest of Open Client pages. Earlier, for any unforseen exception a .NET error page was being displayed. An application level exception handler has been introduced to handle all the unforeseen exceptions. The user is given maximum amount of information about the error/exception that has occurred. The existing custom error pages will be impacted by this change and you will not be able to see the custom error messages. For more information regarding how to enable custom error messages, refer to Customize the error page.

FileNet IDM COM Objects run under the STA model

ASP.NET Web Services don't allow us to set ASPCOMPAT to support STA IDM COM objects. The page directive ASPCOMPAT = "True" can only be set for ASPX page and causes the page to be executed on an STA thread-pool instead of the new MTA one. The use of ASPX pages has been recommended for Open Client application to handle IDM COM objects as the support for .NET Web Services (.asmx) has been withdrawn due to non-availability of STA threading model. For more information regarding creating ASPX pages, refer to Guidelines for Creating ASPX page.

.NET Framework 1.1 SP1 and .NET Framework 2.0 Collocation Support

You can use Open Client with .NET Framework 1.1 SP1 and some other application with .NET Framework 2.0 on the same server. This collocation configuration will not affect the working of Open Client. Open Client continues to work properly on the same machine if it is configured to use .NET Framework 1.1 SP1 using IIS management console.

Internet Explorer ActiveX Controls and Applets Update

On application of the latest Microsoft Internet Explorer update (KB 912945), ActiveX controls and applets in Microsoft Internet Explorer would get disabled by default. A user would no longer be able to directly interact with the ActiveX controls and applets loaded by the APPLET, EMBED, or OBJECT elements and will need to explicitly click on the controls to activate them. This update will affect the following platforms:

    Microsoft Internet Explorer 6 SP1 for Microsoft Windows XP Service Pack 2

    Microsoft Windows Server 2003 Service Pack 1

This problem can be overcome by using Open Client 4.0.1. All the ActiveX controls and applets used in Open Client will be activated by default and the user will not be required to click on them explicitly for activation. ActiveX controls and applets available in custom applications built on top of Open Client will not get affected by Open Client 4.0.1 and may appear as disabled on the first use. For more information regarding handling ActiveX controls and applets available in custom applications built on top of Open Client, refer to Guidelines for Implementing the IE ActiveX Control and Applet Update Workaround in Custom Applications.

Java Viewer Quick Start Feature

The Java Viewer Quick Start feature provides a mechanism for initializing a Web browser, Java, and Java Viewer session. The background task required to initialize a Java Viewer session is done prior to the time when Java Viewer is actually required. This reduces the startup time of Java Viewer. This feature is supported on various Operating Systems, such as Microsoft 2000 Professional and XP. The only Web browser supported for this feature is Internet Explorer; future versions of Java Viewer may support additional Web browsers.