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 - Paolo F Cantoni

Pages: 1 ... 5 6 [7] 8 9 ... 403
Bugs and Issues / Re: v14 Beta: Technologies dialog crashing
« on: March 08, 2018, 04:25:18 pm »
Seems to have been related to the Missing MDG topic.  Resolving that, seems to have resolved the crashing.

See v14 Beta: Missing MDG


Bugs and Issues / Re: v14 Beta: Missing MDG
« on: March 08, 2018, 03:31:26 pm »
Thanks, Simon,

editing the t_genopt table did the trick as mentioned by Zvolensky.  However, we normally access EA repositories via MS Acces Linked Tables.  MS Access refused to allow us to edit the rows.  Had to go to SQL Server Management Studio to edit the rows.  Not clear why MS Access had trouble.


PS: Also seems to have resolved the MDG enable/disable crashing topic.  See v14 Beta: Technologies dialog crashing

Bugs and Issues / v14 Beta: Advanced>Save as Profile... Missing
« on: March 08, 2018, 02:40:12 pm »
The Diagram context menu option:
Advanced>Save as Profile...
is Missing.

I can't "Save as Profile" like I used to be able to.

Anyone confirm this?

General Board / Re: EA v14 Beta - how to re-use your old layouts
« on: March 08, 2018, 01:42:28 pm »
It didn't quite come in correctly, but it SURE beats setting them up from scratch!
Obviously, the developers believe that the problems with doing that are worse than recreating them.
Well, it's not obvious (what the developers believe).  We only have the observable behaviour.

But I understand the risk-averse decision.  That's why I posted. 

The forum members (presumably NOT the majority of users) can take the calculated risk.


Bugs and Issues / v14 Beta: Technologies dialog crashing
« on: March 08, 2018, 01:22:02 pm »
Enabling/disabling technologies in the technologies window causes crashes.

Anyone else seeing this?


Bugs and Issues / v14 Beta: Missing MDG
« on: March 08, 2018, 01:19:17 pm »
Trying to open our production repository (SQL Server) I get:
Access to this model requires the following technologies which are not available:

Which MDG is this message referring to?


General Board / EA v14 Beta - how to re-use your old layouts
« on: March 08, 2018, 12:25:30 pm »
We went to a LOT of trouble to set up specific window layouts for our various configurations.

In the upgrade from 12->13, we just copied our old layouts to the new directory ...\AppData\Roaming\Sparx Systems\EA\Workspace Layouts13 and off we went.

When we tried to do the same with v14: ...\AppData\Roaming\Sparx Systems\EA\EA1405Workspace-Layouts
we found the file format was not supported!  ::)

However, replacing the Sparx Systems Registry Exporter xx.x.xxxx with Sparx Systems Registry Exporter 14.0.1400
allowed us to at least import the layout.  It didn't quite come in correctly, but it SURE beats setting them up from scratch!

Saving the imported layout seems to work fine!


PS: Perhaps Sparx could allow import with a warning?  ;)

When a class has two associations with the same association name, only one of them will show up in the schema composer.

Steps to Reproduce:
- Create class A, B and C
- Add an association from A to B with name "test"
- Add an association from A to C with name "test"
- Create a new schema composer schema
- drag class A into the schema
- notice that only one (random) association with name "test" will show up with no warning at all.
- remove the names from the associations
- notice that now both associations are visible in the schema composer


That's 'cos they're the same relationship!   (only kidding!  ;) ;) )  But the behaviour you describe is merely a defect.

The determination of semantic equivalence is non-trivial (as we discovered when we wrote our consolidator) - it's not rocket science, but it is not straightforward.


General Board / Re: Replica conflict resolution help
« on: March 07, 2018, 10:37:54 am »
I thought this advice would be like carrying owls to Athens (German proverb).
Wear thick gloves?

The patron god of Athens is Athena, and Athena's sacred animal is an owl.

LOL thanks. I actually looked up the proverb after posting and it appears that low denomination silver coins in ancient Athens had a picture of an owl on one side. Carrying silver coins to Athens, where they were in plentiful supply, would be redundant and not worth the effort. It would be like carrying... *looks at Australian 5 cent coin* ... echidnas to Australia.
Or "Coals to Newcastle" - which is true for both the UK and Australian cities...

Oh, and even in these days of gender neutrality, Athena was a Goddess, not a God.  ;)


Yes you can certainly do all that via an MDG with shape scripts and add tag values for extra attributes. Its also alright to represent the elements of ArchiMate with other symbols/images to cater to the audience. Marc Lankhorst mentions that in his book Enterprise Architecture at Work. I always represent the ArchiMate elements with graphics when showing the executives but use the default shapes when communicating with fellow architects.

I did find extending ArchiMate MDG with another MDG worked but I didn't have complete control so I eventually ended up creating ArchiMate symbols via shapescripts myself and removing the dependency on the ArchiMate MDG supplied by Sparx EA.
As did we...


Good idea  :)


I've reported it.

In a number of places, EA uses the results from an EA Search to do additional things.  For example, the Relationship Matrix.  In an enterprise environment, the same object may have multiple names/identifiers.  We have developed a multi-naming technology that relies on a "trick" to get around the fact that EA only allows at most two names (the Name and Alias).  The trick allows us to place a user selected name for an element on a specific diagram.  However, these additional names aren't available to the rest of EA.

It occurs to me that if we extended the CLASSGUID and CLASSTYPE tokens which provide specific functionality out of the searches, to include CLASSNAME and thus provide the "designated" name to be used, it would be very useful.  The search query would determine what value to supply as CLASSNAME (as it does for the other two tokens).


I tried it a while ago with the tagged values that had been defined on the classifier of an instance, but that didn't work either.
EA shows those tagged values in the GUI, but they are actually defined on another object, so I sort of expected it not to work.

(my emphasis)

That's because you (like me) are too used to EAUI.  Conceptually, it should work - ESPECIALLY if they are on the GUI.  Otherwise, why show them?  Similarly with Specialization/Generalization.

Balu, report a bug (for both situations)


Automation Interface, Add-Ins and Tools / Re: Importing Archi Models
« on: March 01, 2018, 10:40:47 am »
I think both tools supposedly support the Archimate Exchange Format, but the results I had with this import were erratic at best.

Thanks, Geeert,

I was sure it was possible, but I couldn't find it...  Turns out we have all but our MDGs switched off and it is only active if the ArchiMate 3.0 MDG is enabled. (Reasonable enough).

For the simple models we have here seems good enough.


Just a note: be careful when adding relations (even trace relations) to a model that will be used to generate XSD's.
I've seen it slow down the generation process considerably (something like 20 minutes instead of 40 seconds)

For some reason it seems to first see the relations at a certain level, decide to ignore them, and then start over again from the beginning, to see the relations at the next level, decide to ignore them, and .... you get the picture. ;D

One of the reasons we're writing our own generator.   ;)
It will do exactly what we need and hook into our own MDG.


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