Rhapsody DiffMerge - Improve Consistency And Functionality of Graphical Merging

Currently, there are several discrepancies when viewing or merging model content through a diagram view or graphical merge versus inspecting it in the DiffMerge browser.
-Elements on a diagram can have their Rhapsody Features window invoked. Elements in the browser cannot, and are instead summarized in a table (or nested objects/tables).
-Elements on a diagram can display their Rhapsody tooltip, when a user hovers their mouse over the element. Elements in the browser have no equivalent functionality.
-Elements on a diagram have a context menu option to "locate" (although not clear if this is ever an enabled option). Elements in the browser have no equivalent "locate on diagram" option.
-Resolving certain diagram elements graphically can have their corresponding model elements also resolved in the merge. However, resolving elements in the browser does not often resolve a graphical merge.
-Elements with differences indicated graphically (model or graphical) do not have their differences summarized (just that a graphical difference exists). Model elements in the browser can summarize what their difference is.
-Elements indicated as a difference on a diagram in a graphical merge are limited in showing what type of change they exhibit or their merge status. However, there are two graphical indicators to show the difference/merge status of every element in the browser.
-Elements cannot be filtered on a diagram in a graphical merge as they can be from the DiffMerge View menu in the browser (show all, show differences, show undecided, etc.).

In a nutshell, these examples are just to say the workflow and tools available to affect a change in Rhapsody is sometimes very different than the equivalent workflow to affect the same change in DiffMerge.