New feature to add existing relationships to a view for a selected element

Sometimes 2 or more views have similar information, and during workshops, one view can be evolved to contain more relationships and details.

It would be very useful if there was an easy way to add those extra details across other similar views. e.g.

1. Right click on a view element and select a new "Add all relationships" menu item (preferred), or
2. Be able to drag/drop from the Visualiser onto the active view.

I know that there is a way to find and add any relationships to a view which exist in the underlying model but it is very fiddly and manual.

I think 1. above is probably the best way to go because there typically won't be a huge amount of relationships attached to a given model element and the modeller could then just delete those elements which were added by the "Add all relationships" function but not needed.

If this is still not clear, here's an example.

1. I create View1 with App Component 1 (AC1)
2. I create View2 with AC1 and AC2
3. I go to View1 and associate App Function 1 (AF1) with AC1, and AF2 with AC2. I then also add a Flow relationship between AF1 and AF2.
4. I go to View2. The problem here is that depending on the modelling requirements and viewpoint I may want to know all of the interesting modelling which has recently occurred.

• If select AC1 on View 2 and choose "All all relationships" then AF1 should appear.
• If if then choose AF1 on View 2 and choose "All all relationships" then AF2 should appear.
• Finally, selecting AF2 and choosing "Add all relationships should make AC2 appear.

I know all of this is in the model and the visualiser but I'm lazy and think this would be a great way to blend discovery and modelling.

Start by locating the view-element context menu and the existing relationship lookup or Visualiser-to-view interaction. Implement the preferred “Add all relationships” flow for a selected element, including relationships whose other elements are not yet on the view, and verify the step-by-step AC1, AF1, AF2, and AC2 example behaves as described.