Author Topic: Importing Archimate Aggregations - they don't look right.  (Read 4592 times)

Ian Mitchell

  • EA User
  • **
  • Posts: 506
  • Karma: +22/-4
  • The eaDocX and Model Expert guy
    • View Profile
Importing Archimate Aggregations - they don't look right.
« on: January 20, 2022, 10:37:04 pm »
I'm importing a load of archicture data, and it all looks fine, except for one tiny detail.
When I create Archimate 'aggregation' connectors, they don't look right in diagrams: they just look like Associations.
I've tried creating one of these connectors manually, and the underlying data looks the same: but manual ones have the little aggregation diamonds which I want.

Diving in the database, I just can't see where the two connectors (generated and manually created) are diferent:
  • Stereotypes are both Archimate_Aggregation, and in the UI, they both show as Archimate3::Archimate_Aggregation
  • Directions both 'Unspecified'
  • Entries in t_xref are both @STEREO;Name=ArchiMate_Aggregation;FQName=ArchiMate3::ArchiMate_Aggregation;@ENDSTEREO; which I guess is why they look the same in the UI 

I tried creating Archimate3::Archimate_Assignment connectors instead, just as a test, and these looked just fine when generated, with the correct Archimate notation.

I'm totally out of ideas as to how to make them look right. Re-doing them maunally is not possible - I have 1000s of them.

Any ideas?

Ian Mitchell, Designer, eaDocX


www.eaDocX.com
www.theartfulmodeller.com

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8607
  • Karma: +257/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Importing Archimate Aggregations - they don't look right.
« Reply #1 on: January 20, 2022, 11:30:14 pm »
Hi Ian,

have you checked that the destination aggregation field is set correctly in the imports?  We converted all our old-style Aggregation and Composition relationships to be based on Associations to line up with modern / best practices and we had to set the aggregation field via automation (SQL queries in our case).

HTH,
Paolo



Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Ian Mitchell

  • EA User
  • **
  • Posts: 506
  • Karma: +22/-4
  • The eaDocX and Model Expert guy
    • View Profile
Re: Importing Archimate Aggregations - they don't look right.
« Reply #2 on: January 21, 2022, 12:40:33 am »
Perfect - I didn't notice the little field called 'SourceIsAggregate', which was 0 for the imported links, but 1 for the 'correct' connector.
Thanks Paolo - life saver!

..that column doesn't look to be accessible via the API, so I guess I'll need some SQl to fix it. Grrrrr
« Last Edit: January 21, 2022, 12:46:10 am by Ian Mitchell »
Ian Mitchell, Designer, eaDocX


www.eaDocX.com
www.theartfulmodeller.com

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13404
  • Karma: +567/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Importing Archimate Aggregations - they don't look right.
« Reply #3 on: January 21, 2022, 03:02:47 am »
It is accessible through the API. It's something like: EA.Connector.ClientEnd.AggregationKind

Set it to 1 or 2 to indicate aggregation/composition

Geert

Ian Mitchell

  • EA User
  • **
  • Posts: 506
  • Karma: +22/-4
  • The eaDocX and Model Expert guy
    • View Profile
Re: Importing Archimate Aggregations - they don't look right.
« Reply #4 on: January 21, 2022, 03:51:17 am »
Thanks Geert!
Ian Mitchell, Designer, eaDocX


www.eaDocX.com
www.theartfulmodeller.com

mhuebsch

  • EA Novice
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Re: Importing Archimate Aggregations - they don't look right.
« Reply #5 on: June 17, 2022, 12:23:09 am »
Ian, would you be willing to share your script? Did you find it necessary to change both ClientEnd and SupplierEnd? I'm finding that Aggregation relationships created under an older version of EA need to be updated.