Recent Posts

Pages: 1 ... 6 7 [8] 9 10
General Board / More 'natural' curved connectors ?
« Last post by matthew.james on September 21, 2018, 03:53:51 pm »
All the connector line styles in Sparx are straight lines, apart from Bezier. Any tips on how to make the Bezier style lines more 'natural'?

I find that I can get a reasonably natural looking balanced curve for any given connector quite easily, but they don't survive well when diagram layout is changed. If you move one or both of the connected elements you often end up with a distorted, unbalanced curve that looks quite unattractive - can be manually fixed (but, manual). Often the connector ends seem to act like they're pinned (even thought they're not) and you end up with weird loopy lines coming out of the far side of the element and lines crossing over unnecessarily, almost like they want to twist around each other.

Note: I am using Archimate_Flow connectors, based on ControlFlow type, both of which have the same issues observed above. And no, I don't know whether curved lines are allowed / precluded / accepted or otherwise approved for use according to the Archimate standard.

Bugs and Issues / Space Horizontal Bug ?
« Last post by matthew.james on September 21, 2018, 02:23:27 pm »
I have encountered a strange bug (?) with the "Space Horizontal" function where (sometimes) rather than spacing out the selected elements, it instead spaces out most of the elements (usually all except one) and just shifts the remaining element(s) into the range, overlapping others that have been spaced out. It appears that if the elements are re-ordered then the alignment will work (with that ordering).

For example, if the are 5 elements (A,B,C,D,E), roughly spaced and in alphabetical order, select them all and click 'space horizontally' and (under this buggy behavior) you may get 4 of them spaced out (A,B,C,D) but the 5th (E) moved to be somewhere between the 1st and 4th and overlapping other elements. This happens consistently with any re-arrangement of the elements whilst that are kept in that same order. If instead you re-order to put the errant element inside the order (eg A,B,C,E,D) then the space horizontal will work correctly, ie all elements spaced out and in the same order (A,B,C,E,D)

I can't determine the circumstances when this happens, but once it does (with a given set of elements) it seems to always happen - so feels like there is some property of the element(s) at play.

Further to this:
- Space vertically exhibits the same behaviour (with the same set of elements)
- Put the same elements on a different / new diagram preserves the behaviour
- Copying the elements (paste as new) fixes the behaviour and the new elements align as expected

Has anyone seen anything similar Any explanations / workarounds?
I think sometimes the extension to the metaclass is still needed to make things work.

I recently created a abstract stereotype specializing ArchiMate_BusinessObject.
Then I added concrete sub-stereotypes.

With that setup but the toolbox profile helper didn't work.
I could select my stereotype, but the toolbox item was not added (no error message, simply nothing happened).
This was solved by adding the extension to the metaclass Class (as was mandatory in a previous version)

I have not found any adverse effects of the extra extension to Class.

(all of this in version 14.1.1426)

General Board / How can we surface the scenarios (for an element) onto a diagram?
« Last post by Paolo F Cantoni on September 21, 2018, 10:47:53 am »
How can we surface the scenarios (for an element) onto a diagram?  I was expecting a compartment (similar to Requirements and Constraints) but no such luck.

We can use a Linked Note, but this is quite cumbersome and is not directly attached to the element.

General Board / Re: Keystore Service system requirements
« Last post by Aaron B on September 21, 2018, 10:06:51 am »
No idea, sorry. I wouldn't expect any problems with this version of Windows. I'd suggest installing it anyway to give it a go. If you do encounter any problems, please contact support and we'll look into it.
Yes, I have an extension to the base «metaclass» Component because that's what an E.A. consultant told me to do.
In the mdg_technologies.pdf p.28, the note says: If you are adding any of the Metaclass element Attributes to your stereotype, or if you want to use the Profile Helper to create a toolbox profile, your stereotype Class must extend a metaclass as well as specialize a stereotype.

That PDF is out of date, and so is your consultant.

I ran through your steps.

Step 1:
- Created new Stereotype LBC_ArchiMate_ApplicationComponent. I add a tag value attribute to differentiate from parent class.
- Component is correctly instantiated but the stereotype in properties is empty.
In the properties dialog, the tagged value will be in a separate page with the name of your profile. In the docked tagged values window you'll see it under <profilename>::LBC_ArchiMate_ApplicationComponent

Step 2:
- Add «redefines» stereotype to Generalization Relationship establish in step 1
- Component is correctly instantiated but the stereotype in properties is empty.
Now the tagged value should show up under ArchiMate3 in the dialog. In the docked window it shows up under ArchiMate3::ArchiMate_ApplicationComponent.

I can't see anything wrong with this behavior. As an added bonus, if you set your technology as Active in the manage technologies dialog. Any time you create an Application Component, it will use your stereotype instead of the one from ArchiMate 3.

Step 3:
- Add «metaclass»Component
- Establish Extension Relationship from LBC_ArchiMate_ApplicationComponent to Component
- toolbox has now the folder icone. If I drad&drop on the diagram, I'm asked to select between ApplicationComponent and ApplicationComponent  ::).
- I've tried with both and same result: Components are correctly instantiated including the stereotype that now has the «LBC_ArchiMate_ApplicationComponent» value
As I said, that will cause the behavior. Take my advice instead of some random "E.A. consultant". Not only is it not necessary in the current version of EA, it breaks things.
Bugs and Issues / Re: DAO.Recordset Errors after File Transfer from EAP to EAPX
« Last post by Paolo F Cantoni on September 21, 2018, 09:28:14 am »
That's probably not an EA bug, I guess?

I DID send in a defect that the final compress should be part of the project transfer functionality, but I guess that was fixed in a different timeline (binge-watching Continuum on Netflix).

General Board / Re: Keystore Service system requirements
« Last post by carl_stevenson on September 21, 2018, 08:43:48 am »
Thanks for the reply. Do you know if there are any plans to officially support it on Windows Server 2016?
Automation Interface, Add-Ins and Tools / Re: SQL Update on Notes with Carriage Returns
« Last post by qwerty on September 21, 2018, 06:09:04 am »
Just a guess: EA uses a proprietary format for notes. IIRC it's partially HTML. Try changing the CR to an &-format or try using the Repository.GetFieldFromFormat to convert the text first.

Bugs and Issues / Re: Database RE - game breaking bug - need workaround
« Last post by Geert Bellekens on September 21, 2018, 02:07:05 am »
Yes it is definitely possible to fix it using a small script. I saw a topic in the last few weeks related to that.
I think it also included some details about how to properly create table in EA (and not classes with «table» stereotype)

Pages: 1 ... 6 7 [8] 9 10