Release Notes
 for
 Panagon WorkFlo Services and Web WorkFlo 5.0.0
(November, 2004)

Introduction to 5.0.0 
This file contains information for the Panagon WorkFlo Services and Web WorkFlo 5.0.0 release for AIX, HP-UX, Solaris, Windows 2000 and the Process Analyzer.

Information for setting up Open Client 3.2.0 for use with WorkFlo Services 5.0.0 is located at the end of this document.

Where to find installation and other documentation
Installation and other documentation is available (in PDF format) on the FileNet web site at http://www.css.filenet.com/products.asp?id=1030463541&mainFolderID=1000157883  Once you log on to the site, proceed to Product Info > Panagon > eProcess > Product Documentation > eProcess 5.0.0, then see appropriate document(s): 
Panagon Web WorkFlo Installation Handbook
Panagon WorkFlo Services for Windows Installation Handbook
Panagon WorkFlo Services for UNIX Installation Handbook
Process Analyzer Installation Guide
Panagon eProcess Developer’s Guide

You can view and print the installation documents in Adobe Acrobat Reader. If you do not have Acrobat Reader, you can download the reader from Adobe’s web site (http://www.adobe.com/products/acrobat/readstep2.html).
After installation, you can access the Panagon WorkFlo Services and Web WorkFlo (collectively referred to as eProcess) documentation as follows:
•	On the web server, click the eProcess button on the left pane of the Panagon Web Services home page, then click the Help button.  The displayed "Welcome to eProcess Help" page provides links to and/or descriptions of all eProcess documentation. In addition, you can search for help on common activities.
•	On the workflow server, a sub-set of the eProcess documentation is available.  Note that in the “Location” column of the table below, <drive> is the drive where you installed the Panagon WorkFlo Services executables.

Documentation	Location	
Help for eProcess Administrators	<drive >:\Fnsw\Lib\WF_Help\admin_hb.htm	
Online help for eProcess Task Manager	<drive >:\Fnsw\Lib\WF_Help\taskmanager.htm	
Online help for vwlog	<drive >:\Fnsw\Lib\WF_Help\vwlog.htm	
Online help for vwtool	<drive >:\Fnsw\Lib\WF_Help\vwtool.htm	
Help for eProcess Services Administrator		<drive >:\Fnsw\lib\WF_Help\esm\esm.htm	

•	Documentation for developers is available if you install the Developer Files included with the eProcess Toolkit on the Panagon Web WorkFlo and Toolkit CD:
Documentation	Location\Home Page	
Panagon eProcess Developer’s Guide	..\Developer Files\Documentation\Developer Guide\ index.htm	
eProcess API JavaDoc documentation	..\Developer Files\Documentation\JavaDoc\JavaAPI\ index.html	
UI Toolkit JavaDoc documentation	..\Developer Files\Documentation\JavaDoc\ UI_Toolkit_API\index.html	

•	On the Process Analyzer Engine, from the Start\Programs\FileNet Process Analyzer menu, select either “Process Analyzer Configuration Help” or “Process Analyzer User Guide.”  

•	On a Process Analyzer client, from the Start\Programs\FileNet Process Analyzer menu, select “Process Analyzer User Guide.”

Note: When available, updated versions of the eProcess 5.0.0 documentation will be placed in the “Services and Support” section of the FileNet website (http://www.filenet.com).

Installing a Panagon Web WorkFlo 5.0.0 Development Environment
For information about installing a development environment, see “Appendix B—Installing the Toolkit” in the Panagon Web WorkFlo Installation Handbook.

Supported Software Levels for Panagon WorkFlo Services and Web WorkFlo 5.0.0 
See the eProcess Compatibility/Dependency Matrix located at: http://www.css.filenet.com/products.asp?id=1043085319&fldName=Compatibility+%26+Dependency&mainFolderID=1041356765&pathname=/Product%20Info/1)%20Products/Image%20Manager%20(IM)/eProcess%20Services/Compatibility+%26+Dependency

Prerequisite for Upgrades from eProcess 4.1.0 
If you used the F_Operation system field as a source of the step name in a 4.1 application, you must modify the application for use with 5.0.0, because F_Operation no longer includes the step name. In 5.0.0, F_Operation contains the name of the operation that is either in process or (if no operation is currently in process) is next to be executed for the work item. In 5.0.0, use the F_StepName field instead. Similarly, if you used F_OperationID in 4.1, use F_StepProcID in 5.0.0.

Important Notes and General Restrictions
•	Sun linker patch 109147-30 has been qualified for use with eProcess 5.0.0.

•	Sun linker patches 109147-25, 109147-27 and 109147-28 cause run-time server problems, including VWJs crashes.  Use linker patch 109147-30 instead.

•	Sun OS cluster patch 29 installs linker patch 109147-28.  Replace it with linker patch 109147-30.

•	Server-side work performers are not currently supported in this release.

•	In order for the installer wizard to function properly on the AIX platform, Java 1.3.0 must be running on the server.  If upgrading from eProcess 4.2.2. with the latest hot fix pack to eProcess 5.0.0, it is possible that Java 1.3.1 or above may be installed.  In this case, the wizard may not start when it is deployed.

•	Changing the name of a CS or IS library has ramifications for attachments that reference the library in both workflow definitions and running workflows.

If an attachment target (for example, a document in a CS library) is specified in a workflow definition, that workflow definition thus references the name (GUID) of the library in which the target resides. So if you change the name of the library, you must update the reference to the library in the workflow definition as well.

If an attachment target is specified during the launch step or a later step rather than in the workflow definition, the library name (GUID) reference is in all running workflows in which the step was completed. In this case, if you change the name of the library you can either delete and then re-launch all running workflows containing the old library name, or you can write an application to update the library name in the running workflows.

•	On an AIX or HP-UX workflow server, a stack trace on a hung VW process (such as VWRs) might point to “zombie_eating_sig_child handler (int) (dummy = 20), line 1531.” To free up the hung process, or to prevent such hangs from occurring, set the BEQUEATH_DETACHED variable in the Oracle sqlnet.ora file to YES.

•	The way step processors are identified internally differs in releases 4.2.2 and 5.0.0. As a result, you must manually update a workflow definition (.pep file) you created in 4.2.2 to use it in a 5.0.0 system. Depending on the circumstances, take the appropriate steps in eProcess Designer 5.0.0. 

•	If you transferred a 4.2.2-based workflow definition into an existing 5.0.0 system:

1. Open the 4.2.2-based workflow definition.
2. Click Validate Workflow on the toolbar.
    The validation process will return errors for all steps in which the step processor references a
    number (4.2.2 convention) rather than a name (5.0.0 convention). 
3. In the Step Properties for each step identified by validation, select the correct step processor   
    name from the dropdown list.
4. Save your changes and proceed as usual to launch a workflow from this definition. 

•	If the 4.2.2-based workflow definition exists in a system you upgraded to 5.0.0:

If you modify the workflow definition, complete the above procedure--otherwise, validation errors will result and you will be unable to launch the workflow. No action is necessary if you do not modify the workflow definition. 

•	Important information about API, Java UI Toolkit and developer/API-related changes is located in the Panagon eProcess Developer’s Guide.  See the section titled “What’s New in 5.0”.

•	There is a known problem with installing AIX 5L on older IBM hardware.  See IS 3.6 release note number 328 for more information

•	Windows 2000 Terminal Services cannot be used for remote administration of a Panagon WorkFlo Services system.  Use NetMeeting as an alternative for remote administration.

Known Software Problems and Restrictions
API
The VWSession.logonWithToken() method of the Java API has been modified in order to more fully and accurately explain its uses and limitations. Previously, we had erroneously stated that the method was unsupported.  It has been supported, however, with the caveats noted below:
logonWithToken
public void logonWithToken(java.lang.String theToken,
                           java.lang.String router_URL)
                    throws VWException
This method can establish a shared logon session. The VWSession constructors and logon(...) methods are preferable to this method, because all tokens time out and some tokens may not be valid. 
Parameters: 
theToken - The Process token. 
routerURL - The URL of the web server router, including the RMI protocol. 
Throws: 
VWException - Causes include invalid arguments, like timed-out and invalid tokens. 
See Also: 
getToken() 

Applications
•	When opening a step processor from email notification, the session for active applications may be lost, thus compromising any unsaved work.  Avoid this problem by saving your work before switching between eProcess applications. 

•	Due to a restriction in JRE 1.4.0, the Euro character and extended characters cannot be entered into eProcess applications using Alt + code.  The Euro character and extended characters normally entered using the Alt + code can be copied from the Character map (provided by Windows) and pasted into the eProcess applications.  For extended characters, set the input locale to the desired language, for example, German. On an English keyboard, press "Shift + {" or "[" etc. to get the desired extended characters.

•	The eProcess applications will hang when a Workflow Group with a large number of users is selected.  This problem can be avoided by adding -Xms256m -Xmx256m to the run-time parameters of the Java Plug-In used by the web client.

Configuration Console
When using the “CopyTo” function in Configuration Console, make sure the target region is initialized.

Designer
Designer does not launch the latest version of the workflow definition checked out from the CS library if the Designer preference “Add/Checkin Workflow Before Transfer/Launch” is unchecked.

Documentation
•	In the help topic titled "Null functions," the syntax example for the null() function does not clearly indicate that time is the only data type supported for this function. The example should instead read as follows:

Use the following syntax:
null(time)
where time is the data type. Time is the only supported data type for this function.

In addition, the description of the null() function should indicate that it returns a null time value.

•	The online Help for the vwtool environment command lists the "d" option for outputting data to a CDL file. However, the "d" option is no longer supported; the same functionality is available via the dump command, "f" option.

•	The online Help for the vwtool dump command does not indicate that an additional parameter is required when using the "f" option to output a CDL file. The additional parameter specifies the file content; valid entries are:
•	s = system-wide attributes
•	i  = attributes of the current isolated region

•	There are errors in the location of the eMail Notification files and the description of variables values as described in the Panagon eProcess 5.0 Developer's Guide topics: "Modify eMail Notification Files", "Localized Notification Files", and "Optional eMail Variables. These should be corrected as follows:

Under the "Modifying eMail Notification Files Procedure" heading in the "Modify eMail Notification Files" topic:

•	The sentence "The variables values are supplied by WorkFlo Services at runtime." should read: "The variables values are supplied by WorkFlo Services at runtime, where a given field variable obtains its values from the field that is named by the string following the "$" prefix in the field variable name."

•	The first step in the procedure, which specifies the location of these files on the WorkFlo Services server, should read: On the WorkFlo Services server, navigate to the \fnsw_loc\sd\msg\2 directory (for ActiveX). (On UNIX servers, navigate to the /fnsw/loc/sd/msg/2 directory.) Note that for Open Client, go to the \fnsw_loc\sd\msg\3 directory; for custom, use the \fnsw_loc\sd\msg\100 directory; these match the WEBAPP constants defined in the VWSession API.

Similarly, in the "Localized Notification Files" topic, the first paragraph should be amended to read:

•	On the WorkFlo Services server, navigate to the \fnsw_loc\sd\msg\2 directory (for ActiveX). (On UNIX servers, navigate to the /fnsw/loc/sd/msg/2 directory.) Note that for Open Client, go to the \fnsw_loc\sd\msg\3 directory; for custom, use the \fnsw_loc\sd\msg\100 directory; these match the WEBAPP constants defined in the VWSession API.

In the "Optional eMail Variables" topic, the first paragraph should be replaced by the following:

•	If an optional field is not exposed in the Event Log, that optional variable will be ignored. By default, all of the system fields necessary to supply required variable information are exposed in the Event Log.

Note: While it is technically possible to expose any system field in the event log, it is also possible for a predefined F_xxx system field to be recorded in the event log record incorrectly or meaninglessly. For example, the F_Response field may contain a stale response string. 

•	A user-defined field does not begin with "F_" and it must be exposed in the event log. 

•	A given field variable obtains its values from the field that is named by the string following the "$" prefix in the field variable name, as indicated in the following table.

•	In the online Help for Designer, the Workflow Properties – Advanced topic includes the following note: ”After the workflow definition is transferred to the workflow database, you cannot specify a different roster for the workflow. The originally specified roster is in effect for all versions of the workflow definition.”

It should read: “After the workflow definition is transferred to the workflow database, you cannot specify a different roster or different event log for the workflow. The originally specified roster and event log are in effect for all versions of the workflow definition.”  

•	In the online Help for Process Designer, the topic “Save document class properties to data fields on launch”  describes one syntax (Doc_<property_name>) for copying a value from a property of a launching document into a corresponding workflow data field. In this syntax, property_name is the display name of the document property. 

This topic should also include a second syntax (DocID_<property_id>) which uses the property id, rather than the display name of the property. Use administration tools on the library to obtain the property ID for a particular property name. This is the recommended syntax because, unlike the display name, the property ID will not change. In addition, the property_id format must be used if the display name contains spaces.

Email Notification
•	When the eProcess applications and email notification are open on the same web client, a blank display may be encountered.  This can be avoided by cleaning up the Internet temporary files (go to IE/Tools/Internet Options/General and click on "Delete Cookies" and "Delete Files").

•	When executing a step that includes an email notification, the workflow server communicates with the SMTP server only as long as is required to send the message. Once the email notification has been sent, the workflow server does not listen for status messages about that email notification. For example, if the SMTP server subsequently generates a message indicating that the recipient's inbox is full so the email notification cannot be sent, the workflow server does not receive this information. It is necessary to monitor the SMTP server directly to get status information for email notification messages.

HTML Step Processor
•	Due to Hotmail’s architecture, the HTML Step Processor does not display correctly when initiated from an email notification link in a Hotmail message.

•	The list of users/groups displayed in an HTML step processor reflects the content of the VWCachedSecurityList, which is cached on the web server. If you add a user or group in Image Services (IS), you will not be able to select that user or group in an HTML step processor until the VWCachedSecurityList has been refreshed. By default, a refresh occurs every 12 hours; you can modify this behavior by setting the rss_UserListRefreshRate variable in the resource.asp file on the web server (in the FileNet\IDM\Web\IDMWS\Redist\WF_Html_Toolkit\ui directory) as desired. Valid settings are:

integer < 0      VWCachedSecurityList is updated only when Internet Information Services (IIS) is restarted.

integer = 0      VWCachedSecurityList is updated every time the user displays the list of users/groups in an HTML step processor.

integer > 0      VWCachedSecurityList is updated every integer hours

Java Step Processor
A warning is displayed when assigning a UNC attachment in a Java Step Processor.

JavaDocs
Javadocs viewed with Internet Explorer 6.0 may have the rightmost letters of the text covered by the frame's right scroll bar.  Earlier versions of Internet Explorer and Netscape (including IE 5.5 and the latest Netscape 7.0) or other browsers do not appear to exhibit this behavior.

The problem seems to occur in any HTML file that contains the standard frameset declaration ("<!DOCTYPE ...FRAMESET…”>) that the JavaDoc compiler produces. Since the JavaDoc compiler includes this frameset declaration on every page that uses frames, all JavaDoc documents (not just FileNet documents) viewed with IE 6.0 are affected by this rendering.

JRE Download
We recommend confirming the JRE version installed on a web client prior to accessing any eProcess applets from that web client (go to Start\Settings\Control Panel\Java Plug-In to see the version). eProcess 5.0.0 requires either JRE 1.3.0 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, 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. When prompted, uncheck both the Netscape 6 and Internet Explorer options on the Select Browsers screen during installation. 

As an alternative to initiating the JRE 1.4.0 installation by accessing an eProcess applet, a web server administrator can make the JRE 1.4.0 installation available on a network and direct users to install it prior to accessing eProcess. After Web WorkFlo installation, the JRE 1.4.0 setup package is available on the web server in the ..\FileNet\IDM\Web\IDMWS\Redist\Download directory.

•	If JRE 1.4.0 exists, verify that the Netscape 6 and Internet Explorer options on the Browser tab are both unchecked prior to accessing the eProcess applets.

•	If JRE 1.3.0 exists, no actions are required prior to accessing the eProcess applets. 

•	If a JRE other than 1.3.0 or 1.4.0 exists, do not access the eProcess applets. You can force a download of JRE 1.4.0 by uninstalling the existing version prior to accessing the applets; however, before doing so consider the following:

•	Any issues uncovered during eProcess testing with both JRE versions are covered in this Known Issues document.

•	JRE 1.4.0 causes a Euro display problem.  This will be corrected in a future release of the JRE.

•	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.0 or 1.4.0, you must decide which applications you will run on or access from that client.

Launch
The online help indicates that a Content Services General User can launch a workflow from either a workflow definition file or from a document linked to a workflow definition file, as long as he or she has Viewer access to the workflow definition file or document. This statement is correct only if:

•	The workflow definition has already been transferred to the isolated region that the logged on user is accessing, or
•	If the workflow definition has not already been transferred, the logged on user has access to all work queues referenced in the workflow definition. Attempting to launch a workflow that has not yet been transferred triggers a transfer; however, that transfer will fail if the logged on user does not have access to all referenced work queues.
Also, a single workflow definition can be active in only one isolated region at a time, even if that workflow definition has been transferred to multiple isolated regions. The active isolated region is the one to which the workflow definition was most recently transferred. For example, assume the file called Workflow42 was transferred first to isolated region 1, then to isolated region 2. You will only be able to launch Workflow42 in region 2, even if you subsequently log on to isolated region 1. To be able to launch Workflow42 in isolated region 1, you must re-transfer it to region 1. After the re-transfer, you will be able to launch Workflow42 in isolated region 1, but not in isolated region 2. As a workaround for this behavior, save Workflow42 as multiple files--one file for each region you want to run it in. For example, create files called Workflow42_region1 and Workflow42_region2.

Linker
The Help for Linker includes the following statement:
"To create, edit, or delete a link between a workflow definition and a document, you must own both the workflow definition and document.”
This statement is incorrect; it should instead say:
"To create, edit, or delete a link between a workflow definition and a document, you must log on as a member of the Administrators group.”

Performance
•	As documented in the eProcess Developer’s Guide, you can achieve significant performance improvement for large scale queries by querying on exposed fields of database views (generated by the workflow server) via an ADO Connection object instead of doing a typical query on a queue, roster, or event log, via the Process APIs. However, on an Oracle database if you create a database view with an altered column type (for example using, RAWTOHEX(), TO_CHAR(), etc.) and you are using the F_WobNum field for a query on a view, in response to your SQL SELECT query Oracle will perform a full table scan with no index, resulting in a slow query response. Use the following workaround to resolve this problem and improve ADO query performance:

1. Using vwtool > createDBviews, create a script file that contains the SQL statements needed to create the database views. For details, see the eProcess Developer’s Guide and Help for vwtool.
 
2. Edit the script to remove the column type conversion by replacing RAWTOHEX(F_WobNum)with F_WobNum in the SQL SELECT statement for the database view. For example:

 select F_WobNum, F_WorkSpaceId, "userfieldname1", "userfieldname2" from f_sw.VWVQ94_testmodswp where F_WobNum = HEXTORAW('<specific WOB ID>');

3. Close and save the script.
 
4. Run the modified script on the database to create the database views. Note that database views are created automatically during a transfer and will overwrite those created when you run the script. Database views generated as part of transfer include the RAWTOHEX conversion function in the SQL SELECT statement. 

•	When a site has a large number (e.g., 12000) of eProcess users, performance can be improved by caching the security database in memory.  This is accomplished as follows:

1.	Run the fn_edit configuration editor.  Under the Performance Tuning tab, increase the value in the Security Buffer Pool Size (KB) field such that the security data buffer size is equal to or larger than the sum of the sizes of all active security databases on the eProcess server. 

2.	Exit the configuration editor, saving this change, and run fn_build -a.  

If fn_build -a returns an error message that the requested security data buffer size is too large, it will be necessary to increase the combined size of the redo logs.  This is accomplished as follows: 

1.	Run the fn_edit configuration editor.  Under the Procedures tab, run the Add an Additional Dataset procedure, and add a new dataset of type Security Redo Log.  This redo log should be large enough that the combined size of all the redo logs is equal to or larger than the combined size of all the security databases.  

2.	When this condition is satisfied, you should be able to increase the value of security data buffer size as specified above.  As always, fn_build -a is required to activate these changes.  

PPM
On a workflow server where the PPM is running as a Windows service, logging off Windows shuts down the VWJs process, thus preventing web clients from accessing the workflow server. To maintain the security of the workflow server while also enabling web client access, lock the workflow server rather than logging off. (Press CTRL-ALT-DEL, then click Lock Computer in the Windows Security dialog box.)

Process Analyzer
•	If the Process Analyzer collects incompatible events, those events will be stored in the deferred event table on the Process Analyzer Engine. The number of deferred events is shown in the Publisher Service (see the Publisher dialog). In some cases, incompatible events occur because the corresponding data from the workflow server has not yet been transmitted to the Process Analyzer (once the corresponding data is received, the incompatible events are moved out of the deferred event table). Incompatible events can also result if you install the Process Analyzer on the same calendar day you upgraded the eProcess system to release 5.0.0. 

•	You can remove deferred events by launching SQL Query Analyzer on the Process Analyzer Engine and running the following commands: use vmaedw; delete from x_deferredEvents. Prior to taking these steps, however, we recommend enabling the workflow server to send all events to the Process Analyzer. Once the AEEngine.exe on the Process Analyzer Engine is no longer consuming any CPU, which indicates it is not receiving incoming events, it is safe to purge the deferred events table.

•	Deleting user-defined fields, described in the Help for Process Analyzer Administration and Configuration, is not available in this release.

•	Pruning isolated region data from the Process Analyzer database, described in the Help for Process Analyzer Administration and Configuration, is not available in this release.

Unified Logon
In IDMWS, clicking the eProcess Logoff button ends the sharing of authentication information between IDMWS and eProcess within the browser session. As a result, after you log off eProcess in the browser session, you will be prompted to log on the next time you access eProcess in the session, even if you are already logged on to a CS library. 

Using Open Client with Web WorkFlo and WorkFlo Services 5.0.0
•	Open Client and Web WorkFlo can be installed on the same web server or they can be installed on separate web servers. In all cases, Web Services 3.2.0a must be installed on the web server prior to performing either an Open Client or a Web WorkFlo installation.

•	Open Client has specific web server installation requirements (e.g. .NET).  Please see the Open Client documentation for more information.

Installing Open Client without Web WorkFlo
•	Use the following procedure to install Open Client:

1. From the IDM Web Services 3.2.0a with Open Client CD initiate the Open Client installation by
   double-clicking on the setup.exe program in the OpenClient directory.
2. During the Open Client installation, select the Complete installation option.
3. Provide the CD key when prompted. The key can be obtained from FileNet Customer Support   
    Services (CSS) personnel.

•	Once the installation completes Open Client is compatible with WorkFlo Services 4.2.2. To upgrade the environment for use with WorkFlo Services 5.0.0, complete the following steps:

1. Stop any eProcess-related services, including any routers.
2. Change the properties of the FileNet VW Service from Automatic to Manual.  
3. Reboot the web server.
4. Stop the IIS Administration service.
5. Locate the Open Client Connectivity directory on the Web WorkFlo 5.0.0 CD.
6. Copy the contents of the Open Client Connectivity directory over the files installed by the Open  
    Client installer.
7. Change the setup type of FileNet VW Service back to Automatic.
8. Reboot the web server.

Co-location of Open Client and Web WorkFlo
•	Web WorkFlo 5.0.0 and Open Client can be co-located on the same web server. 

To update an Open Client web server with the latest Web WorkFlo release

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.

To update a Web WorkFlo 5.0.0 or later web server with the latest Open Client release

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.

Uninstalling Open Client or Web WorkFlo
•	If Open Client and Web WorkFlo are co-located, uninstalling one package will prevent the other package from functioning correctly. To workaround this issue, use the following procedures when uninstalling:

Removing Web WorkFlo
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.

Removing Open Client
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. Re-install the files you backed up in step 1.
6. Restart the eProcess services.
7. Reconfigure the routers.

Known Issues for Open Client
•	When checking in a workflow definition using the Open Client interface, the drop down list might not be presented to users in the expected order.  While it might appear that users are missing, in fact, all users are present in the list.

•	A warning is displayed when assigning a UNC attachment in a Java Step Processor.

•	Open Client and Web WorkFlo can be co-located on the same web server. However, while workflows initiated from Open Client can be processed from a Web WorkFlo inbox, the reverse is not currently supported.