Workarounds and Limitations: Known issues in IBM Engineering Workflow Management 7.0.3

Older versions of Symantec Endpoint Protection cause issues with Edge Chromium-based embedded browser in the EWM client for Microsoft Visual Studio

Workaround

Related Information
Task 535727

Windows 10 updates break EWM Shell Control Panel functionality

1. Create a folder and change its attribute to read-only.
2. Rename the folder to IBM EWM Shell.{1632EAAE-5B6A-4861-AE2E-90BA389AF9BC}.
3. Open the folder to ensure that it displays the EWM Shell Control Panel.
   Note: Opening this folder does not start a new Explorer process.
4. Pin the folder to the Start menu or taskbar or create its shortcut on the desktop.
5. Click the folder icon that is pinned to the taskbar or double-click the shortcut icon on the desktop to start the EWM Shell Control Panel.
   Note: To open the EWM Shell Control Panel, use the new icon that you created instead of the default shortcut icon.

ELM installation media available on Passport Advantage site has no option to install EWM 7.0.3 client on Visual Studio 2019 IDE and older supported versions

Unable to simultaneously install EWM client on Visual Studio 2022 and prior Visual Studio versions using the ELM 7.0.3 WebInstaller

Workaround
Remove the cached files from Installation Manager. If you choose this option, you will not be able to roll back to a previous version.In order to remove the cached files, start the Installation Manager with Administrative privileges. Go to File->Preferences->Files for Rollback and click Delete Saved Files.

Related Information
[EWM][Visual Studio] Unable to simultaneously install 703 VS Clients on VS 2022 and prior Visual Studio versions using WebInstaller (569345)

Unable to update an older version of EWM client to EWM 7.0.3 using the Installation Manager

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.

Related information
[EWM][Git]Exploring post-receive hooks for gitlab15.3.1 (556882)

EWM integration with BuildForge fails to connect through secure connection, https if IBMJSSE2 is used as a security provider

First occurrence
7.0.3

Problem
EWM 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.

Related information
565978: [Java 11][Build Forge]After Java 11, “A java.io.IOException exception occurred testing the connection.no such provider: IBMJSSE2” appears during buildForge scenario execution.

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.

Related information
568382: Link Validity – Report result for LQE with config data source is different for SPARQL and SQL for link validity on SCM File links

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.

Related information
525491: Prevent publication of team private items

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. All users that have access to the file in the web UI can update the link validity status.

Related information
568903: Permission enable the ‘Update Link Validity’ operation (on SCM File OSLC links) to require role-based permissions. Lack of EWM/RMM control on who can set link validity creates governance/security hole in ELM.

When using the EWM Eclipse client with Edge as the embedded browser, hovers do not display on the History tab or in the Description if rich text is present

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 EWM Eclipse client.
Elements within the EWM 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 EWM 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 above 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