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-IF0000011.zip file.
2. Double-click the downloaded 6.0.2.1-WB-ModelerBas-IF0000011.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-IF0000011, 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 11

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
50623,6X8,760	JR28175	Eliminates an exception returned when performing auto-layout after adding a lane in swimlane layout.
65070,033,000	JR28275	Allows for checkout of all project elements after a project has been checked in with a renamed default catalog.

This interim fix includes the following fixes, which are associated with APAR JR28275:

• Eliminates an exception returned when opening the Process editor.
• Eliminates an exception returned when switching to swimlane layout to display a process with no content.
• Allows a disconnect from multiple projects using the Versioning > Disconnect action without restarting WebSphere Business Modeler.
• Correctly deletes persistent data from the filesystem after committing the deletion of a catalog containing leaf elements.

Fixes included in Interim Fix 10

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
50179,6X8,760	JR27931	Allows deletions from a repository by non-administrator users and users outside of the group that owns the repository.

Fixes included in Interim Fix 9

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
87271,010,678	JR27629	Additional corrections for checkout failures when two users are updating or renaming a shared element, and a third user attempts to perform a checkout.
87987,057,649	JR27721	Corrects a problem with the display of inputs and outputs on the Input and Output logic tabs in the Attributes view for a task when the number of inputs or outputs exceeds two.
00867,228,631	JR27755	Ensures that the History view displays the correct number of revisions when integrated with Clearcase.
29398,442,000	JR27759	Corrects an import problem where multiple elements are created in the Project tree for a single elment.
08598,500,000	JR27845	Prevents validation failure during XML export and report generation.

This interim fix includes the following fixes, which are associated with APAR JR27882:

• Ensures that a folder is correctly deleted even when a persistent element within the folder has been shared with a CVS repository.
• Corrects an issue with checking out a project after a process has been deleted from the repository.
• Corrects an issue where shared business items cannot be updated or opened.
• Corrects a migration failure when checking out a project developed in a previous product version, requiring migration.
• Corrects an issue where locked repository elements could not be unlocked

Fixes included in Interim Fix 8

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
00146,69C,760	JR26905	Guarantees the appropriate display of decision branch conditions for output branches when viewing conditions for multiple-choice decisions.
29896,6X8,760	JR27500	Marks the Commit and Update items with a warning symbol in the project tree view context menu to indicate that these actions in this context are deprecated, and will be removed from this context menu in future versions.
24687,442,000	JR27514	Corrects failure in deleting annotations.
50274,6X8,760	JR27609	Corrects an issue where copy and paste of stop nodes results in later misalignment of upstream connections, if the connection is moved from a from a pre-existing stop node to the pasted stop node.
87271,010,678	JR27629	Corrects checkout failures when two users are updating or renaming a shared element, and a third user attempts to perform a checkout.
50143,6X8,678	JR27707	Corrects a process diagram copy and paste failure when pasting a default start or stop node in swimlane layout.

Fixes included in Interim Fix 7

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
89120,442,000	JR27273	Enables the persistence of internal project data after a failure occurs.
50199,6X8,760	JR27532	Corrects an issue where copy and paste of stop nodes results in later misalignment of upstream connections.
22583,442,000	JR27542	Not a fix for the issue, however, code implemented to detect and assist in reporting if this swimlane corruption issue occurs.

Fixes included in Interim Fix 6

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
01973,758,758	JR26851	Ensures that new line characters are generated when specified in the content of the Description field for a Process procedure report template.
89135,442,000	JR27117	Corrects issues with modeling artifacts built through the Expression Builder.
86961,010,678	JR27177	Improves the message returned to users when a check out from CVS fails, including enhanced user feedback and recommended user actions.
34544,724,724	JR27249	Allows the opening of processes containing elements with leading or trailing blanks in their name.
30697,756,000	JR27255	Fixes a problem with repository labels being visible when the repositories in the diagram are hidden.
76545,500,000	JR27257	Improves the performance of some basic diagram editing operations.
91491,550,000	JR27260	Fixes incorrect behaviour in generated report templates where the font setting for a cell in the first row of a table is applied to all cells in the table.
09894,442,000	JR27316	Enhances the Repair process action, allowing WebSphere Business Modeler to open process models that have errors and were previously unviewable.
21728,442,000	JR27371	Fixes processing for corrupt data within a process model and allows the model to be published.

This interim fix includes the following fix, which is associated with APAR JR27380.

• Allows for the persistence of a Publishing server definition created via the Pubish action from the Project tree.

Fixes included in Interim Fix 5

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
61430,442,000 89201,442,000	JR27043	Corrects failure in report generation when queries have nested collation.
89176,442,000	JR27055	Corrects null pointer exception being surfaced to end-user when attempting to perform CVS check-out while disconnected from CVS server.
89146,442,000	JR27132	Fixes a problem where the product hangs when switching to swimlane view by roles.
31625,019,866	JR27145	Alleviates model corruption preventing user from opening a process model.
86412,010,678	JR27146	Corrects CVS committed elements from corruption due to rename actions.
89146,442,000	JR27161	Improves performance and scalability during project publishing action.

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

• Prevents project house keeping file, URIListFile.xmi, for a particular from being updated with information from another project.
• Prevents publishing failure by limiting the size of the xml being published
• Prevents publishing failure by passing user identifier and unique id on transmission
• Eliminates regression of failing when publishing models with attachments

Fixes included in Interim Fix 4

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
71849,033,000	JR26324	Corrects the display of gradient filled elements in a diagram that is embedded into a report exported to PDF.
61430,442,000 49080,442,000	JR26345	Avoids partial check-outs while performing the CVS team support check-out action, due to connection or other unknown failures on the client or server.
55957,999,000	JR26560	Corrects the displacement of the cursor to the beginning of the field, when the first character is typed in a date or time field of the Process editor's attributes view duration tab, for an unspecified Processing time or Resource wait time.
55958,999,000	JR26567	Corrects the behavior of collapsing sections of the Process editor's attributes view duration tab when focus is moved from element to element in the Process editor.
27469,756,000	JR26629	Corrects the display behavior for decision percentage labels, when toggling the Grid or Page break overlay, after setting the preference to hide in the Visual attributes page.
01607,033,000	JR26657	Ensures that text that is vertically aligned in the Report template editor appears aligned in the generated report.
12826,019,866	JR26713	Corrects problems with generation of Process level details or Task by role reports due to incorrect handling of certain characters (!@#$%^&*(){}[]'";`).
28444,756,000	JR26756	Ensures persistence of Page layout data under migration for global elements that support page layout.
00145,69C,760	JR26869	Elminates configuration issues reported by error markers on Modeler features in the Manage configuration view. A complimentary fix which is delivered as 6.0.2.1-WB-ModelerAdvModelerBas-IFJR26869 will resolve a similar configuration issue related to WID dependencies plugins.
75219,500,000	JR26871	Enhances the existing behavior for lock and unlock functionality while performing versioning actions for Clearcase.

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.

• Corrects problem with missing x-axis information in chart generation
• Corrects problem with extra characters appended to category labels in charts
• Fixes button icons on the Welcome pages in a plug-in installation of the product
• Ensures that Hindi numbers are displayed in reports when running the product in Arabic
• Synchronizes the measurement unit set in the general preferences for Report designer, and the unit reported for static text field via the attributes view for the Report designer
• Corrects regression with incorrect display of page numbers in generated reports

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.

• Corrects check-out error from a repository when a user defined catalog has the same name as a default catalog.
• Allows the application of a report style master to a Crystal report template
• Allows the application of a report style master to a Predefined report
• Corrects a Report generation problem when parameters have been previously associated to a deleted page of a Report template
• Eliminates exceptions when auto-layout is selected and performing a swimlane re-order

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.

• Corrects the default format type for a Business item's maximum attribute added to a report template.
• Removes a set of invalid diagram-related data fields for Process statistics, Process details and Process specification predefined queries and data sources.
• Corrects the calculation of the value for the number of Organization units in a Task statistics report.
• Removes the ability to generate the predefined Process procedure report for a Process catalog, in accordance with design specification.
• Eliminates an exception when generating a Task by roles report on a process with a role requirement that does not have its role value set.
• Corrects the names shown in generated Task details reports for requirements, resources and roles.
• Prevents customized Report templates and Style masters from being marked as different from repository in CVS synchronization view, when one of these committed elements is simply opened and closed.
• Corrects a percentage formatting problem with premature rounding at the incorrect decimal place in generated reports.
• Corrects an issue with elements, such as ellipses, not printing in the header of generated reports.
• Corrects an issue with the missing display of process diagrams in generated and exported Process summary reports.
• Corrects the timestamp on attachments for published elements.
• Includes National language support translation updates and fixes.
• Corrects inconsistent display of New context menu items in Report designer after the Fields view has been closed.
• Corrects the display and input of value representing midnight in time fields.
• Corrects a failure in the ability to add parameters to a report template that has been checked out using Team support.
• Adds "Decimal" to the list of formatters in the Field tab of the Attributes view for a report template
• Corrects an assignment issue when modifying Start time for a Timetable element.
• Eliminates default parameter values in the Enter parameter values dialog when generating a predefined report.
• Adds migration consideration for predefined report templates introduced in Version 6.
• Corrects the content generated using a Crystal report template.
• Corrects display of item names in Task details reports.
• Corrects a regression in generating Process level detail predefined report on processes containing a subprocess.
• Corrects missing content in printed output from the report generation preview dialog.

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.

Show or hide repository connection

In a process diagram, you can now show or hide repository connections. To show or hide the connections, right-click the diagram and select Show > Repository Connections. This feature is particularly useful in the FileNet Business Process Management mode because of the recommended pattern of using repositories to pass data.

Alignment of text that has been vertically aligned in the Report template editor

The alignment fix, provided through the fix for JR26657, requires that the user multi-select the text elements that should be vertically aligned, perform one of the align actions, for example, Align top via the toolbar button, and save the template.

The current fix is only available if elements are specified with Arial or Times New Roman fonts. Future updates to this component will give consideration to all supported fonts.

Alleviating connection errors while checking out from a CVS repository

If you are checking out projects from a CVS repository and your environment is configured with pserver or extssh (ssh2 only), you can attempt to alleviate failing check-outs due to connection errors by increasing the Communication timeout preference. To increase the Communication timeout, navigate to Windows > Preferences > Team > CVS, and increase the value of Communication timeout.

If you are checking out projects from a CVS repository and your environment is configured with pserver or ext or extssh (ssh1 only), a complimentary fix which will be delivered as 6.0.2.1-WB-ModelerAdvModelerBas-IFJR26345, will surface additional parameters to allow user-defined timeout values.

Lock and unlock behaviour for Versioning actions and Clear case repository

As of this interim fix, before showing the lock/unlock dialog, the Clearcase repository is queried for the lock status of the element being locked or unlocked. Based on the results returned the following actions are taken:

• If the element is not locked, the Unlock radio button of the Lock/unlock dialog is disabled, disallowing the unlock function for that element.
• If the element is currently locked, regardless of the view in which it is locked, the Lock radio button on the Lock/unlock dialog is disabled, disallowing the lock function for that element.
• If the element is locked, and the view that locked that element is not the current user's Clearcase view, the Unlock radio button is disabled. Furthermore, the dialog includes information about the element itself and the Clearcase view that currently has that element locked. Note: Due to a limitation of Clearcase clients on Windows 2000 environments, the Unlock radio button is always enabled on Windows 2000.

In all cases the OK and Cancel buttons are enabled, however if neither of the radio buttons can be selected, clicking either the OK or Cancel button will effectively cancel the operation.

Support for the IBM WebSphere Business Modeler FileNet Integration SupportPac

This support pack provides the FileNet Business Process Management mode and the FileNet Business Process Management export, both of which enable you to model processes that you can open with FileNet P8 Process Designer. For information on the SupportPac, refer to the BA77.pdf file included in the SupportPac ZIP file.

Swimlanes corresponding to deleted roles remain.

The fix for the problem where the product hangs when switching to swimlane view by roles, allows the user to open the swimlane layout of the diagram. The problem manifests when roles that no longer exist are being referenced. The swimlanes corresponding to the missing roles remain. Both the swimlane and the elements it contains are decorated with errors. To remove the swimlane, the user should perform an auto-layout.

Versioning Commit and Update actions are deprecated in the Project tree view.

With interim fix 8, the Commit and Update actions are marked as deprecated in the Project tree view context menu, and it is recommended that you not use them. They will be removed in the next release deliverable, WebSphere Business Modeler 6.1.0. Currently, the context menu items in the Project tree, Version > Commit/Update, will be marked with a warning symbol.The reasons for removing these actions are as follows:

• The Synchronize view provides equivalent functionality and is more intuitive, less error-prone, and has been better tested.
• Commit and Update actions from the Project tree view do not behave as users expect them to behave.
• Multiple mechanisms for achieving the same results leads to confusion.
• Naive usage can lead to loss of data, for example, as a result of users committing and overwriting changes in the repository, or users updating and overwriting local changes.

Model validation for XML export and report generation

When a user performs an XML export or generates a report, a model validation is performed as a precursor to the requested processing. Models are evaluated in sequence and invalid models are reported before any transformation errors occur.

Commit changes between multiple versioning actions

You might experience problems when attempting multiple actions from the Project Tree if you do not commit the changes between actions. For example, if you rename a process and then attempt to create another process with the same name, the create will fail. However, if you rename a process, commit the change, and then create another process with the same name, it will succeed.

After performing an action from the Project Tree (in particular, deleting, renaming, or moving an element from one catalog to another), it is highly recommended that you synchronize and commit your change before proceeding to make additional changes to your project.

As a result of a rollback in interim fix 11 to fixes involving Project tree rename actions and Versioning, which is necessary to resolve a more serious scenario reported in PMR 65070,033,000, the following scenario is considered to be a known limitation with a valid workaround.

Abstract: Synchronize view after update reports renamed elements as conflicts.

Requirement: This scenario requires two users. The two user requirement can be simulated by opening two workspaces on the same Modeler installation

1. User 1: Create "Business item 1", "Business item 2" and "Business item 3".
2. User 1: Share the project and commit the new elements.
3. User 2: Check out the project
4. User 1: Swap the names of the business item, ie,
1. "Business item 3" to "Business item 4"
2. "Business item 2" to "Business item 3"
3. "Business item 1" to "Business item 2"
4. "Business item 4" to "Business item 1"
5. User 1: Synchronize the project and commit the changes.
6. User 2: Synchronize the project and update the changes.

Expected: No content appears in the synchronize view

Actual: The renamed elements appear as conflicts in the synchronize view.

Workaround: In this specific scenario atleast two additional updates will be required before no content is reported in the Synchronize view. The requirement for the number of updates may vary if a derivative of this scenario is performed.

Unrelated to the rollback mentioned above, another rename scenario has been identified as a known limitation with a valid workaround. The following scenario exist before interim fix 11.

Abstract: Synchronize after check-out shows renamed catalog, and elements, as conflicts.

1. Create a project using default wizard values.
2. Rename the default process catalog, "Processes", to "My Processes".
3. Check the project into CVS repository. NOTE: Alternately, Clearcase can be the repository.
4. Delete the project and check it out from CVS repository, into the same workspace.
5. Synchronize the project.

Expected: No content appears in the synchronize view

Actual: The renamed catalog and the process appear as conflicts in the synchronize view.

Workaround: Perform an "Update from repository" action from the Synchronize view, on these conflicting elements.