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 - Simon M

Pages: 1 ... 5 6 [7] 8 9 ... 434
General Board / Re: BPMN Pool and Lane title freeze
« on: September 18, 2018, 06:03:33 pm »
I don't think there is an option for this available.

General Board / Re: Empty tags of a class not shown in diagram
« on: September 18, 2018, 06:02:26 pm »
It was an intentional change. Probably to clear some unnecessary clutter since there is no value there. (Although we have had some discussions here about whether an empty string is a value)

I don't believe there's an option to revert to the previous behavior. If you really want the empty value displayed, maybe you could insert a zero width space?

And don't forget the fill in the metatype on the stereotype. Leaving that blank will also not make the icon appear (for obvious !NOT! reasons :-X)
EA doesn't customize the icon based on a stereotype. It customizes it based on a metatype. (Not that saying that explains why)

Bugs and Issues / Re: Bizarre bug in QuickLinker!
« on: September 17, 2018, 11:52:40 am »
It's completely new, and doesn't generate anything that earlier versions know to look for.

In terms of backwards compatibility, it will override an existing quicklinker table if one exists. (If you have a metamodel only stereotypes not mentioned in the metamodel will be taken from the quicklink table.) So your technology can include both.

General Board / Re: Named default value constraints
« on: September 17, 2018, 09:18:17 am »
Looks similar to the primary keys and uniqueness constraints etc that are modeled using a separate stereotyped operation.

General Board / Re: Create read-only tag in an UML profile
« on: September 17, 2018, 09:16:18 am »
Predefined Structured Types
Code: [Select]
Used to: Create a read-only constant value.

To include this in a profile, see With Predefined Tag Types.

According to, BABOK is included in Corporate.

(qwerty, it won't be in yours because it was added in v14 and you refuse to update)

No, you can't change the metatypes in a profile.

My only recommendation is to use a template package.

I was talking about the impact such a change would have on the existing tagged values for elements with those stereotypes already applied. You can probably correct that by running a synchronize stereotype though.

General Board / Re: Custom element label in EA with ArchiMate
« on: September 12, 2018, 08:58:01 am »
On a basic shape it looks something like this. (Note, the bold text for a subshape is EA 14.1 only)

Code: [Select]
shape main


shape name
shape body

General Board / Re: Automatically maintain users from AD group
« on: September 11, 2018, 05:38:10 pm »

The bottom two options are what you want. At login it manages group membership etc. I believe there is still local user and group entries required, but it will no longer be used for login.

I'm not sure how it handles deleted users. They should no longer have access to the model, but there may still be a user entry.

Your data modeler deserves a kick in the butt if that is really the reason he refuses to use EA.
That was more or less what I wanted to say. I could understand someone saying they think a tool is too hard to use or doesn't do everything they think it should. But if you're told to use a particular tool anyway, you find a way to make it work. (And that applies even if you're being directed away from Enterprise Architect)

There is a (fairly) new set of events related to editing tagged values:

Unfortunately, they are only relevant for AddinBroadcast tagged values.

But you could use them to force tagged value edits to go through your addin.

Bugs and Issues / Re: Use of @Element in QuickLinker
« on: September 11, 2018, 01:19:42 pm »
As I said, @Element in the source won't work for implementation reasons, not necessarily conceptual ones. EA needs the source type to be a concrete term.

The metamodel method for specifying relationships does allow it, but it works by expanding the three metatypes involved before feeding information to the quicklinker.


My users are doing modelling Archimate Business Processes and linking them to Archimate Business Objects. The use
- Business Process
- Business Object
- Flow
- Some of my own Stereotypes extending standard Archimate elements.

They don't need any of the other Archimate element/connector types, and I don't even want them to.

Sounds like exactly what the view definitions are for. See Custom Metamodel Diagram View

  • Create a "view specification" in a new profile.
Create an "Extension" connector to one or more ArchiMate diagram types. As described in that link, open the desired diagram and enter the following into a Javascript scripting console to get the fully qualified name: ?GetCurrentDiagram().MetaType
Add "Exposes" connectors to the types you want to display. Use the metaclass item in the toolbox to select the profile items you want included. (Quick way to create abstract stereotypes with the fully qualified names needed)
Include this profile in your technology in the UML profiles section[/li]

Users can then select this view under the the diagram types extended in the second step. The result is that the toolbox and quicklinker are filtered to the types you specified. You can also optionally filter the diagram to those types even if something else was added for any reason.

Pages: 1 ... 5 6 [7] 8 9 ... 434