Author Topic: Redefining an ArchiMate element does not work as expected?  (Read 2304 times)

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13065
  • Karma: +544/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Redefining an ArchiMate element does not work as expected?
« Reply #15 on: July 03, 2024, 06:48:25 pm »
Could it depend on where the MDG is located?
If the MDG is saved within the same model's Resources then maybe relaunching EA is not necessary, but with an MDG saved to the local disk I guess the relaunch is needed so that EA goes to the disk (/server) and brings in the MDG definition from the xml again.
Just a guess based on some thing I've been doing recently.
In any case, I'm with the rest of you - "Troubleshooting step 1 is to turn it off and on".
Even with MDG's in the model you need to restart EA for some things.

Geert

Sunshine

  • EA Practitioner
  • ***
  • Posts: 1295
  • Karma: +119/-10
  • Its the results that count
    • View Profile
Re: Redefining an ArchiMate element does not work as expected?
« Reply #16 on: July 11, 2024, 04:21:51 pm »
If anyone is interested here is an EA MDG that extends ArchiMate and adds attributes to various elements like application component.
https://github.com/EASunshine/Sparx-EA/blob/master/EAMDGProfile.zip
Happy to help
:)