Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - rmartinezb

Pages: [1] 2 3
Thanks qwerty :D

I just see that FQStereotype contains what i want, but its only available from version 12.1 onwards and my in my work we are using v.12.0.1207.

There is any other way to obtain that?

Automation Interface, Add-Ins and Tools / Obtain MDG from stereotype
« on: June 28, 2017, 01:05:48 am »

There is a way of reading the stereotype of an element, get its MDG.
For example, I want to know if a collection of elements are Archimate, BPMN or other type elements.


I want to obtain programmatically some information about the version control, for example the url, or the type (SCC, CSV, subversion or TFS) etc.

There's a simple way to do this with the automation interface? I only see the package functions but any of them returns information about the version control.

Hi! Thanks for your suggestions.

Unfortunately, the company I work for only use EAv12, so we resolved this problem doing an addin and using the EA_OnPostNewElement event to edit the activityType for the elements we want.

Greetings  ;D

General Board / Re: Extending built in stereotypes in a profile (BPMN)
« on: April 28, 2017, 10:44:51 pm »
Hi!, I'm here again and I still have the problem. I'll try to give more information about it:

I need to create a custom BPMN 2.0 Sub-Process element, but EA define this elements changing the "activityType" Tagged Value on a Activity element.

I tried to include the "activityType" property on my new elements, but instead overwrite the property, the elements get 2 activityType properties one of the of the task type and the other with Sub-Process type. This later gives problems in other processes.

So, is there any way to assign a value to an inherited property an the in the MDG file? I really need that the custom elements that extend from BPMN 2.0 Activity be Sub-Process type.

General Board / Re: Export extended BPMN2.0 elements
« on: April 19, 2017, 06:47:46 pm »
Well, that was the problem, I had the 1.0 and 1.1. versions active.
I think I'll do a little addin to change the custom stereotypes to base bpmn 2.0 ones before exporting the models and restoring them after that.

Thanks ^^

General Board / Re: Export extended BPMN2.0 elements
« on: April 19, 2017, 05:07:09 pm »
Yes, but I am selecting the BPMN2.0 stereotype , why is 1.0 being applied instead? And ow can I do to the 2.0 be applied?

General Board / Re: Export extended BPMN2.0 elements
« on: April 18, 2017, 07:20:04 pm »
I should like to broach this subject again, is there any way to export at least the base elements from where custom elements are extended?

I tried to delete custom stereotypes, and then export the diagram, but when I put again the base stereotype, the element does not return to its original state.

Standard bpmn pool elelementSame element, after delete stereotype and put it again

General Board / Re: Extending built in stereotypes in a profile (BPMN)
« on: April 04, 2017, 04:44:13 pm »
This is the same that I posted before but the v13 guide instead the v12.1  :-[

But how can I redefine my new activity to be a subProcess Activity?

General Board / Extending built in stereotypes in a profile (BPMN)
« on: April 04, 2017, 12:49:08 am »

I'm working with BPMN and I have to create some new elements. I know how to do this thanks to this guide

For example:

But some of the new elements have to extend form some built in stereotypes, like a subProcess Task. For that I have to extend form BPMN2.0::Activity and indicate that this activity have the subProcess type. How can I do that?


Is there any way for launch an addin from other addin, for example clicking a button?


Hi qwerty,

I'm not sure I have understood you. I don't want to replace any element, and if i had to replace some, put the new one in the old place won't solve anything, wasn't it?

Also I tried some test like:
Code: [Select]
            Collection elements = thePackage.Elements;
            Element groupingElement;
            groupingElement = elements.AddNew("Grouptest", "Archimate2::ArchiMate_Grouping");

            Element test;
            Collection groupElements = groupingElement.Elements;
            test = groupElements.AddNew("test", "Archimate2::ArchiMate_Node");

            EA.DiagramObject dObject = diagram.DiagramObjects.AddNew(groupingElement.Name, "Archimate2::ArchiMate_Grouping");
            dObject.ElementID = groupingElement.ElementID;

            dObject = diagram.DiagramObjects.AddNew(test.Name, "Archimate2::ArchiMate_Node");
            dObject.ElementID = test.ElementID;


Create first the grouping element, create the test element directly into grouping element and then create the diagram objects, but still doesn't work.


I'm trying to create programmatically some archimate elements into an ArchiMate_Grouping element. I'm doing that replacing the parentID of the element for the elementID of the grouping element.
In the Project Browser, the elements appears into the grouping element, but this is not reflected in the diagram.

How can I represent this in the diagram?

PD: I have tried to create the DiagramObjects before and after replacing the parentID.

I solved my problem, I would have something wrong in the MDG, so I redo it from the beginning and now all works.

Pages: [1] 2 3