===================================================================================
IBM WebSphere Business Modeler Basic Version 6.0.2.1
Interim Fix 3 Readme

===================================================================================

© Copyright International Business Machines Corporation 2007. All rights reserved. 

This is an interim fix for IBM® WebSphere Business Modeler® Basic Version 6.0.2.1.


Installing the interim fix
Fixes included in this interim fix
Product notes

Installing the interim fix


Use the software update function to install WebSphere Business Modeler interim fixes.

To install the interim fix, complete the following steps:

  1. Download the 6.0.2.1-WB-ModelerBas-IF0000003.zip file.
  2. Double-click the downloaded 6.0.2.1-WB-ModelerBas-IF0000003.zip file, and extract the files into a temporary directory. The rest of these instructions assume that you extracted the files to C:\temp\.
  3. In WebSphere Business Modeler, click Help > Software Updates > Find and Install. A wizard opens.
  4. Select Search for new features to install, and click Next.
  5. On the "Update sites to visit" page, click New Local Site. The Browse for Folder window opens.
  6. In the Browse for Folder window, navigate to C:\temp\6.0.2.1-WB-ModelerBas-IF0000003, and click OK. You return to the wizard, and the site that you specified is included in the Sites to include in search list.
  7. Select the site that you just added.
  8. On the Search Results page, click Select All to select both the product and the documentation features.
  9. On the Feature License page, read the license agreement for the feature that you are installing. To accept the agreement, click I accept the terms in the license agreement.
  10. On the Install Location page, click Finish. During the installation, you must confirm that you want to install an unsigned feature.
  11. When you are asked if you want to restart the workbench, click Yes.

The interim fix is now installed.

Fixes included in this interim fix

This is a cumulative interim fix for WebSphere Business Modeler Basic Version 6.0.2.1.

Fixes included in Interim Fix 3

This interim fix includes the following fixes. The PMR number and APAR identifier associated with each fix are included.

PMR Number Related APAR Identifier Description
01582,033,000 JR26325 Corrects problem with truncation in the Process procedure reports column heading
00002,I00,760 JR26353 Corrects a problem where an error message is incorrectly displayed after renaming an element with a single parenthesis when working in swimlane layout
JR26377 Allows manual ordering of elements in the project tree and allows user to save ordering
62755,442,000 JR26392 Adds user friendly messages for exceptions that are surfacing to the end user during and after import action failure.
54509,L6Q,000 JR26478 Fixes problem with the Process procedure report when double quotes are used
64595,442,000 JR26582 Removes the copy action from the context menu in the project tree for predefined queuries

This interim fix includes the following fixes, all of which are associated with APAR JR26643.

Fixes included in Interim Fix 2

This interim fix includes the following fixes. The PMR number and APAR identifier associated with each fix are included.

PMR Number Related APAR Identifier Description
49208,442,000 JR26347 Adds ability to auto-layout and maintain swimlane order.

This interim fix includes the following fixes, all of which are associated with APAR JR26381.

Fixes included in Interim Fix 1

This interim fix includes the following fixes. The PMR number and APAR identifier associated with each fix are included.

PMR Number Related APAR Identifier Description
65749,999,706 JR25993 Corrects failure to authenticate with a Publishing server when using long user ID and password combinations.
71850,033,000 JR26054 Enables scaling of SVG diagrams exported from Modeler's Process editor and embedded into a custom report.

This interim fix includes the following fixes, all of which are associated with APAR JR26169.

Product notes

Delay when testing connection to Crystal Reports server

When testing the connection to a Crystal Reports server from the Preferences page, it might take several minutes for the connection test to complete.

Delay when selecting fields for Crystal Reports report template

When creating a new Crystal Reports report template using Detailed Process Data Source as the data source, you might experience a significant delay when selecting fields to display in the report template. On the Select Fields page of the Report template wizard, if you select all available fields using the >> button, it will take several minutes for the Fields to Display list to populate.

To avoid this delay, consider individually selecting fields that you want to display using the > button instead of selecting all the available fields at once using the >> button.

Close Report Designer before deleting Crystal Reports report template

If you delete a Crystal Reports report template from the project tree while the report template is open in the Report Designer, the deletion will not complete. Even though the report template will not appear in the project tree, the associated files will not be deleted and you will not be able to create a new report template with the same name as the deleted report template.

To avoid this situation, close the Report Designer before deleting a Crystal Reports report template.

Auto-layout can maintain swimlane order

Modeler now allows you to maintain swimlane order during auto-layout. The behavior is enabled through the ordering dialog, available through the context menu of an open process diagram. Previously, the OK button would only be enabled if you changed the order; now it is enabled when the state of the auto-layout button changes.

Manual ordering of elements in the project tree view

You can now manually sort items within the Project Tree view, for example, to reflect frequency of use or relative importance of items within a catalog.

By default, items in the Project Tree view are sorted alphabetically within a container or catalog. When this default mode is enabled, the sort button in the Project Tree toolbar is pressed.

To enable manual sorting, click the sort button in the Project Tree toolbar to deselect it. The default order of items will change to chronological ordering, with most recently created items appearing last in a given container. To change the order of items within a container, select the item and drag it to the desired position within that container.

To move an item to a different container, for example to move a business item from one data catalog to another data catalog, first drop the item onto the catalog or logical node where you want it to be. The item will appear last in the new container. Then drag and drop the item to the desired position within the container.

There is a fixed order for item types within a catalog. For example, within the Process catalog, processes always come before tasks. Even if the logical nodes are not visible, you cannot change the order of these item types. For example, within the process catalog, even if you cannot see the separate containers for processes and tasks, you will not be able to reorder a task before a process.

The sorting mode and order of items is maintained when the product is restarted, and when catalogs are imported and exported. However, the ordering of items is not maintained when using project versioning. A catalog that is checked in and out again will revert to default alphabetical ordering.

Link-to-editor setting maintained on product restart

As an option in the Project Tree view, you can choose whether the navigation view selection is linked to the active editor. This means that when you are editing an item in an editor, that item is highlighted in the Project Tree. This is enabled by clicking the link-to-editor button in the Project Tree toolbar. Starting with this interim fix, the state of the link-to-editor button is maintained when you shut down and restart the product.