Book a Demo

Recent Posts

Pages: 1 ... 3 4 [5] 6 7 ... 10
41
Automation Interface, Add-Ins and Tools / Aris software import
« Last post by Typia on October 09, 2026, 12:16:26 am »
Hi,
We currently have diagrams modeled in Aris.
Is there a way to import those diagrams in EA ?
We have xml format + DTD

Many thanks.
42
Automation Interface, Add-Ins and Tools / Re: C4 Modeling
« Last post by philchudley on October 08, 2026, 11:46:28 pm »
One method that I know of is:

1. Place the MDG file on a network drive that everyone can access
2. Then everyone's EA will require the following setting performed once only:
    a) Select Manage Technology from the Settings Toolbar
    b) In the pop-up dialog select Advanced... This displays a dialog where you can specify the path to the file set in 1. above

When EA loads the C4 MDG will be loaded along with all other MDGs

Each user will have to add the C4 MDG to their current active perspective.

There maybe other methods, but this is the one I have used in the past.

Phil

43
Automation Interface, Add-Ins and Tools / Re: C4 Modeling
« Last post by Typia on October 08, 2026, 11:37:55 pm »
Thanks a lot, I got it.
is there any way to package it so it can be deployed automatically ? we're in a multi user environment.
44
Automation Interface, Add-Ins and Tools / Re: C4 Modeling
« Last post by philchudley on October 08, 2026, 09:34:11 pm »
45
Automation Interface, Add-Ins and Tools / C4 Modeling
« Last post by Typia on October 08, 2026, 09:20:40 pm »
Hi,
is there any official MDG for C4 ?
I can't find it on registered downloads ?

Many thanks,
Best regards
46
General Board / Re: Why aren't diagrams included in Update Status?
« Last post by miksko on October 08, 2026, 06:22:30 pm »
Thanks! I will forward your suggestion.

Mikael
47
My concern is that most users have custom addins, EA scripts or 3rd party scripts which often use the Repository.Execute method for the reasons I gave. Decomissioning this will generate a lot of issues and claims, with no workaround to provide due to the API limitations:
Then you need to apologize to your users for providing them with an addin/workflow that relies on unsupported API functions.

I created a Model-Based Add-in for one of my clients which automatically adds legend (or legends) to diagrams that require them. This is a massive productivity aid to them and apart from saving time it also ensures all diagrams are consistent across all models.

So how does Repository.Execute() feature.
Same for you. You wrote an add-in for your client that relied on unsupported functionality. No-one else did that.

I have the feeling that Sparx Systems is looking at this whole security feature in a different way.
This has nothing to do with EA's security function. This is a change to prevent Enterprise Architect itself from being considered a security threat and therefore being completely banned completely from the networks of all sorts of large organizations. It's not about protecting your EA models. It's about not being the security flaw in your network that a bad actor can use to influence anything they shouldn't be allowed to.

For me it would be a perfectly acceptable solution to allow Repository.Execute in these conditions:
Frankly, unless you can convince the rest of the world that "the whole security vulnerabilities scare" isn't relevant or just doesn't apply to Enterprise Architect then it doesn't matter. We live in a world with bad actors of all sorts. It took a while, but it was inevitable that Enterprise Architect would eventually be looked at in that light. Once that happened our choice becomes to "fix" the vulnerabilities or to accept that nowhere that has any kind of security policy for their network would be about to use Enterprise Architect at all.

I don't need Sparx Systems to child-proof my EA models. I'm prefectly capably to assess the risk myself, and to allow it where appropriate.
Maybe you can assess the risk to EA models, but maybe not to organizations.

Here's a list of things I use Repository.Execute() for.

- updating the code of internal scripts (EA-Matic)
The very first thing is a violation of EA's existing security model.
48
This is the list of use cases I've sent to Sparx support

Here's a list of things I use Repository.Execute() for.

- updating the code of internal scripts (EA-Matic)
- Updating the ActionKind of an Action (t_xref)
- Updating the PDATA(x) fields on elements, connectors, diagrams etc.. (MiscData is read-only and can only be used to read the data)
- Adding, and removing Workingsets
- Merging elements (replacing all the references to an element with references to another element). Here it's purely a question of performance.The API is so slow that it would take ages to do this using the API. Using an SQL Update query is at least 100 times faster for these types of bulk updates.
- Modifying the contents of Schema composer schema's or creating new schema's
- Updating user preferences in usys_system
- Automatically removing all userlocks at shutdown (removing them would be possible with the API, but again extemely slow. Getting the current user's locks would be impossible with the new restrictions in SQLQuery)
- Bulk updates to the model (e.g. removing old tagged values after an MDG update) Again, mostly a performance issue.
- updating the details of diagram legends (t_xref)
- updating elementID of a diagramObject
- updating user group permissions (in this case it was to remove all permissions for all groups except the administrators group)
- solving the problem when users had done "checkoutOffLine" by accident and then updated the (DBMS) repo (updating packageflags)

We use Repository.SQLQuery() on the  the security tables for the following use cases
- Getting a list of all the locks a user currently has
- Knowing if a user is part of a certain security group
- Getting the user name and firstname that currently has a lock on an element
- Getting a list of all users currently defined in the model
- Checking if the contents of a package(branch) is completely locked by the current user.
- Checking the RequireLock property in t_secpolicies

Geert
49
I have the feeling that Sparx Systems is looking at this whole security feature in a different way.

For me the security feature is a feature to protect bonafide good actor users from themselves.
I think it was never intended to protect the model from some bad actors that are trying to "hack" into the model.

What is the threat we are protecting the models from? Users using backdoor tools to give themselves rights to... edit models???

But, with the whole security vulnerabilities scare, this viewpoint seems to have shifted.

For me it would be a perfectly acceptable solution to allow Repository.Execute in these conditions:

1. In case no security is setup, allow it always
2. In case security is setup, allow it with a new permission (that can be set to false by default)

That would make it a concious decision by the model admin to allow this feature or not, and for whom.

I don't need Sparx Systems to child-proof my EA models. I'm prefectly capably to assess the risk myself, and to allow it where appropriate.

Geert
50
Agreed!

I created a Model-Based Add-in for one of my clients which automatically adds legend (or legends) to diagrams that require them. This is a massive productivity aid to them and apart from saving time it also ensures all diagrams are consistent across all models.

So how does Repository.Execute() feature.

Well, there is no API function to create a Legend. Therefore it is all performed in the script. Involving, writing a an entry into that well known cross-reference table t_xref.
Repository.Execute() is required to insert a row per legend.

Yes, I did perform extensive research to ascertain exactly what is required in the t_xref row, so as not to corrupt anything.

For me, the only work arounds would be:

  • Inform the client to revert to manual addition of legends
  • Wait for a Create Diagram Legend function to be added to the API, along with most likely a Legend Class

Until then I believe they will not be upgrading to EA v17.2

Phil
Pages: 1 ... 3 4 [5] 6 7 ... 10