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.

Topics - Geert Bellekens

Pages: 1 [2] 3 4 ... 15
Automation Interface, Add-Ins and Tools / Zipping MDZip files
« on: May 10, 2017, 03:30:27 pm »

A client of mine is going through the process of migrating their Magicdraw models to Enterprise Architect.
Because of some issues in transferring the models we wanted to unzip the mdzip files, change the xmi contents, and then rezip them in order to import them into EA.

But for some reason that doesn't seems to work. Even without changing anything to the contents, just unzipping and rezipping the file and then trying to import it into EA we get "analyzing mdzip file" for a few seconds and then it stops.
I'm suspecting that we are using the wrong zip settings to rezip the file.

Does anyone know which settings we should use to produce a valid mdzip file that can be imported into Enterprise Architect?



The UMM/UPCC3 method uses inheritance to assemble enumerations.
One enumeration could inherit from different other enumerations with the intention of combining the values of all the parent enumerations.
The problem is that currently the Schema Composer doesn't allow the selection of those "inherited" enumeration literals. As a workaround we have to copy all the values down to the assembled enumerations, but that is error prone and not according to the UN/CEFACT recommendations.
Please allow inherited enumeration literals to be selected in the schema composer exactly like we can do with inherited attributes.



(Feature request sent)

I'm working on a document that should be printed in either dutch or English. We store the English name in the name, and the Dutch name in the Alias.
The problem is that the Dutch name is not always filled in. In those cases I should print the English name.

Does anyone have a bright idea on how to do that?
With the Start/End bookmarks I can hide something when not filled in, but I cannot do the opposite, show something else if a field is not filled in.

The only solution I see at the moment is to go completely SQL or Script, but I'd rather avoid that.
A feature like 'Use Alias if Available' for reports would be ideal.




Does anyone has a shapescript example of how to make an attributes compartment, pretty much the same as in regular UML classes?

I checked my library, and the examples in the help, but I couldn't locate such an example.



Bugs and Issues / {Diagram.Figure} not working anymore in v13 RTF templates
« on: February 16, 2017, 07:55:49 pm »
I just noticed that my existing templates have a problem when generating a report in version 13.0.1309
Instead of sequence number of the diagram I get the text "Diagram Sequence" when I use the field {Diagram.Figure}
These templates work perfectly fine in v12.1.1230

Reported as a bug.


General Board / UN/CEFACT Message Composer tutorial
« on: February 11, 2017, 01:24:12 am »

Recently EA claims to support the UN/CEFACT standard to create message definitions.
I searched the help, and found some bits and pieces, but I can't seem to find a good tutorial or example that shows me the steps I'm supposed to take to go from model to message.

I'm sure there is a specific way this is supposed to be used, I just can't find an explanation.

Does anyone know a tutorial or kind of explanation on how this feature is intended to be used?



I'm extending one of the yellow stereotypes of Archimate 2 (Business Object) and that all works out fine, except for the fact that my new stereotype has the standard fill color (beige) while original Archimate element is yellow.
I'm wondering how the Archimate elements get their yellow color.
It's not defined in their shapescript (I checked) so it must be somewhere else, but I have to clue where.

I can ofcourse add the yellow fillcolor in the shapescript, but I would rather do it like Archimate does.

Anyone here who knows the secret sauce to make this work?


PS. I tried drawParentShape() but that didn't make any difference (it must have done that already because it otherwise looks exactly like an Archimate Business Object, except for the color that is)

Bugs and Issues / Issues with RTF document generation in v13
« on: January 13, 2017, 01:53:59 am »
- {Diagram.Figure} is not working anymore. Instead of outputting a number is show the literal text "Diagram Sequence". The same templates work just fine in v12.0.1230
- I cannot delete styles anymore in v13. The button who used to be there in v12 is not there anymore in v13
- The styles dropdown lists the styles in a non-determined order. this was bad already in v12 (lowercase styles vs upperase styles), but now is has become a total nightmare

Bug(s) reported


Bugs and Issues / Breaking change in API in v13
« on: October 11, 2016, 05:26:58 pm »
There is a breaking change in the API since v 12.1.
The types EA.SchemaType and EA.SchemaProperty now have property Guid and no longer the property GUID.
Please try to avoid these kind of breaking changes, and especially is they have no added  value at all.



Reported as bug to Sparx.

If you have multiple associations to different entities that all have the same name (e.g. "has") then the schema composer will only show one of those associations.
This is of course problematic as I need to be able to select some of those associations for my schema.

The schema composer should show every association, even if they have the same name.

Reported to Sparx


I had a situation where I had some RTF docgen templates, some linked document templates (that eventually where supposed to end up in the document as well) and a stylesheet that was used for both.
All of these things were nicely packages in an MDG and distributed that way to the production environment.

When I tested this on my development machine it all worked perfectly fine. The numbering of the RTF template parts, and the numbering of the linked document nicely continued (because they use the same style defined in the same stylesheet)

Big was my surprise that this DID NOT work on production. The numbering of the linked document sections didn't continue in the RTF sections. (so I had two time section 1, two times section 2, etc...)
I even tried to update the styles on my linked document to set them to my (MDG) stylesheet, but the MDG stylesheet wasn't even listed as an option.

This was solved simply copying my MDG stylesheet as a regular stylesheet on the production model. Then suddenly it all worked fine and the numbering in the final documents was OK.
But of course now I have the stylesheet twice in my model, once in the MDG, and once as a copy in the regular resources.

So please make sure that Linked Documents can use stylesheets imported as part of an MDG.

I'll report it as an official bug as well.


General Board / Model Transfer from Cloud server
« on: August 31, 2016, 12:54:57 pm »

Yesterday I had a client who installed EA with the cloud service because of their internal security policies.
(they don't allow direct database access from clients to a database server)
After a bit of messing around we got it working with an SQL server as backend, connecting over the cloud service.

Then I wanted to show them how to do regular backups to .eap files using the model transfer feature (as we do in "normal" installation) but I came to the conclusion that I didn't have the option to transfer from cloud to .eap file, only from a direct database connection, which is not allowed in that organisation.

So does anyone know a workaround for this kind of situation? For now they can still use xmi export/import, but that will soon become a way too slow process as their model grows.


General Board / Mapping tool in EA -> who wants it?
« on: August 26, 2016, 05:46:50 pm »
Hi everyone,

I'm thinking about developing a mapping tool add-in for EA.
The idea is that you can manage a mapping between two types of (data) models. For example between your logical data model and your message model, or between your logical data model and your database model etc...

I already have a number of add-ins and scripts that somehow create traceability between models on element, attribute and association level, but I don't have a tool yet to visualize and manage those traces.

To give you an idea the GUI of the thing could look similar to this:

Functions could include
- ability to add notes to each mapping
- ability to export the mapping to excel
- drag-n-drop to create mappings

Now it seems to me like there could be many parties interested in such a tool.
I would like to develop this as a free and open source add-in (as I do for all my add-ins) but I'm still looking for sponsors.
My initial rough estimate for the development of such a tool is 15 man days.

I already have two parties that might be interested, but the more sponsors I can find the lower the price would get for each individual party.

So if you are interested in such a tool please let me know:


We wanted to set a default notes template on a BPMN business process so I naturally suggested to use the project template package.

But this doesn't seem to work for BPMN business processes. No matter what I put in the notes of the element in the project template package, my notes on a new BPMN business process are always empty.
It works for any other element I have tested, but apparently not for BPMN things.

Grr.. now I have to build a workaround for something that should be standard behavior.

Reported to Sparx


Automation Interface, Add-Ins and Tools / SetFixedRegion crashes EA?
« on: July 09, 2016, 03:53:59 pm »
I must be doing something wrong.
I'm trying to replicate the behavior of the standard requirements that have a left border block that only sizes vertically, but stays the same width.

I thought I might use the SetFixedRegion() command to get that effect, but when I try it EA crashes hard getting the processor up to 100%
And this is repeated every time EA tries to execute the shape script.

Anyone know how to use the SetFixedRegion() correctly?

Here the shapescript that makes EA crash. Removing the SetFixedRegion fixes the crash.

Code: [Select]
shape main
 layouttype = "leftright";
 h_align = "left";
 v_align = "center";
shape borderBlock
shape nameCompartment
h_align = "center";
v_align = "center";
editablefield = "name";
shape S
//left vertical line
//bottom arc
//top arc
//right vertical

Pages: 1 [2] 3 4 ... 15