Book a Demo

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

Pages: [1] 2 3 ... 32
1
As far as I know I cannot insert an image.
I created a ArchiMate3::ArchiMate_Serving realtionship. The mcp server created an association with profile "ArchiMate3". But the checkbox for the stereotype "ArchiMate_Serving" has not been set.

I tested this behavor now for qeax and MariaDB. Stereotype (checkbox) has been set for Elements, but not for connectors.

2
Hi Viking,

I am afraid I still do not quite understand the issue; however, this forum is not the appropriate place to solve individual problems related to a specific add-in. Could you please email me the details, along with an example project or the steps to reproduce the error?

As far as I know I cannot insert an image.

I created a ArchiMate3::ArchiMate_Serving realtionship. The mcp server created an association with profile "ArchiMate3". But the checkbox for the stereotype "ArchiMate_Serving" has not been set.

3
Hello Viking,
I cannot reproduce the issue you mentioned on the latest build. If you use the older builds, please updaate to the latest and try again. If you can still reproduce the issue with the latest build, could you send an email to me for detail with the example mode to reproduce?

No, the stereotypes ar not set for connectors. But the connectors are shown correctly as ArchiMate connectors. I said "add an "ArchiMate3::ArchiMate_Composition" connector between REST API and Microservice.

For elements the stereotypes have been set.

4
Elements are created as intended with Stereotype. But Connectors are not. They are shown correctly, but the attribute Attribute "Stereotype" is empty. Is the issue on my side? I mentioned the profile as required and do not see a chance to do something in addition.

5
This error seems that there was an error between Copilot and GitHub (GH). My add-in never returns an error or requests the Copilot-Vision-Request header. This error maybe relates to Copilot Vision feature, so I cannot help you.

Agreed. It seems more a problem with GitHub and the LLM. I tried several LLMs and one did not throw this exception.

6

Hi Takeshi, I tested v2.3.11. The mcp identifies the linked diagrams now. Many thanks.

But Copilot throws an issue:
' Sorry, your request failed. Please try again.
Copilot Request id: 37d72ba4-1757-43e8-becc-6763ef90ff8d
GH Request Id: 647D:3E781C:528352:5B6037:696F8921
Reason: Request Failed: 400 {"error" : {"message": "missing required Copilot-Vision-Request header for Vision requests","code" :""}} '

With the older version I also got this issue, but it was gone later. Any ideas?

7

Many thanks, Paolo.

There should be at least a possibility to retrieve this information, regardless of the theory behind it.

8

Would a user care, if it is an owned or other referenced diagram? I think, only one or the other can be added to an element. And both are diagrams.

Or just adding composite to get_element_information?

9

Yes, you are right. We we are "just" using Composite Diagrams only, not Composite Structure Diagrams.

But even my agent is confused about this distinction. Copilot using your mcp says, that "Elements with Composite Diagrams: 0". It does not say "Elements with Composite Structure Diagrams: 0".

Can your mcp be extended to also return Composite Diagrams? This feature is part of Enterprise Architect, that's why it should be also supported by your mcp. Our child diagrams cannot be moved into the structure of the parent diagram, because many parent diagrams are using these Composite Diagrams. Otherwise, this restriction would dominate our complete repository and we could not order it accoring our standards.

10
Regard to the following Viking comment, now the latest MCP server can generate better BPMN diagrams including Pools, Lanes, better layout, etc.

Just great !

11
It looks to me like this AI agent does only does the stuff I can easily do myself.

All this can be achieved by just using natural language. Even my grandfather would be able to create a BPMN diagram now.

To make it actually work in a serious modelling environment, it should need to learn and follow the guidelines of the organisation.

You can teach your agent (easily) and the results will quickly improve.

I don't want to rain on your parade, and I'm sure it's really technically a very advanced tool.
But for now I'm not yet able to recommend usage of such a tool to my clients.

I would, I do, we do.

12
Hi Takeshi, the command seems to have a bug. 'get_element_information' always returns 'empty' for 'Owned Diagrams'. Goal is to find out the composite diagram / child diagram of elements.

13
Yes, new elements will no longer be placed on diagrams for various reasons, mainly due to user requests and ideas on how to use this MCP, as well as to improve performance.

We can now place multiple elements at once using the place_element_on_diagram tool. I will update the add-in so that it can create two or more elements at once, saving on AI costs and improving performance.

Sorry, I don't understand. I can create new elements, but cannot create a diagram using them? Or do you mean that I have to tell the agent in addition, that I want to place the new elements on a diagrams?

14
The version 2.2.0 has been released. I found and fixed some issues during my tests, but there may still be others.

I tested the newest version for my UML Class Diagrams. It now creating elements, connectors, attributes, and cardinalities. Awesome :)

For any reason it does not create the model anymore (empty "diagram" also cretaed, opened, and selected). So, I have to move the elements from the project brwoser to the diagram.

15
The implementation for adding/modifying attributes and operations (including parameters) has been completed...
I think I can release the new installer today or tomorrow.

Great news

Pages: [1] 2 3 ... 32