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 - adepreter

Pages: [1] 2 3 ... 11
Thank you Geert!

Very useful!

And you answered at 7:30 in the morning on a public holiday :-)

Automation Interface, Add-Ins and Tools / Import/Export Working set?
« on: June 01, 2020, 02:59:39 am »
Does anybody know how to export and import working sets?
Or, as an alternative, do you know where this data is stored?

I can't find this in "Export reference data"
Nor in AppData
Nor in the registry

So I guess in must be somewhere in the database?

Thank you

Thank you Geert and UFE.
Yes I tried the _HideUMLLinks. But it does no work for hiding ArchiMate links.

So what's the point of having a stereotype specialization capability ...
Well, I will then keep my set of ArchiMate elements and connectors with all icons and shape scripts so I don't have to drag the built-in ArchiMate metamodel with it... which I don't (re)define using a metamodeling language as it quickly becomes unreadable.

For the work I am doing at least, I find (generated) QL CSVs much simpler and more convenient than (generated) meta-constraints.


Today , in a custom MDG including a Quick Linkers CSV, I redefined all built-in ArchiMate elements and connectors by
using the technique so called "Create Stereotypes Extending non-UML Objects" (

But when I do that my restricted Quick Linkers CSV is ignored and I get all possible default quick linkers instead based on the connectors available in the toolbox.

Does anybody knows how to disable this default EA behavior that shows plenty of ArchiMate quick linkers notably based on the connectors available in the toolbox?
(I don't want the quick linkers to be constrained by the toolbox)

@Eve: I hope you don't mean to solve the problem by removing the feature from the user guide?

This useful feature should simply work as described in the documentation!!

About: Hide Default Quick Linker Settings

Unfortunately, as described at the end of the:
"Note that this technique does not affect the automatic appearance of 'Dependency', 'Trace', 'Information Flow' and 'Help' options on the Quick Linker menu"

When shall we have this fixed? (We have been asking that for years)

General Board / Re: Best practices for modeling of ETL chain?
« on: April 04, 2020, 10:14:32 pm »
Indeed you cannot do this with AchiMate. You need a language that can manage levels of detail.

In Labnaf, you can model your ETL chains of DBs like this: "Application Interaction Details" viewpoint.

In order to manage complexity and to enable zoom in/out, it is important to keep two levels of details.
  • Level 1: Application to Application, ignoring the integration system in the middle. These applications are used as APM entries and for dashboards. They carry application attributes.
  • Level 2: Component/Data Store to Component/Data Store. Here you do model the integration system


I installed Pro Cloud Server and let the WebEA images be generated.

As a result my master repository is now 9 times larger than it was before.

The problem is that I need to distribute replicas of this database.

Any idea how to remove the Pro Cloud Server content?

Thank you

General Board / Re: Making EA friendly for new users
« on: April 01, 2020, 06:01:49 am »
If you want to make sure all the concepts, guidelines, are interrelated, zoomable etc... you can model these.


Thank you Geert and Uffe

Tagged values can reference elements (RefGUID or ReGuidList).

Is it possible somehow to define a tagged value referencing a package?

@Eve: About "The option you describe is effectively what we have".

I checked... and indeed I can see that in the last version (Build 1527), the quick linker column "Exclusive to ST Filter +" is now properly interpreted as described here:

Since we automatically generate this value to TRUE, it now works as documented.

Thank you :)

I am not sure this should start from a technical discussion.

We all have our habits. EA was born when "UML Profile" was the ubiquitous religion.

If we step back a little bit, when we define a new domain specific language we do not care about UML.
There is no reason why we should inherit anything from UML.
The fact that, using EA, we create domain specific languages as UML profiles is "un accident de l'histoire" as we say in french.

So by default these UML specific relationships should not be present.
You might have a configuration option to inherit these relationships from UML.
And you would use that only in the case where you would create a language that semantically extends UML.

Btw UML itself can be seen as a domain specific language for modeling software systems.

General Board / Re: Making EA friendly for new users
« on: March 23, 2020, 03:25:16 am »
Hello Ian,
Here are some resources for "Making EA friendly for new users".

These documents are not specific to Labnaf. They explain how Labnaf does it and how you can further customize.


There is also this earlier article called " Tailoring and Deploying a Sparx Enterprise Architect Configuration

To make it REALLY simple you can use Labnaf itself:
   1) When Labnaf Lite (free version for average size projects) gets installed, it automatically simplifies the EA user interface for Strategy & Architecture work. It also provides an adequate workspace layout
   2) If you want further customization, see also the video on the Labnaf Channel: "How to Customize the Labnaf Language and Metamodel" (in a few clicks):
To learn what Labnaf is about, watch this video:

Pages: [1] 2 3 ... 11