Pasting a diagram with legends using Shallow type

[Modesto Vega]

Another issue with legends. Just noticed that when copying a diagram as pasting it as new diagram with a "Shallow - Links to exiting elements only"  type, legends are copied. This makes legend reuse difficult and cumbersome.

Why aren't legends treated as if they were another diagram element?

We are using v16.1.1621 64-bit with a SQL Server backend.

[Geert Bellekens]

Exactly!

For one client I had to write a cleanup script just to get rid of all the duplicate legends.

Geert

[Paolo F Cantoni]

Exactly!

For one client, I had to write a cleanup script just to get rid of all the duplicate legends.

Geert

Modesto, it has always been so.  This is another manifestation on the diagram "owning" certain types of elements.  I'm not familiar enough with the depths of the UML spec to determine if this is a UML requirement or merely a "Sparxian" decision.  In either event, I believe it is spurious.  In the case of relationships, there is a setting to override the "strict" UML behaviour.  There should be something similar for these elements.
In our view, the only element that should be unique to a diagram is the Title Block (incorrectly referred to as the DiagramNote Element).  If the user is making a shallow copy, by definition, they want links, not instances.

Like Geert, we've had to write automata to clean up the duplicates and point all references to the "template" instances of Legends, Notes, Texts etc...

Paolo

[BobM]

I had reported this legends bug in v16.1.1621.64bit on 1st of december 2022

Thanks for contacting Sparx support.
We appreciate your findings. The issue you highlighted has been reported to the appropriate team and is confirmed as an issue. This will be addressed in the future releases.

In 16.1.1623 release notes:
Ensure Diagram Legend objects are not duplicated with a Shallow Diagram copy or Diagram Clone

[Geert Bellekens]

I had reported this legends bug in v16.1.1621.64bit on 1st of december 2022

Thanks for contacting Sparx support.
We appreciate your findings. The issue you highlighted has been reported to the appropriate team and is confirmed as an issue. This will be addressed in the future releases.

In 16.1.1623 release notes:
Ensure Diagram Legend objects are not duplicated with a Shallow Diagram copy or Diagram Clone

So it should be fixed now? nice

Geert

[BobM]

So it should be fixed now? nice

Geert

It has been fixed on Januari 17th 2023
I think it was a complete fix as I heard no more complaints about it after we installed that update.

[Modesto Vega]

Thank you Gert and Bob, I guess it is time to upgrade to v16.1 (Build 1625), the latest.

I am hoping Sparx Systems doesn't make another release soon, our service desk is never happy with frequent upgrades.

Paolo, since they fixed the issue; it must be a bug and does not have anything to do with strict UML behaviour.

[Geert Bellekens]

I am hoping Sparx Systems doesn't make another release soon, our service desk is never happy with frequent upgrades.

On the contrary for me. I'm still waiting for the bugfix to make document generation work again as it was in v15.2
I have several clients who are stuck on v15 because of this bug in v16.

I had a few encouraging conversations with Sparx about this, but it has been all crickets and tumbleweeds for the last couple of months.
Makes me afraid they are working on v16.5 or v17 or something like that and no longer focussing on fixing regression bugs in v16.

Geert

[Modesto Vega]

Can you please remind me what the documentation issue is?

Hopefully, Sparx has not accidentally reversed the preference mentioned here, https://sparxsystems.com/forums/smf/index.php/topic,47671.0.html, in Build 1625.

If they have, upgrading to Build 1625 is not an option.

[BobM]

I am hoping Sparx Systems doesn't make another release soon, our service desk is never happy with frequent upgrades.

As I'm waiting for some mayor and minor bug fixes as well, I marked 9th of June as a potential release date for a new version, if it isn't then there might be no releases until 16.2 which is predict will be released right after global summit (in September?).

[Geert Bellekens]

Can you please remind me what the documentation issue is?

https://sparxsystems.com/forums/smf/index.php/topic,47342.msg276026.html#msg276026

Geert

[Paolo F Cantoni]

Thank you Gert and Bob, I guess it is time to upgrade to v16.1 (Build 1625), the latest.

I am hoping Sparx Systems doesn't make another release soon, our service desk is never happy with frequent upgrades.

Paolo, since they fixed the issue, it must be a bug and does not have anything to do with strict UML behaviour.

With respect Modesto,
My suspicion is that Sparx made Legends "the exception that proves the rule".

When I said it's always been so, we ran the tests as soon as Legends were created and Legends fitted the "Bjelke-Petersen Test - If it walks like a duck and it quacks like a duck, it'll get shot like a duck!  My word it will".  It never occurred to us that Legends should be different to the other Text elements - which, as I mentioned, we believed shouldn't be cloned.

It's good that it's been fixed, although we don't care anymore as we have to manage a pile of other item metatypes in the same way.

Paolo

[Modesto Vega]

Paolo, fully appreciate where you are coming from, it is not easy to manage upgrades of large repository with legacy content and customisations.

[SNIP]
"Bjelke-Petersen Test - If it walks like a duck and it quacks like a duck, it'll get shot like a duck!  My word it will".

Have you considered the possibility that Sparx Systems made it look and quack like a duck, until they realised it actually wasn't a duck?

[BobM]

On the contrary for me. I'm still waiting for the bugfix to make document generation work again as it was in v15.2
I have several clients who are stuck on v15 because of this bug in v16.

I had a few encouraging conversations with Sparx about this, but it has been all crickets and tumbleweeds for the last couple of months.
Makes me afraid they are working on v16.5 or v17 or something like that and no longer focussing on fixing regression bugs in v16.

Geert

Hi Geert,

I noticed a lot of entries on document generation on the 1626 release
Have all issues been handled "properly"?

[Geert Bellekens]

I wouldn't know. I had no idea there was a 1626 .

I do keep an eye on the latest news forum, but it seems they forgot to publish it there. https://sparxsystems.com/forums/smf/index.php/board,22.0.html
(oh, I see, its only just released today)

I'll let you know as soon as I'm able to test it. It sure looks promising.

Geert