Known issues

IBM Engineering Lifecycle Management installation media available on Passport Advantage site has no option to install IBM Engineering Workflow Management7.0.3 client on Visual Studio 2019 IDE and older supported versions.

First occurrence: 7.0.3

Problem: The IBM Engineering Lifecycle Management installation media available on Passport Advantage site allows you to install IBM Engineering Workflow Management 7.0.3 client on Visual Studio 2022, but not on the older supported versions of Visual Studio.

Workaround: You can use IBM Engineering Lifecycle Management 7.0.3 WebInstaller to install on older supported Visual Studio versions.

Unable to update an older version of IBM Engineering Workflow Management client to IBM Engineering Workflow Management 7.0.3 using the Installation Manager .

First occurrence: 7.0.3

Problem: You are not able to use the update functionality in the Installation Manager to update an older version of IBM Engineering Workflow Management client to IBM Engineering Workflow Management 7.0.3 due to IES version upgrade.

Workaround: You can uninstall the older version of IBM Engineering Workflow Management client from Installation Manager and install IBM Engineering Workflow Management 7.0.3 as a fresh install..

The older versions of Symantec Endpoint Protection cause issues with Edge Chromium-based embedded browser in the IBM Engineering Workflow Management client for Microsoft Visual Studio.

First occurrence: 7.0.2

Problem: If you are using an older version of Symantec Endpoint Protection, you might face a STATUS_ACCESS_VIOLATION or STATUS_INVALID_IMAGE_HASH error when you open the Edge Chromium-based embedded web UI in Visual studio.

Workaround: Update Symantec Endpoint Protection to the latest version.

Unable to simultaneously install IBM Engineering Workflow Management client on Visual Studio 2022 and prior Visual Studio versions using the IBM Engineering Lifecycle Management 7.0.3 Web Installer.

First occurrence: 7.0.3

Problem: When you use IBM Engineering Lifecycle Management 7.0.3 WebInstaller to install IBM Engineering Workflow Management client for Visual Studio, the installer gives error, if you first install IBM Engineering Workflow Management client on Visual Studio 2022 and then on any previous version of Visual Studio.

Windows 10 updates break IBM Engineering Workflow Management Shell Control Panel functionality.

First occurrence: 6.0.4

Problem: When you start the IBM Engineering Workflow Management Shell Control Panel by clicking the Start menu or the taskbar icon, you see a duplicate taskbar icon. Also, operations that you perform in the Control Panel such as switching modes, connecting to a repository, setting up a sandbox, or changing preferences, are not applied to other File Explorer windows. Each taskbar icon can display a different set of menu items based on the operations that you perform in the Control Panel. The Windows 10 updates that were released in October 2020 cause the Control Panel to open in a different explorer.exe process. IBM Engineering Workflow Management Shell does not support a configuration where multiple Windows Explorer processes are running at the same time. In version 6.0.3 or earlier, IBM Engineering Workflow Management Shell resides on the desktop and not in the control panel, and hence, is not affected by Windows 10 updates.

Related information: https://docs.microsoft.com/answers/questions/149362/opening-a-shell-window-registered-under-control-pa.html

IBM Engineering Lifecycle Management installation media available on Passport Advantage site has no option to install IBM Engineering Workflow Management 7.0.3 client on Visual Studio 2019 IDE and older supported versions.

First occurrence: 7.0.3

Problem :The IBM Engineering Lifecycle Management installation media available on Passport Advantage site allows you to install IBM Engineering Workflow Management 7.0.3 client on Visual Studio 2022, but not on the older supported versions of Visual Studio.

Workaround: You can use https://jazz.net or IBM Engineering Lifecycle Management 7.0.3 WebInstaller to install on older supported Visual Studio versions.

An error is shown when performing Git commit operation if you are using post receive hooks.

First occurrence: 7.0.2

Problem: In GitLab 15.3.1, when post-receive hooks are configured for linking work items to Git commits and you perform the push operation through the Git CLI client, an error “128: Author identity unknown” is shown. However, the Git push is successful and the work item is updated with a link to the Git commit.

IBM Engineering Workflow Management integration with BuildForge fails to connect through secure connection, https if IBMJSSE2 is used as a security provider.

First occurrence: 7.0.3

Problem: IBM Engineering Workflow Management integration with BuildForge over https fails to connect using IBM Semeru Runtime 11, Java 11 with "IBMJSSE2" security provider. This security provider was present in Java 8 but does not seem to be present in Java 11. Thus, secure connection using the "IBMJSSE2" security provider fails.

Link validity data entered for SCM files in 7.0.2 or lower versions is not available for reporting.

First occurrence: 7.0.3

Problem: Link validity data entered for SCM files prior to 7.0.3 version is not available for reporting in Report Builder. The data entered or modified in 7.0.3 is available.

Team private component visibility or user owned components are not visible in JRS reports.

First occurrence: 7.0.3

Problem: Report Builder reports do not include results containing SCM files, which are in either a component owned by a team area and which has Team Private visibility, or a component which is owned by a user.

Updating the link validity status for SCM files does not require a role-based-permission.

First occurrence: 6.0.4

Problem: The ability to update link validity status from within the SCM web UI does not use role-based permissions. If you have access to the file in the web UI, then you can update the link validity status.

Hovers are not displayed on any element that uses a browser to render content, most commonly the History tab and the Description field where rich text is present, if Edge is used as the embedded browser

First occurrence: 7.0.3

Problem: Edge does not support StatusTextListener, which is integral to the mechanism, and is used to trigger browser based hovers within the IBM Engineering Workflow Management Eclipse client. Elements within the IBM Engineering Workflow Management Eclipse client that are rendered as web content include History values and large HTML attributes, such as Description when they contain extended rich text. The attributes that contain extended rich text are displayed as read-only within the IBM Engineering Workflow Management Eclipse client and have an informational message "Edit rich-text content in the web client". The following setting controls the rendering of web content within Eclipse is set in the eclipse.ini, and if set to Edge, it results in the same behavior: -Dorg.eclipse.swt.browser.DefaultType=edge

Related information: https://www.eclipse.org/swt/faq.php#edgelimitations, https://www.eclipse.org/swt/faq.php#howuseedge, https://www.eclipse.org/swt/faq.php#browserplatforms