Recent Posts

21

General Board / Hierarchical BDDs

« Last post by jas11 on February 11, 2026, 11:29:47 pm »

For a nested BDD hierarchy, how can I split the modelling across different BDDs? For example, for the following model:

Code: [Select]

-----------------------------------------
|                 B1 (block)            |
-----------------------------------------
       |              |            |
     ------        ------       ------
     | B2 |        | B3 |       | B4 |
     ------        ------       ------
       |
------  ------
|B2.1|  |B2.2|
------  ------

I can in EA create the project hierarchy as shown below:

Code: [Select]

System Package
   System BDD
   B1
   B2
      B2 BDD
      B2.1
      B2.2
   B3
   B4

For the System BDD, I can add just the B1, B2, B3 and B4 blocks, and not show that B2 further comprises B2.1 and B2.2 since I want to defer that level of detail to another diagram. So if I wanted to show this at the B2 BDD level, I wouldn’t be allowed to add B2 since I would be trying to add the block to its own BDD.

Is there any way around this?

22

Automation Interface, Add-Ins and Tools / Re: Eliminating an inherited connection metamodel when specializing an MDG

« Last post by adepreter on February 11, 2026, 07:44:02 pm »

Thank you.
Indeed full control is always better.
Is the Sparx version of the ArchiMate MDG QEA available to boost partners' productivity and Sparx sales ?

23

Automation Interface, Add-Ins and Tools / Re: Eliminating an inherited connection metamodel when specializing an MDG

« Last post by Geert Bellekens on February 11, 2026, 06:14:53 pm »

For some client's I've completely rebuilt the ArchiMate profile to suit their specific needs.

That is a bit of work, but it allows full control of which relations are allowed or not.

Geert

24

Automation Interface, Add-Ins and Tools / Re: Eliminating an inherited connection metamodel when specializing an MDG

« Last post by Eve on February 11, 2026, 08:20:56 am »

I think the only option is to override each allowed relationship.

25

Automation Interface, Add-Ins and Tools / Eliminating an inherited connection metamodel when specializing an MDG

« Last post by adepreter on February 11, 2026, 03:54:46 am »

Hello, Does anyone know how to eliminate inherited connection metamodels?

Context: In a custom MDG, we redefine most stereotypes that exist in another MDG.

Question: How to avoid that the redefined element stereotypes inherit the related connections metamodel ?

For example:
- In the ArchiMate MDG, there is a built-in Assignment meta-connection from Application Component to Application Function.
- In a custom MDG that redefines Application Component and Application Function, how to AVOID that the Assignment (and all other meta-connections) gets inherited ?

26

Automation Interface, Add-Ins and Tools / Re: JavaScript to convert an element to an ArchiMate data object

« Last post by Modesto Vega on February 10, 2026, 09:59:36 pm »

Thank you Eve and Geert, scripts corrected, including adding the right value to stereotypeEx.

27

Automation Interface, Add-Ins and Tools / Re: JavaScript to convert an element to an ArchiMate data object

« Last post by Eve on February 09, 2026, 05:00:03 pm »

1. element.Stereotype = "ArchiMate3::DataObject";

Attempts to assign a stereotype with the name "ArchiMate3::DataObject" to the object. If it is not already defined it will attempt to define it as a global stereotype. It's less bad if you don't include a profile. As an example, if you specified ArchiMate_DataObject it may assign ArchiMate2::ArchiMate_DataObject or ArchiMate3::ArchiMate_DataObject. Think of it as "I don't care where the stereotype comes from, as long as it has this name".

2. element.StereotypeEx = "ArchiMate3::DataObject";

Attempts to assign the stereotype "DataObject" from the profile "ArchiMate3" to the object. As Geert said, this won't be found because no such stereotype exists in that profile. If you replace it with "ArchiMate3::ArchiMate_DataObject" It will still fail if the element is not a Class.

3. element.MetaType = "ArchiMate3::DataObject";

Does literally nothing.

4. Repository.AdviseElementChange(element.ElementID);

Effectively updates any places in the UI that have that object.

28

Automation Interface, Add-Ins and Tools / Re: JavaScript to convert an element to an ArchiMate data object

« Last post by Geert Bellekens on February 07, 2026, 06:39:27 pm »

You need to set the stereotypeEx to the correct fully qualified stereotype, and call update() to save it.

Now the problem is that you fumbled the steretoype.
Ther is no such stereotype as DataObject in the ArchiMate3 profile.

It's ArchiMate3::ArchiMate_DataObject

The easiest way to get the 100% correct stereotype name (casing is important) is to use the metatype objet from the Profile toolbox.
There you can choose to create any existing stereotype, and you'll get the full name as it is known by EA.

Geert

29

Automation Interface, Add-Ins and Tools / Re: JavaScript to convert an element to an ArchiMate data object

« Last post by Modesto Vega on February 06, 2026, 10:57:04 pm »

An update on this.

The modified script has indeed added ArchiMate3::DataObject to the stereotype but it is only visible through the properties dialog. In the properties pane, it is not visible. Furthermore, the Stereotype field is not populated when exporting the data.

30

General Board / Re: Inferring an XSD from and XML - aka reverse engineering a XML file

« Last post by Modesto Vega on February 06, 2026, 10:37:30 pm »

“I see you’ve fixed the issue!” I said.  “No, we turned off the speaker,” came the reply.

It depends on your intent: to fix the issue or the symptom.   

You got me laughing.

It is more about supressing the symptom, not fixing it. Something it is way too common nowadays.

Let's bring this thread back on track.

The schema composer has a Schema Set option always defaulted to Common Information Model (CIM), for both New Schema and New Model Transform. Let's assume that we want to do this properly and create a CIM. Is there anyway to specify the package containing the CIM that Scheme Composer should use. I have used this functionality before but I can no longer find it.

P.S.: I know Geert has a really nice add-in but we may not be able to deploy it to our work laptops.