Known issues in 7.2.0

The following issues and limitations are known for 7.2.0 release. Some issues have workarounds and other issues are limitations.

Limitations

The following issues in this release do not have workarounds.

Mandatory upgrade to IBM® Engineering Lifecycle Management 7.1.0 SR1 (or later) before moving to Engineering Lifecycle Management 7.2.0 to ensure successful report migration and validation

Problem: Before upgrading to Engineering Lifecycle Management 7.2.0, you must first upgrade to Engineering Lifecycle Management 7.1.0 SR1 or any later 7.1.0 iFix. If reports or data sources still depend on LQE Jena, they will not function after upgrading to Engineering Lifecycle Management 7.2.0. This prerequisite ensures that report migration and validation are completed successfully, reducing the risk of issues after the upgrade.

For more information about known limitations, performance considerations, and migration constraints in the Engineering Lifecycle Management 7.2.0 release, see Key considerations and known issues when upgrading to ELM 7.2.0 (LQE relational store). Use this information to assess readiness and plan your upgrade effectively.

Conditional color overrides appear differently in the new UI

ID: Internal

First occurrence: 7.2.0

Problem: After applying conditional color formatting, some override colors might render differently in the new UI.

Text color on links is not applied in the new UI

ID: Internal

First occurrence: 7.2.0

Problem: Applying text color to links does not reflect in the new UI. Clarification needed on which color attribute is affected.

Pie chart overlaps with content below

ID: Internal

First occurrence: 7.2.0

Problem: Large datasets might cause pie charts to overlap with subtotals, x-axis labels, or legends.

Chart colors differ from classic UI

ID: Internal

First occurrence: 7.2.0

Problem: Chart colors might not match those in the classic UI due to a change in the underlying library.

Dashed lines are not supported

ID: Internal

First occurrence: 7.2.0

Problem: Dashed lines are not supported in the current chart implementation.

Date lines behavior differs from classic UI

ID: Internal

First occurrence: 7.2.0

Problem: Date lines are implemented as a workaround and do not replicate classic behavior. Y2-axis support is also missing.

Bar thickness is slimmer than classic UI

ID: Internal

First occurrence: 7.2.0

Problem. The bars in bar charts appear slimmer than in the classic UI.

X-axis overlap in large charts

ID: Internal

First occurrence: 7.2.0

Problem: X-axis values might overlap in large bar or line charts due to fixed chart size and lack of horizontal scroll.

Vertical scroll missing for horizontal charts

ID: Internal

First occurrence: 7.2.0

Problem: No vertical scroll support for horizontally oriented charts.

Legend positioning and axis value representation vary.

ID: Internal

First occurrence: 7.2.0

Problem: Legends and axis values might appear different compared to classic UI.

Show values and grid lines are not supported

ID: Internal

First occurrence: 7.2.0

Problem: The option to show the values and grid lines is not available.

Clickable x-axis labels are not supported

ID: Internal

First occurrence: 7.2.0

Problem: X-axis labels are not clickable in the new UI.

Multiple goal lines and date lines with bar charts are not supported

ID: Internal

First occurrence: 7.2.0

Problem: Multiple goal or date lines do not render correctly with bar charts.

Decimal target lines are not supported

ID: Internal

First occurrence: 7.2.0

Problem: Cannot create target lines with decimal values.

Chart export limited to excel (tabular only)

ID: Internal

First occurrence: 7.2.0

Problem: Only excel export is supported for charts; no PUB api integration for chart output.

Export options always visible; drill-down limited to excel

ID: Internal

First occurrence: 7.2.0

Problem: All export options are visible in new UI to support existing reports, but drill-down is only available in excel.

Column width changes in classic are not reflected in the new UI

ID: Internal

First occurrence: 7.2.0

Problem: Column width changes made in Report Builder classic are not retained in the new UI.

Data source or property changes require page refresh

ID: Internal

First occurrence: 7.2.0

Problem: After changing data source or toggling data warehouse properties, a page refresh is needed to reflect updates.

System alerts do not support rich text/html

ID: Internal

First occurrence: 7.2.0

Problem. JRS system alerts cannot render rich text or html.

"Select all" missing in tree-rendered filters

ID: Internal

First occurrence: 7.2.0

Problem: “Select all” option is missing in the filter panel for enumerations that are rendered as a tree.

Embedded images are not always rendered correctly; embedded links open in the wrong context when clicked

ID: DT382330

First occurrence: 7.0.2

Problem: In Report Builder, when viewing images embedded into the primary text of an RM artifact, those images get resolved by the DNG server without any context provided. Our embedded images purposely only consist of a link to the concept URL of the image without a configuration, so in Report Builder, the browser simply makes a GET request for the image without providing a context. If the image is not present in the default configuration, this results in failure (and JRS does not show any content), otherwise the image version from the default configuration is used, which might not be the same version that should be used for the report scope.

Multiple link types for relationships cause report timeouts (Oracle)

ID: DT438165

First occurrence: 7.0.3

Problem: Reports that specify two link types on for a relationship can time out. The specific example was a report on DNG artifacts, that traced from a Module > uses Requirement > Links To, Links From Requirement.

Report Builder defaults the custom attribute enum type to RICALM.REQUEST_STRING_M_EXT for DCC type reports

ID: DT451004

First occurrence: 7.0.3

Problem: Custom attribute of type ENUM in CCM are populated to smallString sometimes. The default extension table for enum types in RB is mapped to mediumString in the generated query. It should check all the extension tables to capture the populated value.

Custom reports cannot be imported back to JRS

ID: DT452969

First occurrence: 7.0.3

Problem: Custom reports cannot be imported back to JRS.

Users with special characters in their user-ID are seeing 401 Unauthorized error

ID: DT455340

First occurrence: 7.1.0

Problem: Users with special characters in their user ID get a 401 Unauthorized error after enabling LTPA check.