Cannot add a stereo type to my toolbox

[Arnoud_B]

Sorry forum, I feel sometimes (well actually often) rather stupid trying to get things in Sparx going. Although the documentation is not bad it is never complete and understandable for me.
So I have another dummy start-up question:
I have created a MDG Technology model and create a profile package where I extended some ArchiMate 3 elements but for now only giving them new names.
Now I want to add them to a toolbox (and later create a diagram type to use them on)
So I create a toolbox package and a toolbox page and with the "edit with profile helper"; "Add"; "Add Stereotype"; I select my 'new' element from the <<profile>> package click OK AND ... nothing happens no error but also nothing added to my toolbox page. I now read the instructions 4 times in 3 days and I feel that I miss the obvious (again) but I am clueless what I do wrong.

[Geert Bellekens]

Had the same issue.

The problem is that the toolbox needs the original UML meta class. What I usually do is add an extension to whatever UML metaclass the Archimate stereotype was extending.
That way the profile helper can add my stereotype to the toolbox for me.
You can remove that extension later if you want, but I don't think it hurts to have it there either. (you will also need it if you want to group your tags)

Geert

[Arnoud_B]

Thanks Geert, I was afraid of something like that. If you know it is not a big problem but it is nowhere clearly documented and I spend a lot of time getting 'simple' things running. But that is called learning I think 
Then a follow up question, how can I find which UML class the Archimate class I am extending was using. There is a large range of stereo types to choose from and I actually do not understand the data model behind.

[Arnoud_B]

OK RTFM 
If I look at the Archimate3 UML I see for instance that the ArchiMate_TechnologyService definition contains <Apply type="Activity"> So I imagine that it extends that UML type. So my STIB_TechnologyService now extends both the ArchiMate service AND the UML Activity and then it pops-up in the list.
Did I interpret your response correctly?

[Geert Bellekens]

Yes, the "easy" way to figure out the basic UML metatype is to create such an element in EA, and then remove the stereotype.

Geert

[Arnoud_B]

So now I managed to create a MDG; some elements, a toolbox and a diagram type.
However my elements extend both an ArchiMate3 type and a UML type as otherwise the toolbox would not work.
The elements now have all behaviour of the UML type and nothing of the ArchiMate3 type they extend, no icon no connectors to choice from not the image nothing.
So why did I extend the ArchiMate3 type? Is it actually possible to extend extentions or do you always have to start from the UML basic types and then create your own element type all together.
I could do that by reading the Archimate3 MDG file and copying all I want to retain and changing what I want to change but I then need to create my own ArchiMate3 implementation and I just wanted to extend it left and right.
In the documentation they only show how to build an MDG from the ground up, I do not know I have the time and energy to go that direction (well if I need to I'll have to ;-/ )

[Geert Bellekens]

Yes, it's definitely possible. You need a Generalization from your stereotype to the ArchiMate Metatype.

If you post a picture of your profile diagram, we might be able to spot the error.

Geert

[Arnoud_B]

  
And how do I post an image??

img]C:\\Users\\buitenhuisa\\Desktop\\SparxSnip.png[/img]

Does not work.

[Geert Bellekens]

post it on a public image hosting site such as imgur.com and put the link here.

Geert

[Arnoud_B]

Hope this is visible:
https://imgur.com/a/GhKOttI

[KP]

As Geert said, you need a Generalization, not Extension, between <<stereotype>> elements. The Extension from <<stereotype>> to <<metaclass>> is correct.

[Arnoud_B]

Indeed he said so but I did not read accurately enough, I do not think the Sparx documentation mentions this but I will re-read. I think the Sparx documentation is certainly not bad but it is hard to do it correct just using the book, but I admit sometimes you have to read really carefully as a small mistake will not give you an error but just a silent fail.
My extension looks way better already ;-) I have correct icons in the project browser however the shape is still different from the Archimate3 version, size and color are different but the top right icon is now correct. Well I know how to manually correct that however it would be nice to know if I still did something wrong or that this is the expected behaviour of Sparx. Also the relationships proposed when linking the overwritten element to another element are different from the ones proposed for the Archimate3 stereotype extended.
Well thanks very much for the help sofar I am on the move again, some more reading of the fucking manual to do 

[qwerty]

Many things in life can't be learned by RTFM but just by the pain of the real thing...

q.

[Arnoud_B]

Yep that is what I'm doing I read the manual and then try to get it working. It is a painful process for now however there is some kind of logic in Sparx. When I started scripting it never worked but after a while I got (mostly) the hang of it how to interpret their docs. I hope I will make some progress in that direction with the MDG as well. For now it is slow progress but well learning a new language is not a thing you do in two days ...