Known issues in Engineering Insights 7.1

Edit online

The following issues and limitations are known for Engineering Insights 7.1 release. Some issues have workarounds, other issues are limitations.

Workarounds

The following issues in this release have workarounds.
The rendered links are not adjusted automatically when the link direction is set to Auto

First Occurrence: 7.0.2

Internal ID: 569536

Problem: For the linked container scenario, the rendered links might not align.

Workaround: You can manually adjust the linked containers, for example, by dragging the container to add more rendered links.

The toolbar option of Engineering Insights view is not properly visible on the Safari 16.0 browser

First Occurrence: 7.0.2

Internal ID: 569537

Problem: The toolbar option in Engineering Insights View is displayed improperly when the Safari browser is used.

Workaround: You can adjust the zoom of the browser. Zoom in or zoom out so that the toolbar is properly displayed.

Multiple query Lifecycle Query Engine selection options are not available in impact analysis diagram and custom artifact elements if one of the Lifecycle Query Engines is down

First Occurrence: 7.0.2

Internal ID: 578103

Problem: To display the query language selection options Engineering Insights fetches the status of Relational Store and Triple Store from all the registered Lifecycle Query Engine instances. If any Lifecycle Query Engine instance is down, the API in Engineering Insights fails to fetch the status from the Lifecycle Query Engine and does not show the expected response. This failure affects Engineering Insights and application is unable to display the query language selection options. This failure also happens if both - Relational and Triple stores are enabled in one of the Lifecycle Query Engine instances.

Workaround: Start or unregister the failing Lifecycle Query Engine instance.

Applications stop responding when selected for showing the count of Rhapsody® Model Manager linked containers

First Occurrence: 7.0.2

Internal ID: 570611

Problem: Engineering Insights page stops responding when a large set of data is loaded in Engineering InsightsViews

Workaround: You can apply a relevant project area scope to view and necessary conditions on the node containers to limit the data to the necessary set.

Filter behavior for child artifact types

First Occurrence: 7.1

Internal ID: 578429

Problem: In certain cases, the filter feature does not give expected results when applied to child artifact types for creating an impact analysis diagram.

Workaround: Use the filter on the root artifact type to achieve the expected filter results and maintain accuracy in the workflow.

Limitations

The following issues in this release do not have workarounds.
Building query failed for Show properties (SQL view, opt-out)

First Occurrence: 7.1

Internal ID: 578059

Problem: In the SQL-based view, Show properties for resource node do not work for a few cases and displays a Query failure error.

Inconsistent number of results at Select Artifact - CAE, SPARQL

First Occurrence: 7.1

Internal ID: 577001

Problem: In a SPARQL-based custom artifact element (CAE), running search in the Preview result dialog gives an inconsistent count that is displayed at different locations.

No help content is available message is displayed for all context-sensitive help

First Occurrence: 7.1

Internal ID: 565540

Context-sensitive help, which is displayed when hovered over does not work. The No help content available message is displayed.

Sorting based on Name at Views doesn't work

First Occurrence: 7.1

Internal ID: 577475

Problem: On the Browse views page, sorting based on view name does not work.

Exclude filter not operating correctly for an impact analysis diagram

First Occurrence: 7.1

Internal ID: 578428

Problem: When you apply the excluded filter on an impact analysis diagram, the excluded items appear in the diagram.