Recent Posts

31

Bugs and Issues / Doc gen IDBs generating properties

« Last post by andrew.francis on November 28, 2025, 02:22:21 am »

I have an issue where disabled 'Show Compartments' settings fail to apply consistently during Doc Gen.

When I generate a document with multiple Internal Block Diagrams (IBDs), the 'properties' compartment is being wrongly added to about half of them in the outputted document, corrupting the diagram layouts.

I'm hoping there's a simple configuration fix I've overlooked.

Edit:
1. I have created a Test document, with just the misfiring diagrams on it (added the 'Model Document' elements and used the same template), and they export correctly to the generated document - which makes me think the problem is configuration of the 'Model Document' block rather than the Diagram - wrong.
2. I have deleted and re-added the misfiring 'Model Document' elements, and the problem persists.
3. I have checked all the configuration settings I can find for the firing diagrams against the misfiring diagrams and can find no differences.
4. I have tried enabling and disabling all available Compartments from the 'Show Compartments' option on the diagram - interestingly the 'Properties' compartment was not an option

Edit 2 - and fix:
1. I wanted to recreate the diagram to see if that helped, and when I created another IBD in the same package as the misfiring IBD, the misfiring IBD suddenly updated itself to show the compartments that I had disabled (including in the options). I was then able to disable the compartments and save, and the subsequent doc gen did not include the misfire. Shame I have about 50 IBDs to recreate and save.
2. The fix works by just creating another IBD and then dropping the Elements onto it, this updates the bad diagrams.

32

General Board / Re: Modelica Library integration with EA/SysML/SysPhS

« Last post by fishy on November 28, 2025, 02:00:37 am »

An update on what I'm learning by experimentation:
Analogues of the Modelica block structures need to be set up in EA:   Blocks, contianing properties to represent Modelica parameters, and ports.

• For blocks, stereotype them as ModelicaBlock and set the ModelicaBlock.Name property to the full classpath of the Modelica element you want to 'wrap'.   For example:  Modelica.Fluids.Pipes.StaticPipe for a block that calculates flow through a pipe
• For properties, stereotype them as ModelicaParameter.   Use the ModelicaParameter.Name property to match the name of the parameter instance within the Modelica block - for example length or diameter as constant properties of the pipe.   That allows you to set a completely arbitrary name as the SysML parameter name if you want to - e.g. use d for diameter, or L for length.   If you don't use ModelicaParameter.Name, or don't apply the ModelicaParameter stereotyope, then the SysML name field must match the Modelica instance name exactly.
• For ports, similar to parameters, use ModelicaPort and ModelicaPort.Name to match the interface name used by the Modelica block - e.g. port_a or port_b on a pipe.

One clear problem arises, which I can't see a workaround for:  If you stereotype a propery as both ModelicaParameter and PhSVariable, the SysMLSimConfiguration ignores this, and lists the property as a PhSConstant.   This means that the property then isn't available to choose as a plottable value, and as a consequence I can't see a way to extract varibles calculated by Modelica (e.g. flow through a pipe, or water level in a tank) and plot it from EA.

Another clear problem is the setting of typed Modelica properties via SysML parameters - e.g. specifying a Medium used in a flow calculation, such as water.   There isn't any easy way to do this as Modelica requires you to redeclare types that don't match the base class that a block is expecting.   For example, Modelica.Fluid.Vessels.OpenTank expects a Medium of type Modelica.Media.Interfaces.PartialMedum.   But the modelica object Modelica.Media.Water.StandardWater isn't of this type.   Setting Medium = 'redeclare package Medium = Modelica.Media.Water.StandardWater' as the EA initial value doesn't work - you still get the error:

Error: component tank1 contains the definition of a partial class Medium. (Expression: Modelica.Fluid.Vessels.OpenTank tank1(T_ambient=20,crossArea=1,height=3,p_ambient=101325) annotation(Documentation(info = ""), Placement(visible = true, transformation( origin = {-357, 30}, extent = {{0, 0}, { 152, 141}})));  ")"
Please redeclare it to any package compatible with Modelica.Media.Interfaces.PartialMedium.

33

Automation Interface, Add-Ins and Tools / Re: ArchiMate Grouping and Alternatives

« Last post by Modesto Vega on November 25, 2025, 11:18:25 pm »

Since we gave away the notion of the browser indicating any form of holonymy, we basically haven’t had that problem.  Only items that require referential nesting are nested.

The issue that I have always faced with Sparx EA, specially with enterprise level or multi-project repositories, is that I have never managed to dispel the notion, for me and some of my colleagues, of the browser not indicating a semantic relationship between the whole and the part, irrespective of whether there is referential nesting or not. The browser looks like a folder structure, is used like a folder structure, and it is way too easy to create a very deep folder structure.

All other items are in a "flat" structure (by type).  The diagrams are in a separate branch of the repository and can be structured however you like.  Consequently, we don't have as much of a problem as you do.

I have used Sparx EA, like that, but it is very cumbersome and leads to duplication. This is because when creating an element from a diagram Sparx EA always places the element in the package containing the diagram. As a result, we switched to having elements and diagrams of a similar type in dedicated packages but this still does not solve the duplication problem.

Ideally, I would like to restrict the use of the browser to advanced users and use views for most people contributing to a model. Of course, it does not help the way Sparx Systems has implemented views, including the capability of creating (non-dynamic) views under the root node. TBH, I have never understood what views are and how they work, other than another way of referring to a folder.

34

General Board / Re: Importing stereotype extending PackagingComponent via CSV

« Last post by Modesto Vega on November 25, 2025, 10:54:19 pm »

Hi Mauricio,

The PackingComponent is one of those elements I have previously described in the forum as having a dual personality - i.e., it is an element but it also a package. It exists twice in the repositories.

With previous version of Sparx EA (v13 to v16), we tried using it as a component, or to be more specific as a way to model an Information System Service or a complex application. We gave up because of a combination of issues importing and exporting data and limitations on how this element is rendered by Sparx EA when used in diagrams.

35

General Board / all-Option in visible timeframe is not available

« Last post by BKG_EA-User on November 25, 2025, 12:15:10 am »

Hello,
just a little question:
Does anyone know how to make the "all" option in the visible timeframe-Menu in Discuss & Review History available? In the Discuss & Review for the elements this option is available. Does it depends on my user role?
Thanks and best regards, Juliane.

36

General Board / Re: Level Numbering Inactive

« Last post by Esperan on November 24, 2025, 10:00:38 pm »

Dear all,

I am new to EA and currently setting up my first project. In the tryouts I was able to activate level numbering in the specifcation manager. For some reason it is now not possible to activate it. I have tryed also other (old) files and also there it seems to be deactivated.

Anybody has an idea why it is deactivated and where to reactivate it?
The same question!
Thanks,
SafEAty

37

Bugs and Issues / Re: v17.1 - Extended character issue with Name field in Properties window

« Last post by Geert Bellekens on November 24, 2025, 06:50:21 pm »

Did you notice the 32-bit - 64-bit difference also?

No, didn't test that one.

Geert

38

Bugs and Issues / Re: v17.1 - Extended character issue with Name field in Properties window

« Last post by Paolo F Cantoni on November 24, 2025, 10:05:14 am »

I can confirm this behavior in v17, but also in v15.2.1560

Geert

Thanks, Geert,
I rechecked my v15.2.1560, and I must have waved a magic wand because this morning it also behaves as the others.
Did you notice the 32-bit - 64-bit difference also?

Paolo

39

Bugs and Issues / Re: v17.1 - Extended character issue with Name field in Properties window

« Last post by Geert Bellekens on November 24, 2025, 04:05:43 am »

I can confirm this behavior in v17, but also in v15.2.1560

Geert

40

General Board / Re: How can an activity invoke a behavior defined in a subclass of its own class?

« Last post by ea1122 on November 24, 2025, 03:54:30 am »

OK, I see my error.