Recent Posts

Pages: [1] 2 3 ... 10
Hi, welcome to the forums and thank-you for your thanks.

If you hold the Shift key while selecting an object in the Palette it will remain selected (this is mentioned in the user guide page 25).

As for mapping keys to the palette elements, I'm afraid this is not possible.

This is my first post on this forum, so first of all, I would like to thank you for the wonderful work you are doing. Archimate tool is really impressive.

I would like to ask if there is a way (key shortcut or some setting) to keep the most recent artifact/element from the palette active?

When I create diagrams/views I often draw one type of element many times
e.g. many business process boxes, then I am connecting them with a single type relation
Each time I need to click the proper element again in the palette.

If it is not currently possible, could you please consider this as feature request:
1. Add a parameter to keep the last element from the palette active
2. Add a key shortcut to make the most recent tool active again
3. Add key shortcut mapping in the parameters to the palette elements (e.g. Ctrl-1 = Bussines Process, Ctrl-2 Flow relation etc.)
General Archi Discussion / Re: Showing the differences between two models
« Last post by lemoux on May 06, 2021, 10:23:08 AM »

I found this topic while searching a solution for my use case.
We aim to have several architects working on a same model.
The model is mainly divided in two folders : cartography & studies.
Cartography corresponds - somehow - to our knowledge database about the existing information system.
While studies correspond to new projects and evolutions which rely on the cartography (typically by reusing some elements).

Using coArchi plugin and a git instance, people can create a branch for their study. When time comes to merge the work back into the master branch, one needs to look for and check any change in the cartography.

Compare two versions of the cartography folder and subfolders is a tedious work that needs to be automated as much as possible.

For anyone interested, the attached script - to be used with the jArchi plugin - generates some kind of checksum file for a selected folder content.

Executing this script on both versions of the cartography or any other folder results in two files that can be compared using any diff / merge tool.

The comparison makes it possible to find :
- Any element name or documentation changes
- Element or relationship removals
- Additions to diagrams

It will - however - not point out pure graphical changes (ex. an element slightly moved in a diagram).

The file content is basically an ordered list of diagrams and their elements.
Each line contains the element name, its type and a UUID.
The UUID generation is simply based on the concatenation of the element name and its documentation.

This solution is good enough to cover my need and - maybe - useful to anybody else.

Kind regards,

General Archi Discussion / Re: Nesting elements in the model
« Last post by jonnydab on May 04, 2021, 05:03:16 AM »
Hi Xiaoqi

Thanks for the reply and recommendation. I thought that would be the solution. Folders are a little redundant and would be useful to obscure child elements within the parent, but this will suffice.

General Archi Discussion / Re: Views vs Viewpoints?!
« Last post by tsanov on May 03, 2021, 17:53:29 PM »
Hello everyone,

As far as I am concerned, there are two great advantages specific to Archi's "tooling mechanism implementation" as per Phil's question:

I have a genuine question. Why do people need to have a tooling mechanism to impose the constraints of viewpoints? Isn't it enough to describe the viewpoint and its concerns and constraints say in the View's documentation field, or in a note? If you are the modeller then you must already know this stuff. If sharing the model then surely the documentation field would suffice? And what if you change your mind?

1. "Learning/comprehension aid": in Archi the view points bring user experience which I personally spontaneously associate with a "filter" and to me this is a much better analogy than "the place we are looking from".

2. It's an automation and improves our quality of life. It's like the spell checker in any word processor ...

General Archi Discussion / Re: Nesting elements in the model
« Last post by xiaoqi on May 02, 2021, 20:04:24 PM »
Hello Jonny,

As JB mentioned, this is the working approach that we're using in day to day basis of maintaining the Business Capability model, actually you can keep breaking down to further level.

And the nesting relationship (e.g. compose) can be created in the Capability Model view, in which you can place Level 1 capabilities into respective Level 0 parent capability.

Good luck,
General Archi Discussion / Re: Nesting elements in the model
« Last post by Jean-Baptiste Sarrodie on April 30, 2021, 07:52:10 AM »

This is not possible in Archi because parent-child relatioin is in fact a native relationship in ArchiMate (composition), and thus appears in the relationships folder.

But you can create sub-folders anywhere in the model tree, so you can create a "capability 1" folder and move other capabilities inside. You'll then have to decide whether "capability 1" capability is inside this folder or not.


General Archi Discussion / Nesting elements in the model
« Last post by jonnydab on April 30, 2021, 07:22:54 AM »
Wondering if it's possible to nest related elements underneath each other i.e parent child many EA catalogues have a parent-child relationship for example data, capabilities. To abstract complexity in the model structure it would be good to be able to place elements underneath each other i.e.

capability 1
  --- capability 1.1
  --- capability 1.2


A viewpoint is not a way to filter concepts in a view but simply a reference to a precisely defined type of view, together with its targetted stakeholders, their concerns and modelling conventions used.

So if you want to filter a view you have to build another view and remove unwanted elements. A script could be useful for that.


Pages: [1] 2 3 ... 10