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 [2] 3 4 ... 426
Bugs and Issues / Re: EA Cloud Connection Problems with https over IIS
« on: August 07, 2018, 09:10:23 am »
Make sure you've followed the instructions at

In particular, you need to define the request for sparxcloudlink.sseap to be the isapi/http module. Generally you want to enable it even if it doesn't correspond to a file or directory. You also need to configure the dll to forward to the cloud service itself, but if that was your problem you wouldn't be getting a 404.

It needs to be in a stereotype profile.

Suggestions and Requests / Re: Diagrams with callapsable elements
« on: August 03, 2018, 08:45:45 am »
Yes, it would be nice.

Exactly how it would work, particularly regarding other elements on the diagram is where it becomes difficult.

Repository Class - LoadAddins  - Loads all Add-Ins from a repository when Enterprise Architect is opened from automation.

Bugs and Issues / Re: EA14: Font sizes - random ... ?
« on: July 31, 2018, 09:22:58 am »
Your email to support gave the reason for why the archimate elements are different. The default font size is actually 8.5. So the one that you changed to a different size and then selected 8 will be smaller.

ArchiMate3 Business Interface sets the abstract property on creation, so that explains the italics.

Bugs and Issues / Re: EA14: Font sizes - random ... ?
« on: July 30, 2018, 10:33:27 am »
The bottom two are rendered using a bold font. There's an option to use a bold font for names in EA options. The top two won't use that option (because anything shapescripted can't.)

The bottom left one also appears to be indicating that it's abstract.

The other option is that the font can be changed in both the default appearance and the diagram local appearance. I don't know which you've used, but it's possible that there is a value from the other impacting things.

a) Does that mean the example JScripts will be ported to JavaScript in future versions of Sparx EA?
It doesn't mean that. They could be at some point.

Unless I'm mistaken, the only 'Local Scripts' installed by EA that it matters for are the two 'Model Search' scripts. Converting those should be a matter of replacing ActiveXObject with COMObject. (see the help)

b) Does Sparx Systems recommend a JavaScript Debugger to use with EA?
EA includes a built-in debugger for Javascript that is not dependent on external components.

Of the scripting languages used in EA, I would recommend Javascript. Mainly because Microsoft no longer supports the script debugger used by EA for the other two.

If you're interested in writing add-ins, any .Net language will probably get you going the fastest. C# is probably the most popular of those.

No. Unfortunately, parsing existing javascript and creating a class model from it is problematic, even if the code is object oriented.

It sounds like either you have created a decoration script or you are calling drawparentshape().

Replace left join with inner join.

Bugs and Issues / Re: Problem upgrading from EA13.5 to EA14
« on: July 24, 2018, 09:07:07 am »
I suspect that it has something to do with the desktop version

The Desktop edition no longer exists. Contact sales for a free* upgrade to the professional edition.

* Provided you have a current support agreement.

Suggestions and Requests / Re: Archimate connector stereotype labels
« on: July 13, 2018, 03:12:34 pm »
To be clear - I'm after the Archimate relationship stereotype to be displayed, not anything related to UML types or stereotypes.  For example to have a connector display (optionally, controlled by the existing property) a text label "<<ArchiMate_Access>>", or even better "<<Access>>" to match the toolbox text.

I take your point that Archimate is a new language, although I can't see anything that precludes relationships from being labelled with stereotypes (the Archimate stereotypes). In fact the language explicitly includes the ability to specialize the base (Archimate) element and relationship types and explicitly specifies the use of the UML style guillemet notation for this.
Exactly, those correspond to a UML stereotype on the base UML element representing the connector. It's not something that you would actually want to display on an ArchiMate diagram. If you were using the same notation to describe a specialized form of Access connector, it would make sense to display that like a stereotype.

I don't see how this would impact any users of Archimate negatively - assuming it would be controlled by the existing 'show stereotype labels' diagram property.  With that property turned off the behaviour would be the same as it currently is. However I also take your point that it is unlikely that this will be changed if I raise a feature request (ie I shouldn't waste my time doing that).
Because by default all existing diagrams are set to show stereotypes. That means your change would show those labels on every ArchiMate diagram. Existing users would say that we've broken their diagrams. New users would throw away EA before ever finding the option.

But feel free to submit a request. I'm just one person.

General Board / Re: Need Help TLS1.2
« on: July 13, 2018, 09:49:21 am »
Not yet.

Microsoft has only recently updated the OLE driver for SQL Server databases with support for this, and it's incompatible with the previous driver.

Both EA and the Cloud Server are being updated to allow the new driver. Question though, are you really connecting to your SQL Server database over an insecure network that requires TLS to be used?

Suggestions and Requests / Re: Archimate connector stereotype labels
« on: July 13, 2018, 09:45:07 am »
The ArchiMate technology defines a new language. Yes, it uses stereotypes to define that language, but displaying them would be non-conformant for the target language.

I'm not sure I understand why you want them displayed, but I wouldn't expect any change. Displaying UML stereotypes on ArchiMate connectors based on that option would negatively impact the majority of ArchiMate users.

Pages: 1 [2] 3 4 ... 426