v15.2 β - Release Notes - Diagramming

[Paolo F Cantoni]

The v15.2 β - Release Notes (under Diagramming) mention:
Copying elements between diagrams now always duplicates Note, Text and Boundary elements

Supposing, just supposing, a customer used a modelling methodology where these types of elements, were, MUCH more often than not, NOT duplicated between diagrams.

Could this be an optional behaviour?

From our perspective, the only element type that is unique to a diagram is the (incorrectly named) Diagram Note element - which is used as a "Title Block".  Even Legends are common between diagrams. From our point of view, if you don't want the same note on the second diagram, create a new note - seems intuitive to us.

In an enterprise environment, one of the last things you want is the proliferation of these (typically non-browser visible) objects because users can't get used to the inconsistent approach.

We currently, go to a LOT of trouble to find and eradicate these "viral" objects.

Paolo

[Eve]

The v15.2 β - Release Notes (under Diagramming) mention:
Copying elements between diagrams now always duplicates Note, Text and Boundary elements

Supposing, just supposing, a customer used a modelling methodology where these types of elements, were, MUCH more often than not, NOT duplicated between diagrams.

Then such a custom will likely experience issues due to that practice. (Including, but not limited to the objects being deleted when not expected) If they haven't experienced it already, then it's a matter of time until it does become an issue.

[Paolo F Cantoni]

The v15.2 β - Release Notes (under Diagramming) mention:
Copying elements between diagrams now always duplicates Note, Text and Boundary elements

Supposing, just supposing, a customer used a modelling methodology where these types of elements, were, MUCH more often than not, NOT duplicated between diagrams.

Then such a custom will likely experience issues due to that practice. (Including, but not limited to the objects being deleted when not expected) If they haven't experienced it already, then it's a matter of time until it does become an issue.

So I guess the answer is (still) NO?

Since we train our users that ALL elements are linked^[1], they don't seem to have the problem.  Certainly, no one has complained in all the years we've been doing this.  In fact, they complain as to the opposite.  "I changed the note, but it only affected the diagram I was changing!"

Paolo

^[1] "Title Block" is clearly a copy since the rendered content is different (unlike the other types).

[Eve]

I have good news.

Your request was raised about this, we aren't going to add an option. We are investigating the effect of removing all of the diagram specific behavior for them. Including allowing them all to appear in the Browser. I can't guarantee it will happen, but there weren't any issues doing it for Legends or Constraints.

Thanks for your interest in the beta.

[Paolo F Cantoni]

I have good news.

Your request was raised about this, we aren't going to add an option. We are investigating the effect of removing all of the diagram specific behavior for them. Including allowing them all to appear in the Browser. I can't guarantee it will happen, but there weren't any issues doing it for Legends or Constraints.

Thanks for your interest in the beta.

I had to pinch myself, to make sure I wasn't dreaming!  More used to the "Darryl Kerrigan" response...  "tell 'im 'e's remain!

Anyway, thanks for listening to the argument in favour.  As you say it didn't "break" legends or Constraints.

Paolo

[RoyC]

Eve does have a couple of Jousting sticks in the back yard, though...

[Geert Bellekens]

I have good news.

Your request was raised about this, we aren't going to add an option. We are investigating the effect of removing all of the diagram specific behavior for them. Including allowing them all to appear in the Browser. I can't guarantee it will happen, but there weren't any issues doing it for Legends or Constraints.

Thanks for your interest in the beta.

I guess that includes the boundaries? That would be good news indeed.
With the update of ArchiMate 2 to ArchiMate 3, Groupings have become stereotyped boundaries (from Component in v2?) which makes them disappear from the project browser.
If you had nested elements in those boundaries in v2 they now lose that grouping in the project browser and all end up underneath the package.

Showing the boundaries in the project browser would supposedly fix this problem.

Geert