Sparx Systems Forum

Enterprise Architect => Automation Interface, Add-Ins and Tools => Topic started by: allist on March 13, 2015, 03:14:16 am

Title: Extending TOGAF MDG Technology
Post by: allist on March 13, 2015, 03:14:16 am

Hello all,

We're trying to extend an object in the TOGAF 9.1 MDG Technology to make it more specific for our enterprise. We believe it to be possible since there is an article showing how to do so here: http://www.sparxsystems.com/enterprise_architect_user_guide/10/extending_uml_models/non_uml_metatypes.html

However, it's not working as expected. The extended element is shown in our toolbox, but when we try to drag it to any diagram it doesn't get created.

Here is our relationship in our UML Profile:

(http://i58.tinypic.com/35minax.png)

Can anyone spot anything wrong?

Title: Re: Extending TOGAF MDG Technology
Post by: KP on March 13, 2015, 09:12:09 am

Add an Extension from your «stereotype» to a «metaclass»Activity

Title: Re: Extending TOGAF MDG Technology
Post by: allist on March 14, 2015, 03:38:24 am

I've added this relationship:

(http://i58.tinypic.com/v75a9d.png)

But it still did not allow me to create a ChiBusinessProcess after saving the profile, regenerating the technology and importing it.

I also tried this way, in case I misunderstood you:

(http://i60.tinypic.com/28amirs.png)

Title: Re: Extending TOGAF MDG Technology
Post by: KP on March 16, 2015, 09:27:08 am

Either way should work. Can you send your technology file to Sparx Support please? Somebody there should be able to figure out the problem.

NB: You do have the TOGAF technology enabled, don't you?

Title: Re: Extending TOGAF MDG Technology
Post by: allist on March 17, 2015, 02:19:24 am

Yes, the TOGAF technology is enabled ;)

I will send to support. Thank you for the help!

Title: Re: Extending TOGAF MDG Technology
Post by: allist on March 17, 2015, 03:08:14 am

UPDATE: Finally fixed it and got it working. I created a brand new profile and got it to work right away so that got me thinking something else was wrong. Turns out in our Toolbox profile, it was set as UML::Package. When I changed it to UML::Activity, it started working.

Thanks again for all the help!