Sparx Systems Forum

Enterprise Architect => Suggestions and Requests => Topic started by: JohnE on September 04, 2019, 11:45:59 pm

Title: Why is ApplicationComponent not a valid Element Type?
Post by: JohnE on September 04, 2019, 11:45:59 pm

When using the ArchiMate model, 'ApplicationComponent' is set as the Element Type when selecting the 'Archimate_Application Component' stereo type.

Under certain circumstances (such as when a an eaXL import is executed) the Element Type is changed to 'Component' but using the Type drop down there is no way to select 'ApplicationComponent'.

To work around this I have had to change the stereotype to anything else and then back to 'Archimate_Application Component'. (a bit of effort for a few hundred elements... or work out how to create a script for this).

Can 'ApplicationComponent' be set as a valid entry in the Type drop down and and other scripts to stop the import breaking it?

Regards,
John

Title: Re: Why is ApplicationComponent not a valid Element Type?
Post by: Geert Bellekens on September 05, 2019, 03:08:52 am

In fact the element type is never really changed. It's only the GUI that interprets the stereotype and shows you the metatype associated with that stereotype.
If you look in the database you'll notice that the field t_object.Object_Type is always "Component"

What probably happens is that EA somehow looses the fully qualified stereotype. This sometimes happens if you have this stereotype also in the UML stereotypes in the database.
If you delete that rogue stereotype this problem might be solved.

Geert

Title: Re: Why is ApplicationComponent not a valid Element Type?
Post by: JohnE on September 12, 2019, 12:47:49 am

Thanks Geert,

I also upgraded to the latest version which seems to handle this better.

Regards,
John