Book a Demo

Author Topic: Time aware modelling - Clone structure as new version  (Read 32110 times)

wivel

  • EA User
  • **
  • Posts: 243
  • Karma: +12/-1
  • Driven by Models
    • View Profile
Re: Time aware modelling - Clone structure as new version
« Reply #15 on: May 03, 2024, 09:49:02 pm »
Just an additional thought, the only thing I can think of is that I pressed Ok without changing anything on the 1st dialog, ended up with 2 packages with the same name and version number, and lost track of which one was the original one.

I did the same thing first time I tried. At least a warning from EA would be nice.

Henrik

Modesto Vega

  • EA Practitioner
  • ***
  • Posts: 1183
  • Karma: +30/-8
    • View Profile
Re: Time aware modelling - Clone structure as new version
« Reply #16 on: May 08, 2024, 11:03:31 pm »
The issue was definitely caused by me "accidentally" creating a new cloned version of the package with the same name and version. The fact that I can do that and that the new package is placed above the cloned package in the browser does not help, improving that is essential to modify to improve the usability of time based modelling.

All of this dovetails with another recent post - please see https://sparxsystems.com/forums/smf/index.php/topic,48435.0.html. The way Sparx EA handles this is "incompatible" with the document template resulting from that post because, by default, only the diagrams are cloned to anew version, with that template, any none cloned (to a new version) elements will not appear in that document.

Modesto Vega

  • EA Practitioner
  • ***
  • Posts: 1183
  • Karma: +30/-8
    • View Profile
Re: Time aware modelling - Clone structure as new version
« Reply #17 on: May 10, 2024, 01:34:07 am »
Apologies for keeping this thread open. A couple of other issues related to this are:
  • Somehow Sparx EA remembers the view or package where a new cloned version is/was created, this is an issue if reorganising the contents of the package containing the cloned version
  • To clone all elements or not to clone elements (even if elements don't change)? Because of the way elements are reused in Sparx EA, the stay in their package, there only to ways to include them in a document: either iterate through all elements on a diagram, or cloned all elements into a new package and iterated through the new versions.

Thoughts and comments are much appreciate it.