Skip navigation FileNet logo
  Open Client Developer's Guide
  Search  |  Index  |  Glossary   |  
Close menu Overview
  About This Guide
  What's New in 3.3
  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 3.3

The following sections identify the major changes introduced in Open Client 3.3:

Process 2.0.1 for Open Client

Open Client 3.3 supports both eProcess 5.0.0 and Process 2.0.1. The Open Client Developer's Guide uses the terminology for the newer Process 2.0.1 release. Specifically, as of Process 2.0.1, eProcess is called Process, and Workflo Services is called Process Engine. The following sections outline the new features included in Process 2.0.1 for Open Client.

Process Java Applets Connectivity (PJAC)

As of Process release 5.1 (Process Engine 2.0.1), FileNet provides an installer called "Process Java Applets Connectivity (PJAC)." PJAC installs the components that provide connectivity to the Process Engine and replaces the previous "Web WorkFlo and Toolkit" components. For more information about PJAC, see the section Process Java Applets Connectivity (PJAC).

Process Analyzer

The Process Analyzer is an optional Process Engine functional expansion that provides analysis and reporting capabilities for business processes. The Process Analyzer enables users to analyze collected data to identify workflow business problems and increase workflow productivity, generate chart-based reports on statistical information gathered by the Process Engine, and create and save custom charts for future use. For more information about using the Process Analyzer, see the section Process Analyzer. For information on acquiring the expansion and adding it to your environment, contact your FileNet representative.

FileNet Rules Engine

Process Engine 2.0.1 and later includes built-in integration support from FileNet for the iLog Rules Engine (iLog JRules™ may be independently added to your environment; FileNet does not provide the iLog Rules Engine.) When combined with the iLog Rules Engine, the FileNet Rules Engine integration provides an add-on capability that enables business rules to be independently applied to workflows. For more information about using the Rules Engine, see the section Rules Engine. For information on acquiring the add-on capability for your environment, contact your FileNet representative.

Process Component Integrator

The Process Component Integrator is a service that runs on the Web server and provides application integration by enabling Java components and interfaces to be imported and accessible in Process workflows via Process Engine development tools. The Component Integrator can be used to assist in the creation of a custom Process work performer, which typically performs an operation or set of operations associated with a workflow step, but does not require a user interface. For more information about using the Component Integrator, see the section Using the Component Integrator to Build a Work Performer.

Note: Open Client 3.3 does not support the use of the JMS Adapter for JMS messages.

Open Client Coexistence with ActiveX Clients

eProcess 5.0.0 and Process 2.0.1 support ActiveX and Open Client coexistence on the same Web server and in the same isolated region. For more information about developing Process applications for ASP.NET-based Open Client, see the Developing for Process Open Client section of this guide.

Note: If you are using eProcess 4.2.2 or earlier, review the guidelines described in Developing in a Combined Open Client and ActiveX Environment before proceeding with your development.

Java Viewer Integration Recommendations

The Open Client Developer's Guide for the 3.3 release includes a new section, Customizing the Java Viewer, that provides information to assist developers with the process of integrating the Java Viewer into a custom application. Recommendations provided in this topic include detecting the operating system and Web browser, downloading and configuring the Viewer, interacting with IDM Web Services, determining whether a document is viewable, formatting annotations, and retrieving a document.

IDM COM Objects / JiGlue / .NET Programming Guidelines

The Open Client Developer's Guide for the 3.3 release includes a new section, Developing with IDM COM Objects and JiGlue in the .NET Environment, that identifies guidelines to follow when programming with JiGlue and IDM COM objects under the .NET framework. This topic describes how to ensure that you're using the Single Threaded Apartment (STA) threading model in order to successfully communicate with FileNet IDM COM Objects, and highlights performance improvement tips and known issues related to this development scenario.

Compatibility with .NET Framework and Visual Studio

FileNet Open Client 3.3 requires Microsoft .NET Framework 1.1 with the latest service pack. However, .NET Framework 1.0 can be run along side version 1.1, when required by another application. The .NET Framework is downloadable from the Microsoft web site. Please contact Microsoft for assistance with locating and downloading the .NET software.

FileNet Open Client 3.3 is compatible with any development environment that has been certified with Microsoft Visual Studio 2002 or 2003 (which includes Visual C++, Visual Basic, and Visual Interdev), and installed with the ActiveX (Web Services Client) option. Advanced customization of FileNet Open Client 3.3 requires Microsoft Visual Studio .NET.

Troubleshooting Open Client 3.3 compilation:

  • Verify the reference to the FileNet IDM Objects library. If the reference is broken (indicated by a broken reference icon), remove the reference. To reestablish the reference to your project:
    • Select Project > Add Reference
    • Select the COM tab
    • Select the FileNet IDM Objects Library
    • Click Add and then click OK
  • If you customize the installation including using Process integration, verify the reference to the JiGlue type library. If the reference is broken (indicated by a broken reference icon), remove the reference. To reestablish the reference to your project:
    • Select Project > Add Reference
    • Select the COM tab
    • Select the JiGlue Type Library
    • Click Add and then click OK

Developing with Visual Studio 2003 or later:

  • If the Open Client 3.3 project is opened in Visual Studio 2003 or later, the project file is automatically converted to the later version, and a warning similar to the following will be displayed: "The project will be converted to VS 2003 format and can't be converted back."
  • Before attempting to customize Open Client 3.3 using Visual Studio 2003, verify the Microsoft ADO library reference. (Microsoft recently changed the library name to use all upper case letters.) If the reference is broken (indicated by a broken reference icon), remove the reference. To reestablish the reference to your project:
    • Select Project > Add Reference
    • Select the .NET tab
    • Select the ADODB Library
    • Click Add and then click OK

For a complete list of software configurations and versions supported by FileNet IDM Desktop, Web Services, and Open Client, see the software Compatibility & Dependency document on the FileNet CSS Web site. For a list of additional requirements for developing with FileNet Web Services with Open Client and eProcess 5.0 or Process 5.1 integration, see the Capture and Process Compatibility & Dependency information also on the FileNet CSS Web site.

Open Client Customization Practices

The Open Client Developer's Guide for the 3.3 release includes a new section, Best Practices for Customization, that provides recommendations to follow when customizing the Open Client. This topic identifies points to consider when customizing the Open Client interface or source code, extending the supplied Data Providers and User Controls, or leveraging IDM COM objects when writing custom Web applications.

Open Client Interface Modifications

The visual appearance of Open Client 3.3, as well as the presentation format of this guide and other Open Client documentation resources, have been updated to coordinate with FileNet P8.