Messages

1

Bugs and Issues / Re: States do not allow to “Select Composite Diagrams” anymore once a classifier is

« on: September 30, 2025, 09:43:02 am »

Thank you for your reply, now I understand the situation.

There is a difference by the steps:
create a State, then create a Statemachine, and then
- specify the StateMachine as a type for the State
- specify the StateMachine's child diagram for the child diagram for the State, then specify the type

In both cases, we can move the child diagram of the StateMachine by double-clicking the State. However, in only the latter case can we see the 'link' mark and the 'eye' icon to view the diagram.

This might be a bug because we can move the 'child' diagram in both cases (i.e., the state is linked to the diagram), but there is no linking mark in the former case.

2

Bugs and Issues / Re: Parts, Properties,… do not allow to “Select Composite Diagrams” on Sysml IBD’s.

« on: September 30, 2025, 09:05:20 am »

If I understand correctly, now we can specify the 'child' (or linked) diagram for the Classifier (in the UML world). So we cannot specify the child diagram for Parts (Part Properties), and we cannot specify it for States which are classified (typed) by a StateMachine. I think this is reasonable.

Aside from this, in the actual modelling, we want to show the IBDs from Parts which are typed by Blocks. Currently we need to jump to the typing Block and then go to the IBD of the Block. This is troublesome, we need to do many steps to check the related IBD.

So I have added a feature to show the IBD of the typed Block for the SysML Parts in my free SysML add-in. My SysML add-in contains lots of useful and mandetory features for real MBSE modelling.　I don't know whether that feature should be included as a standard feature.

3

PCS Bugs and Issues / Re: warning WebConfig version after upgrade PCS

« on: September 30, 2025, 08:28:30 am »

Hello,

The error shows because the internal version information of the WebEA was not updated when releasing the current version.

In the globals.php file, you can find the following version information at the top of the file.

   define('g_csWebEAVersion',    '6.1.166.3060');
   define('g_csOSLCVersion',    '6.1.166.3060');

Changing the version such as above, the error will not be shown any more.

HTH,

4

Bugs and Issues / Re: States do not allow to “Select Composite Diagrams” anymore once a classifier is

« on: September 26, 2025, 06:39:25 pm »

Hello PeterHeintz,

Thank you for your reply. However, there are still some uncertainties.

State elements must be classified by State Machine elements. When we create a new State Machine element, a child StateMachine diagram is always created. Therefore, I don't believe we need to manually link the state to any diagram. I think it is reasonable that we cannot change the linked diagram from the classifier's (in this case StateMachine's) diagram to another.

Maybe I misunderstand something...

5

Bugs and Issues / Re: Parts, Properties,… do not allow to “Select Composite Diagrams” on Sysml IBD’s.

« on: September 26, 2025, 09:05:29 am »

Just FYI, my free SysML add-in can create a link to the typed Block child diagram.
i.e., when a Property is typed by a Block and the Block has a child diagram, we can move from the Property to the child diagram by adding a link with my free SysML add-in.

HTH,

6

Bugs and Issues / Re: States do not allow to “Select Composite Diagrams” anymore once a classifier is

« on: September 26, 2025, 09:02:51 am »

If I understand correctly, the 'Select Composite Diagrams' is not necessary because we can open the child diagram by double-clicking the state.

To create a state which is related to another State Machine:
- drag a State Machine element from the Browser onto a diagram and select 'Invocation (State)'  - or -
- right click an existing State element and select 'Advanced' | 'Instance Classifier' and then select a target State Machine

In either case, we can move to the related StateMachine diagram by the double-click. I do not think we need to specify or change the child diagram to another.

7

Suggestions and Requests / Re: Right-click to open diagram link in a new tab

« on: September 19, 2025, 09:03:59 am »

Hello Mikael,

If you create the Navigation Cells, you can select to open at the same tab or at a new tab by right-clicking the Navigation Cell | Open.

HTH,

8

Bugs and Issues / Re: 'Search for' in Summary window - where is search site list specified

« on: September 18, 2025, 08:48:45 am »

Hi,

You can find the definition xml file at Config\searchProviders.xml under the installed directory.

HTH,

9

Automation Interface, Add-Ins and Tools / Re: Enterprise Architect and AI

« on: September 18, 2025, 08:21:59 am »

Does it mean, that a) other repository types were (only) not tested, but the software 'should' work for them, OR b) it probably will fail for other repositories (e.g. some SQL queries utilized, which may be syntactically invalid on other RDBMSs)?

The answer is a), I think it should work fine with other types of repository. But I use some SQL Select statements in the Add-in to get the information faster. So if you would face any problem, please report it to me. I will check it ASAP.

10

Automation Interface, Add-Ins and Tools / Re: SaveDiagram performance V17.1 compared to V16.1

« on: September 03, 2025, 08:57:30 am »

Hi OJB,

I guess that the new snapshot feature might cause the delay. The feature saves diagram image for every saving attempt. If you enable the automatic snapshot creation feature, EA will save the image to the project. Even if not, EA generates the image of the diagram (and stores it in the memory) so it might take some time to create the image.

HTH,

11

General Board / Re: Not being able to type a FlowProperty with a Signal

« on: August 21, 2025, 08:55:34 am »

Just FYI,

With my free SysML add-in, we can create a FlowProperty with a Signal by dragging a Signal in the Browser onto an InterfaceBlock on a diagram. We do not need to have two (or more) steps to define an InterfaceBlock for a Signal.
https://www.sparxsystems.jp/en/SysML/

HTH,

12

Automation Interface, Add-Ins and Tools / Re: Enterprise Architect and AI

« on: August 18, 2025, 03:38:45 pm »

Hi Shimon,

Thank you for your reply. I am glad to hear that it works well with the latest installer.

As you guessed, currently some limited types and the profile-based types (such as ArchiMate) are supported. Please read the description of the tool to know which types are supported. This is because currently I think it is not easy for the LLMs to specify the correct Enterprise Architect element types. (For example, 'UseCase' is okay but 'Use Case' is NG).

About the Sequence diagrams, currently the MCP server supports exporting information from Sequence diagrams, to be able to generate source codes etc. from the Sequece diagrams. The server exports information about fragments too, so now I think it is enough to generate source codes from the diagrams.
Unfortunately, currently generating the Sequence diagrams are not supported, this is very difficult.

I have checked that the MCP server and Claude/ChatGPT on VSCode can generate source codes from the Sequence, StateMachine and Activity diagrams.

p.s.
Please send me the error information directly. I am the only one interested in the details.

13

Bugs and Issues / Re: Is there any chance to get baselining and comparison to work after somany years?

« on: August 14, 2025, 08:24:38 am »

The 'Visibility' in the Properties window of Enterprise Architect is stored in the t_object.Scope column internally, so this is not a bug.

The problem is that EA shows the internal column name in the Comparison view. It should be shown as 'Visibility,' the same as in the user interface.

14

Automation Interface, Add-Ins and Tools / Re: Enterprise Architect and AI

« on: August 12, 2025, 05:58:44 pm »

Hi Shimon,

I have changed the way to find the Enterprise Architect installed path in the x86 installer and uploaded it as version 1.9.4.1.
Please check if it works fine.

15

Automation Interface, Add-Ins and Tools / Re: Enterprise Architect and AI

« on: August 12, 2025, 05:37:25 pm »

Hi Shimon,

Thank you for your comment! I'm glad to hear that.

As I mentioned in my email direct to you, these installers seem to be fine. The file size does not mean that the MCP_EA_x86.msi is not an x86 installer.
If you try running the MCP_EA_x64.msi on a 32-bit Windows system, it will not work. However, the MCP_EA_x86.msi works well on 32-bit Windows.
(I have double-checked with the current files.)

Perhaps the problem lies in the way the installer finds the installed directory. The installer tries to find the EA installation directory. Perhaps your machine has information about the 64-bit version of Enterprise Architect. If there is information about the 64-bit version of Enterprise Architect, even if it has already been uninstalled, the installer tries to install the directory.

I will try to change the way the installer finds the installed directory.