Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
General Board / Re: Importing glossary terms
« Last post by Geert Bellekens on Today at 02:49:41 pm »
I just tried it again to be sure and the import works just fine here.

I'm a bit puzzled as to what could be the cause of the problem here. ???

I'm using EA version 14.1.1427, but that particular piece of code was written in 2013, so it must  be compatible with earlier versions of EA (version 10?)

Geert
22
This sounds like it would be a great feature - freeze a diagram so that it doesn't change layout or add / remove elements and connections. Maybe an extension to the current 'lock' feature but to lock connector visibility as well. When the the diagram is 'unfrozen' there could be an option to add new / missing connectors or not.

I note that this is (or similar) is a repeated request in the forums Does anybody know if this has been raised as a feature request before?
23
Bugs and Issues / Re: How to "Publish Diagram as Pattern"?
« Last post by Simon M on Today at 12:23:13 pm »
24
Bugs and Issues / Re: How to "Publish Diagram as Pattern"?
« Last post by Paolo F Cantoni on Today at 11:45:49 am »
I can't find anywhere in the Help files that refer to the ribbon path that you quote, Paolo. All references are to the correct path that Geert quotes, and the 'Modified Date' field on the text element is at least 6 months ago.  Where did you see the incorrect ribbon path?
User Guide... Publish a Pattern

Note: this is the local copy of the Help file/User Guide (from the v14.1 download area).

Paolo
25
Bugs and Issues / Re: How to "Publish Diagram as Pattern"?
« Last post by RoyC on Today at 11:30:12 am »
I can't find anywhere in the Help files that refers to the ribbon path that you quote, Paolo. All references are to the correct path that Geert quotes, and the 'Modified Date' field on the text element is at least 6 months ago.  Where did you see the incorrect ribbon path?
26
Bugs and Issues / Re: Metamodel Constraints - Meta-Relationship
« Last post by Simon M on Today at 11:19:59 am »
It's likely that Generalize is valid between the two base classes that you are using.

You can also add the attribute _HideUmlLinks=True to your source metaclass element to suppress that. Then you should only get the types you have modeled.
27
What don't you understand?

I modified the ecoSystem profile in the example model to use the constraints, then started writing up the instructions to replicate it. But I don't think it's going to help.

stereotyped relationship is used to specify a specific source/target/connector triple. It's almost the same as a spreadsheet line (but it also can be a reverse entry.) Multiple connectors are used to specify multiple valid targets for that connector type.

metarelation is the same thing. The only difference is that the connector is a UML one instead of a profile one.

You use those when the valid targets depend on what the source is. It's also the simplest when there is only one valid source and target.

To define a quicklinker using metaconstraint, the source will be the connector type. You need at least one umlRole=source and at least one umlRole=target to make it work.

It's simpler to use metaconstraint in this way if there are a number of valid source and target connectors.

That much will get a you a basic quicklinker. But you probably want to add the _MeaningForwards and _MeaningBackwards attributes to the metaclass for your connectors. This will show on the quicklinker and exposes 'reverse' relationship creation.

The other thing to consider is using abstract supertypes for your stereotypes.
28
General Board / Re: Search Diagrams and Elements by UserID
« Last post by i4mdone on Today at 11:11:15 am »
Thank you. The trouble that I am encountering is relating a Diagram or Object to t_secuser table so that I can get the UserID which then I can related to the GroupID. The following works, but the first line I am using String concatenation which seems a bit hackish...but maybe that's the only way.

t_diagram.Author = t_secuser.FirstName + ' ' + t_secuser.Surname AND
t_secuser.UserID = t_secusergroup.UserID AND
t_secusergroup.GroupID = t_secgroup.GroupID AND
t_secgroup.GroupName = '<Search Term>'
29
Bugs and Issues / Re: Metamodel Constraints - Meta-Relationship
« Last post by i4mdone on Today at 11:05:57 am »
If that is true, then what is the purpose of the Meta-Relationship function?

Meaning I thought it meant to establish a "valid" UML Connector between the two Stereotypes. However what happens is that whatever is added with an <exposes> connector is available in the QuickLinker regardless of what I established with the Meta-Relationship connection.

I thought the intention was that only what I have established with the Meta-Relationship would be available in the QuickLinker. In this case I would only expect "Generalization" to show up as a valid UML Connector in the QuickLinker. However if I <expose> other connector types with or without using the Meta-Relationship function they all show up in the QuickLinker.
30
Hi rekelyei1,
We have done this but it is not trivial.
Firstly, your Connector_IDs need to be monotonically increasing (depending on your configuration they may not be).
Consequently, a new connector will have a Connector_ID larger than the current highest Connector_ID on the diagram.
If you can record the highest Connector_ID at a point in time, you can write a script to hide any connector with a Connector_ID greater than the recorded Connector_ID.

We, therefore, "Freeze" a diagram by recording the highest available Connector_ID in the Title Block (Diagram Notes Element) as a Tag.
We regularly (or on demand) run a script to remove the spurious connectors.  If the diagram actually needs to change, the modeller changes the diagram then "Re-Freezes" the diagram.

It's not perfect, but it works well enough to be a popular function on our human maintained (as opposed to automagically maintained) diagrams.

HTH,
Paolo
Pages: 1 2 [3] 4 5 ... 10