Book a Demo

Author Topic: Customized Name for Metarelationship in Quicklink  (Read 3579 times)

conan

  • EA User
  • **
  • Posts: 25
  • Karma: +0/-0
    • View Profile
Customized Name for Metarelationship in Quicklink
« on: October 22, 2020, 11:18:31 pm »
Hi,

I could not define a Customized name for a "metarelationship" using new quicklink feature in my MDG. Which was working fine with existing CSV option.

Do we have any solution for it ?

Thanks in advance.

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Customized Name for Metarelationship in Quicklink
« Reply #1 on: October 22, 2020, 11:40:28 pm »
IIR correctly you use a metarelationship to use an existing relation.
That already has a "meaning forwards" and "meaning backwards", so I those will be used.

If you want to define your own you can create your own connector stereotype and use that one instead of the standard relation type.

Geert

conan

  • EA User
  • **
  • Posts: 25
  • Karma: +0/-0
    • View Profile
Re: Customized Name for Metarelationship in Quicklink
« Reply #2 on: October 23, 2020, 10:46:02 pm »
Hi Geert,

Thanks for your reply. If I understand correct.  You mean to say  eg: metaclass Genralization would have two ends,one is generalization and another end specialization. But that an EA's default nature. Am clear with that. Hope you know, the existing csv quick link feature will allows us to just define name for an  UML Association as I like in the csv. But why the new EA quicklink(since 14) feature is not providing me that facility. I do not have any properties or shapes scripts to define, I just a have name for association why do EA forces me to create a stereotype.

Thanks,
Conan

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Customized Name for Metarelationship in Quicklink
« Reply #3 on: October 23, 2020, 11:17:06 pm »
Hi Geert,

Thanks for your reply. If I understand correct.  You mean to say  eg: metaclass Genralization would have two ends,one is generalization and another end specialization. But that an EA's default nature. Am clear with that. Hope you know, the existing csv quick link feature will allows us to just define name for an  UML Association as I like in the csv. But why the new EA quicklink(since 14) feature is not providing me that facility. I do not have any properties or shapes scripts to define, I just a have name for association why do EA forces me to create a stereotype.

Thanks,
Conan
This is possibly a feature that was not implemented in the new way of defining quicklinks.
The old CSV method is still supported though. Personally I'm more than happy to get rid of the old CSV format, even if it means we loose some functionality.

Geert