Readme File for Lotus Workflow 6.5.1 Please activate word wrapping in your text editor in order to read this text more easily. For important information regarding recommendations for upgrade order and supported configurations for the Notes Domino 6.5.1 Extended products, please refer to Technote #1162481. For the most current information about IBM Lotus Workflow 6.5.1, please visit the IBM Lotus Workflow Homepage at: http://www.lotus.com/products/domworkflow.nsf or The Documentation Library at: http://www-10.lotus.com/ldd/doc or the IBM DeveloperWorks for Lotus Workflow at: http://www-136.ibm.com/developerworks/lotus/products/workflow/ This file contains the following sections: 1. General Information a. System Requirements b. What's New in Release 6.5.1 c. License Information d. International Information - Language Coverage 2. Limitations of the Lotus Workflow 6.5.1 Sample databases 3. Limitations of the Lotus Workflow 6.5.1 Architect 4.a. Limitations of the Lotus Workflow 6.5.1 Application database 4.b. Limitations of the Lotus Workflow 6.5.1 Application database using the Web UI 5. Limitations of the Lotus Workflow 6.5.1 Organization Directory database 6.a. Limitations of the Lotus Workflow 6.5.1 Viewer 6.b. Limitations of the Lotus Workflow 6.5.1 Web Viewer 7. Integrating Lotus Workflow 6.5.1 with IBM Lotus Domino Document Manager (Domino.Doc) 8. Upgrading from Previous Versions 9. Issues with the Help databases 10. Miscellaneous 11. Known Issues for Non-English Locales -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 1. General Information 1.a. System Requirements >>>>> System requirements for Lotus Workflow <<<<< -=-=-=-=-=-=-=-=-=-= IBM Lotus Workflow Viewer 6.5.1 and Lotus Workflow Architect 6.5.1 Platform - Windows NT 4.0/Windows 2000 Professional/Windows XP Professional - Lotus Notes Release 5.0.12 or later version of 5.x. Release 6.0.3 or later version of 6.0.x, Release 6.5 or later version of 6.5.x Other software - IBM Lotus Workflow Engine 6.5.1 in a client/server environment Hardware - Intel(r) Pentium(tm), 128MB RAM minimum, 256MB or more recommended -=-=-=-=-=-=-=-=-=-= IBM Lotus Workflow Engine 6.5.1: Server Platforms - Windows NT 4.0 Server, Windows 2000 Server and Advanced Server on Domino Release 5.0.12 or later version of 5.x. Release 6.0.3 or later version of 6.0.x, Release 6.5 or later version of 6.5.x - Windows 2003 Server and Enterprise Edition : Domino Release 6.0.3 or later version of 6.0.x, Release 6.5 or later version of 6.5.x - AIX 5.2 : Domino Release 6.0.3 or later version of 6.0.x, Release 6.5 or later version of 6.5.x - Red Hat Linux Advanced Server 2.1: Domino Release 6.0.3 or later version of 6.0.x, Release 6.5 or later version of 6.5.x - Linux UL1.0 : Domino Release 6.5.1 or later version of 6.5.x - Solaris 9 : Domino Release 6.0.3 or later version of 6.0.x, Release 6.5 or later version of 6.5.x - iSeries Version 5 Release 1, Version 5 Release 2 : Domino Release 6.0.3 or later version of 6.0.x, Release 6.5 or later version of 6.5.x - iSeries version 5 Release 3: Domino Release 6.5.1 or later version of 6.5.x - zOS Version 1 Release 2 : Domino Release 6.0.3 or later version of 6.0.x, Release 6.5 or later version of 6.5.x - Linux for zSeries/ UnitedLinux 1.0 for IBM S/390: Service Pack 2.: Domino Release 6.0.3 or later version of 6.0.x, Release 6.5 or later version of 6.5.x Hardware and Memory - Please refer to the system requirements for the Domino Server. -=-=-=-=-=-=-=-=-=-= Lotus Workflow Engine 6.5.1: Notes client Platform - Windows XP Professional / Windows 2000 Professional / Windows NT Workstation /Win98 SE2; IBM Lotus Notes Release 5.0.12 or later version of 5.x. Release 6.0.3 or later version of 6.0.x, Release 6.5 or later version of 6.5.x Hardware - Intel(r) Pentium(tm), 128MB RAM minimum, 256MB or more recommended -=-=-=-=-=-=-=-=-=-= Lotus Workflow Engine 6.5.1: Browser clients Software - Internet Explorer 6.x or later on Windows 2000 Professional/ Windows XP Professional - Netscape Communicator 4.7x on Windows - Mozilla 1.4.1 with Sun JRE 1.4.2 on Linux RH 9/ EL 3 -=-=-=-=-=-=-=-=-=-= Lotus Workflow Web Viewer 6.5.1: Server Platforms - Windows 2000 Server and Advanced Server/NT 4.0 Server on Domino Release 5.0.12 or later version of 5.x. Release 6.0.3 or later version of 6.0.x, Release 6.5 or later version of 6.5.x For Non-Windows platforms, please see TechNote # 7003217 for the latest installation instructions and visit the Lotus Workflow website for the latest installation information on supported platforms at http://www.lotus.com/home.nsf/welcome/domworkflow - Linux RedHat Advance Server 2.1 : Domino Release 6.0.3 or later version of 6.0.x, Release 6.5 or later version of 6.5.x - Linux UL1.0 : Domino Release 6.5.1 or later version of 6.5.x - AIX 5.2 : Domino Release 6.0.3 or later version of 6.0.x, Release 6.5 or later version of 6.5.x - Solaris 9 : Domino Release 6.0.3 or later version of 6.0.x, Release 6.5 or later version of 6.5.x The Web Viewer is currently not supported on the iSeries or zSeries platforms. Please check the Lotus Workflow website for the latest information on supported platforms at http://www.lotus.com/home.nsf/welcome/domworkflow 1.b. What's New in Lotus Workflow 6.5.1 Lotus Workflow 6.5.1 contains significant performance enhancements, improved directory support and security, tighter integration with IBM Lotus Domino Document Manager (formerly Domino.Doc), and refinements in time management. Performance * Performance enhancements include improvements in Java API and in the Workflow engine. * Java agents have been moved into a script library for faster execution. * "Coarse-grained" methods provide for retrieving and saving multiple document and object properties with a single call to the API. * "Quick" features in the application database perform job initiation, activity claims, and activity completion by immediately updating only selected fields (visible or user-interactive) and letting the scheduled background agent complete the operation. * An application database enhancement moves agents into script libraries, which run faster. * Organization Directory enhancements speed up internal searches when resolving groups and names. Directory support and security * LDAP support has been expanded to include group resolution. * LDAP security has been enhanced with support for SSL (secure sockets layer). Other enhancements * Time management: The process designer can now specify the start time for activity durations: when the activity becomes available or when the activity is claimed. * IBM Lotus Domino Document Manager (formerly Domino.Doc): Multi-platform support. 1.c. License Information Lotus Workflow You can view or print your License Agreement after installing Lotus Workflow. All language versions of the License Agreement are ASCII text files named with the format . These files can be found in the ...\Architct\License directory. Use any text editor to view or print these files. Gif Encoder.Java Copyright 1996, 1998 by Jef Poskanzer . Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 1.d. International Information -- Language Coverage Brazilian Portuguese, French, German, Italian, Japanese, Korean, Simplified Chinese, Spanish, Traditional Chinese 2. Limitations of the Lotus Workflow 6.5.1 Sample databases The sample databases contain two sample processes used to show the integration between Lotus Workflow and IBM Lotus Document Manager (formerly Domino.Doc). These processes are called "Expense Report" and "Web Publishing". In order to run these processes an IBM Lotus Document Manager installation has to be available. For information about these sample processes and their setup, refer to the Integration Guide supplied with IBM Lotus Document Manager. Issue: If you move files to another server after executing "Set up Lotus Workflow Samples," and you execute Setup again, the old server names remain in the "Run On" field for the agent. Workaround: Don't move sample files to a different server once they have been initiated on a server. [ZYLI4RQ4ME] Issue: In the Expense Report sample, only persons with the Testperson or Secretary role can initiate a job. Workaround: Open the sample process in the Architect. In the Basic Properties dialog box for process, click the Initiators tab and choose All. Save and activate the process. [DHOS4Z5JRW] 3. Limitations of the Lotus Workflow 6.5.1 Architect Issue: You can't create connections out of a cluster. Workaround: Expand the cluster first.[KBIU4PYGW8] Issue: In the Architect, the version number of a process is always one greater than the most recently activated process version number in the Application database. Workaround: None Issue: "Open With" dialog in Windows shows DWF. If you use the "Open With" dialog box in Windows, Lotus Workflow is listed as DWF because the executable file is named DWF.EXE. Workaround: None. The entry in the "Open With" dialog box will launch Lotus Workflow. [KBIU4X9LC2] Issue: When a job is initiated interactively, formulas or job properties cannot be evaluated (as potential activity owners, for example). Formulas are skipped because there is no data yet. Workaround: Don't use formulas or job properties in the first activity; for example, select All as allowed initiators; or specific roles, workgroups, persons, etc. [MZOR4TJP8A] Issue: Certain @Functions don't work in @JobProperty. Formatting functions such as @Newline and @Char(13) will generate an error when used in @JobProperty. Text and form formulas do work. For example, @day(@now) and @Char(56) work in @JobProperty without generating an error. Workaround: None. This is a Lotus Notes limitation [PG0K4Z5VM4] Issue: In the Architect, the Search button is still grey after searching LDAP directory Workaround: enter a search Formula (at least 1 character) to enable the button again, just changing the object type does not ungrey the search button. [YXGO58NDER] Issue: Process diagram does not display in HTML-formatted report. When creating a report from the Architect, the process diagram will not display if (a) the report is in HTML format and (b) the username has a period (full stop, or ".") in it. Workaround: Create usernames without this character. [LREE5S4MSU] Issue: Due to code changes in the Architect for Quick features, the process created and exported from the LWF6.5.1 will not be imported in the previous versions of Architect. Workaround: None. 4.a. Limitations of the Lotus Workflow 6.5.1 Application database Issue: If you try to access the Help system before the Setup document is created, the Help database won't be found. Workaround: Create the Setup document first. [MDIR4KKRVA] Issue: When Lotus Workflow databases are replicated to another server, and you click View Job Diagram, that action sometimes tries to access the Process Definition and Application databases on the source server, instead of the replica. Workaround: None [DRUH4H6RS5] Issue: When using a subprocess or an automated activity as the first activity in a process, the name of the server is stored as the job owner. In this case, using the Job Property "Job Owner" in the process might lead to a routing error, since the server name is not a person defined in the Organization Directory. Workaround: Define a person document within the Organization Directory with the name of the server. Issue: If you create a subprocess with more than one end node, you may encounter errors during processing. Workaround: Redesign your process and use an automated or a normal activity within the subprocess before it is routed back to the corresponding host process. [HALE4C7LUC] Issue: Formula or Job Property used as potential activity owner of first activity will not evaluate. Workaround: Do not select Formula or Job Property as the potential activity owner of the first activity. Select ALL as allowed Initiators, or person, workgroup, role, etc. [MZOR4TJP8A] Issue: If an application database is installed locally, the Application Setup document isn't available in the Administration view. Workaround: Set the option "Enforce a consistent ACL across all replicas of this database" in the ACL. [DRUH4WW37Q] Issue: DWFJobInitiate API can't be used to Initiate processes with an Automated Activity as first activity Workaround: Initiate process using Form-based or Mail-based Initiation or Create an dummy interactive activity that is "save & completedEby the agent that has called the function DWFJobInitiate [PGOK4ZENPU] Issue: Using values other than "", 1, 2, or 3 in the Field MailStatusOS during Form-based or Mail-based Initiation may cause unexpected results during initiation such as broken binders. Workaround: Use values "", 1, 2, or 3 in the Field MailStatusOS as specified in in the Process Designer's Guide [MSHY5A7HPH] Issue: Activity reassignments: "Return Reassignment" button may appear when it has not been activated or fail to appear when it has been activated. This happens typically when a reassigned activity owner makes a subsequent reassignment. Workaround: None. [DRUH5KDVRM] Issue: Job Overdue notification is sent too early. A Job Overdue notice may be sent before the job is overdue, at the same time that an Activity Overdue notice is sent. When the job becomes overdue, the Job Overdue notice is correctly sent. Workaround: None. [PGOK5BNTRD] Issue: Postpone Date validation fails. If the browser's date format is different from the server's date format, Postpone Date validation fails. Workaround: If possible, make the date formats match. [PRJI5RUA5G] Issue: When using Quick Claim feature, a second Mail Inquiry does not work. User is unable to Claim and Edit the mail document a second time. Workaround: Do not use the Quick Claim feature if repeat mail inquiries are likely. [PRJI5QCCGE] Issue: In the Quick Initiate feature, if a team member has activated Save and Reserve in the first activity, subsequent activity owners cannot edit the main document. If the activity owner clicks Save & Complete, the document remains "In Progress" and not "Ready to Route." Workaround: The team member who clicked Save & Reserve should release the document manually. Alternatively, don't use the Quick Initiate feature. [PRJI5QBEQF] Issue: When the Quick Features are activated, automatic joins after parallel activities do not delete extra documents. A main document that was unedited, and should be discarded, is kept as an extra binder document. Workaround: None [PRJI5TUJ9Q] Issue: When Quick Completion is activated, it overrides Immediate Routing. Quick Completion updates essential fields and then allows Scheduled Routing to take care of the rest. Workaround: None; this is not a bug. [PRJI5Q5HD9] Issue: "Potential Activity Owners become Readers" is not updated under Quick Claim until the backgrounder runs. Workaround: None; this is expected behavior for Quick Claim. [PRJI5Q2HDV] 4.b. Limitations of the Lotus Workflow 6.5.1 Application database with the Web UI Issue: Actions are unavailable in search results page. When you perform a search with some browsers, the actions listed for the activities don't work. Actions may disappear when you pass the mouse pointer over them. Workaround: Click on the actual document to open it. Then perform the actions using the action bar or menus. [LTOT4XPKGD] Issue: Multiple context menus open and overlap each other. In a list of activities (such as My Activities), if you left-click on several context menu icons (the small arrow pointing down and to the right), the older context menus don't go away. Workaround: Move the mouse pointer over a context menu (without clicking) and it will go away. [MZOR4XGQHH] Issue: The "Show Audit Trail" action is not available from the Web UI Workaround: The "Show Audit Trail" action is only available from the Notes Client UI. User should use the Notes Client UI to access this action. [MSHY57YN8K] Issue: There are mouse pointer and dialog display issue when using versions Netscape 4.7x such as context menu popup dialog not displaying or mouse pointer staying an hour glass until the mouse is moved again. Workaround: Modifying the column formulas in Web UI views, See TechNote #1094637 for more information. [DRUH5AKQFB] Issue: Error when a reassigned activity owner with Author access returns a reassignment and then saves and closes the activity. The user may be asked multiple times for a password and then be told that he or she is not allowed to perform this operation. Workaround: (1) None; the operation is completed correctly in spite of the error. (2) Assure that activity owners have Editor access. Issue: Internet Explorer search on a non-indexed database generates HTTP 500 internal error with no further information. Workaround: (1) Index the database to be searched. (2) Use a supported Netscape browser, which correctly reports the source of the error (the user still needs to index the database). [MSHY5EAKK2] Issue: Access to application database requires two authentications (username plus password) to access under Netscape Communicator. Workaround. Not a bug. Session Authentication in the Server document for the application database server should be set to Single Server. [MZOR4XPPAZ] Issue: If an activity is reassigned to more than 20 people, not all of the new potential activity owners display in the "Show Details" box for the reassigned activity. Workaround: None. [VSBR5TLGYW] 5. Limitations of the Lotus Workflow 6.5.1 Organization Directory database Issue: If you have created very large workgroups in the Organization Directory database, and you select this group as an activity owner in a process, when you activate this process and attempt to create a job, the error "String too large" may be generated. Workaround: Reduce the allowed owners of the first activity. You may want to consider using the "This job can be initiated by all" property in the Initiators tab of the Basic Process Properties Dialog box. This allows all users that have access to the Workflow application database to initiate a job using this process. [HWER4E7CKB] Issue: When creating large workgroups, the error "Paragraph or field cannot be larger than 64K bytes" may be generated when the workgroup is saved. Workaround: Create small subgroups made up of the individual names, and then create the larger group using the subgroups as members. [JHIX4GZQQM] Issue: In the Organization Directory database, if you copy a hierarchy of departments into another Organization Directory database, the hierarchy will not be preserved and the departments will be copied in at the same level. Workaround: Manually re-set the hierarchy settings of your departments. (This is by design since the hierarchy information may not be valid in the target database.)[QMAA4HE5FZ] Issue: In the Organization Directory database, different roles can be defined with names that are different only in upper-case and lower-case letters, e.g. Testperson and TestPerson. However, these names are not case-sensitive and are not differentiated by the Engine. Using role names that differ only by the case of their letters can cause unpredictable results. Workaround: Use unique role names. [QMAA4GJDW8] Issue: Organization Units names are limited to 255 characters. This is a Software limitation. Workaround: Use Organization Unit Names that are shorter than 255 characers [IRAH4XM92V] Issue: Alternate Names functionality may yield unpredicted results when using different code pages. The list of potential activity owners in More Information -> Show Details in an activity may list both the original name entry and the alternate name. Some code page characters may not display or display incorrectly. Workaround: None. [KMUY4Y6JRW] Issue: Members of groups in another database do not display. For example, groups in a Teamroom database will not be expanded and displayed in the Business Object Library. A database object must be mapped to in the default lwfmap.ini file, not its own .ini file. Workaround: Put the mapping information into the default lwfmap.ini file. [SYPK59WQ2J] 6.a. Limitations of the Lotus Workflow Viewer 6.5.1 Issue: When a workflow participant tries to install the Lotus Workflow Viewer to a drive that has only read access, the Notes client will report a "File not found" error. Workaround: The workflow participant should make sure that the target drive has read/write access. [GJEK4KLUYT] Issue: Text labels in processes defined in the Lotus Workflow Architect cannot be viewed in the Lotus Workflow Viewer. Workaround: None [GJEK4JTHD7] Issue: Different time settings in the operating system of the client and the server may result in an incorrect display and animation of the job in the Lotus Workflow Viewer. Workaround: None [MSHY52SMBA] 6.b. Limitations of the Lotus Workflow 6.5.1 Web Viewer Issue: There are special requirements to run the Web Viewer on a Domino Server running from a remote session (i.e: Telnet). Workaround: See TechNotes # 1092396 and 1094673 For more information. [YXGO52BCDK] Issue: The Web Viewer requires JDK 1.1.8 or greater on the Domino Server. Error "java.lang.IllegalArgumentException: sun.io.CharToByteutf-8: sun.io.CharToByteutf-8" will be displayed on the Server console. Workaround: Open your Servlets.properties file. At the end of your active line add ContentType=text/html (making sure to capitalize the C and the T). Shut down and restart the http server [ZYLI4YDBRB] Issue: The Web Viewer doesn't show correct activity status in loop-back situations. When the routing path loops back to an activity (as in an approval or revision), the Web Viewer shows only the first instance of the activity. Workaround: None [DHOS4YEQNK] Issue: Web Viewer does not support the following characters in a user's name: ~, !, @, #, $, %, ^, &, *, (, ) Workaround: Set "NoLogin = true" in the servlets.properties file. Warning: This causes a security issue by giving all users full access to the Web Viewer Issue: Web Viewer Sametime Integration (IBM Lotus Instant Messaging and Web Conferencing) does not support the following characters in a user's name: ~, !, @, #, $, %, ^, &, *, (, ) Workaround: None Issue: Configuring the Web Viewer to view job diagrams in multiple Application DBs Workaround: See TechNote # 1087865 entitled "Configuring the Web Viewer to view job diagrams in multiple Application DBs" for more information about Web Viewer setup. [CJKE543TVS] Issue: Under Netscape, tool tips in double-byte fonts display as garbage. Workaround: Use a supported Internet Explorer browser. [THIA5AV9W4] Issue: Viewing "show details" by left mouse click on the arrow does not work on Mozilla 1.4.1. Workaround: Mozilla browser does not support document.layers. Modifying the column formulas in Web UI views. See TechNote for more information. [VSBR5UXCAC] Issue: Viewing The tool tip for status of an activity and members are not shown in Mozilla 1.4.1 Workaround: Find all occurences of ALT= in the source code and add TITLE= with the same content as ALT=. This solution will work across all browsers including Netscape, IE, Mozilla. . See TechNote for more information. [VSBR5UXAYX ] Issue: Web Viewer Sametime Integration (IBM Lotus Instant Messaging and Web Conferencing) does not support Sametime version 3.0 or later. [MLAT5V9LP7] Workaround: None 7. Integrating Lotus Workflow 6.5.1 with IBM Lotus Domino Document Manager (formerly Domino.Doc) The sample databases contain two sample processes used to show the integration between Lotus Workflow and Domino.Doc. These processes are called "Expense Report" and "Web Publishing". In order to run these processes, a Domino.Doc 2.5a or greater installation has to be available. For information about these sample processes and their setup refer to the Integration Guide that is distributed with IBM Lotus Domono Document Manager. In general, the integration between IBM Lotus Domino Document Manager and Lotus Workflow is available on all platforms that support both products. There are, however, some limitations for non-Windows NT servers: - All basic integration features, such as interactive and event-based job initiation from IBM Lotus Domino Document Manager, or linking back and forth between IBM Lotus Domino Document Manager documents and Lotus Workflow documents, are fully supported for all server platforms that run IBM Lotus Domino Document Manager and Lotus Workflow. - The automated activity agents for Archive, Search and CheckIn/CheckOut that are delivered with Lotus Workflow as a part of the integration work are based on the OLE API of IBM Lotus Domino Document Manager. Because the automated activity agents run on the server that hosts the Lotus Workflow application, this API has to be available for the LotusScript environment of this server. Therefore, non-Windows NT machines cannot run the automated activities. For the full functionality to be available, it is recommended that the IBM Lotus Domino Document Manager library and the Workflow databases be installed on the same Notes server. Because of problems with Notes login type and backend agents--for example, the "DD Archive" Agent--Lotus Workflow supports only the HTTP protocol as login type for IBM Lotus Domino Document Manager. If a user already has an existing access profile for use with Domino Workflow 2.0, which used the Notes login type, it is necessary to delete the access profile and create a new one. Issue: When archiving to a specific IBM Lotus Domino Document Manager cabinet or binder, you are required to match the case exactly, or they will not be found. This differs from other fields in the Setup document for a Lotus Workflow application database. Workaround: Use exact case matches for referring to the cabinet or binder. [CMOS4J5SLT] Issue: When running IBM Lotus Domino Document Manager from the Web client, a document that is used to start a Workflow job is not viewable from the Document Profile. When you click View from the Document Profile, you get a "File not found" error. Workaround: Add the 2.x view aliases "OSA|OS WD A Name" to the (SK WebAllByJobName) View. This view will now have 3 different aliases "OSA | OS WD A Name | SKWebAllByJobName". Note that you must keep the aliases in this order so you don't break any Lotus Workflow functionality. [JJON4YNKP6] Issue: Profile fields do not get transferred to Workflow when you add DD references to the Main Document. If in the document type specify that the references of IBM Lotus Domino Document Manager (Domino.Doc) should be added as the main document and specify that all profile fields be transferred. The contents of the field is not transferred to the Workflow job. Workaround: Specify the references to IBM Lotus Domino Document Manager be added as a binder document and the information in the field is transferred properly. [JJON4XLSGW] Issue: Field values do not get transferred if IBM Lotus Domino Document Manager info is part of main document for interactive initiation. Workaround: Specify the references to IBM Lotus Domino Document Manager be added as a binder document and the information in the field is transferred properly. [JJON5AMJHZ] Issue: The Reference link in an IBM Lotus Domino Document Manager document does not display the Lotus Workflow navigator panel in the Web UI. Workaround: None 8. Upgrading from earlier versions Issue: Language document is missing after executing design refresh on an application database and the Organization Directory database. Workaround: After the design of the database has been refreshed, re-create the language document. See the Migration Guide for more information. Issue: In the Lotus Workflow Migration Guide, instructions in the topic "Migrating documents" for updating the Organization Directory Database have changed. Workaround: Use these instructions to replace Steps 3 through 6. 3) Choose View - Administration - Setup from the menu. 4) Choose Actions - Create Language Document. 5) Click OK in the message box that displays. 6) Close and reopen the database. Issue: Importing a Lotus Workflow process into an earlier version of Architect can cause the Architect to crash. Workaround: None. Processes may not be backward compatible. [DRUH4WDS9S] Issue: In upgrading applications with API customizations from the Developer's Toolkit, Type mismatch errors are generated when the application is run. Workaround: Use Domino Designer to upgrade the design elements using the enhanced APIs and events included in Lotus Workflow 6.5.1. Issue: Style sheets don't work in the Viewer. Workaround: The problem is caused by using the Viewer from a previous version. Install the Viewer from the latest version of Lotus Workflow. 9. Limitations of the Help databases Issue: @EXTERNALADDRESS function is not documented Workaround: The DWF @Function, @EXTERNALADDRESS, allows mail notification configured in automated activities to route mail to users not defined in the Organization Directory (the Engine removes the @function and doesn't attempt to resolve the address in the Organization Directory). However, this feature works only if another recipient, who is defined in the Organization Directory, is also specified. 10. Miscellaneous Issue: Pentium 4 based PCs sometimes crash during the Install of Lotus Workflow. Workaround: The crash is caused by an InstallShield issue with Pentium 4 based PCs. Please see Tech Note # 1102915 for more information about this issue and its workaround. 11. Known issues for non-English locales Issue: When viewing a process in the Web Viewer, the last character of a process name appears as squares. In the DBCS character set, if a process name has an odd number of characters (1, 3, 5, 7, etc.), the last character will display as squares when viewed in some browsers. This happens when the mouse pointer passes over the background of the process diagram. Workaround: None; this is a problem in the browser. You can avoid the problem by using an even number of characters in the process name or by changing browsers. [YXGO4WQESV] Issue: Web Viewer fails to load when Turkish is selected as the user's default locale. Workaround: None; this is a Lotus Domino issue. [TGRN4URMDE] Issue: If you choose to allow for backward compatibility in the Organization Directory database, by selecting "Yes" for compatibility with 2.1.1 in the Organization Directory database Setup document, then Names in the Organization Directory database are created and displayed as First Name Last Name and use the same naming convention as in the Notes Public Name and Address Book. Workaround: You can copy and paste names from a Personal Address Book with the correct naming convention for Asian names. However, if you also use names from the Public NAB, the names will be of mixed order. [KHIA4HF5F6] Issue: When adding documents to binder via Web UI, double byte form name becomes confused code sometimes. Workaround: None, Don't add documents with a double byte Form name to binder via Web UI. [YXGO4ZMCM6] Issue: On Traditional Chinese OS using Netscape browsers displays question marks in action bar java applet. Workaround: Find corresponding language font.properties java class file and modify it. For Traditional Chinese,it should be font.properties.zh_tw Delete the comment marks as seen below. # name aliases alias.timesroman=serif alias.helvetica=sansserif alias.courier=monospaced