Book a Demo

Author Topic: Stereotyped InformationItems on Information Flow  (Read 12876 times)

Modesto Vega

  • EA Practitioner
  • ***
  • Posts: 1183
  • Karma: +30/-8
    • View Profile
Stereotyped InformationItems on Information Flow
« on: June 05, 2021, 01:55:06 am »
I have stereotyped the InformationItem using an MDG. Everything works as expected but for something visually very annoying: when adding multiple stereotyped InformationItems to an Information Flow I end up with a very long string with the name of the InformationItem preceded by the MDG stereotype.

Is there a way I can hide the stereotypes to shorten the lengthy string?


The stereotypes are not shown for non-stereotyped InformationItems.
« Last Edit: June 29, 2021, 01:22:58 am by Modesto Vega »

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Stereotyped InformationItems on Information Flow
« Reply #1 on: June 05, 2021, 06:14:58 am »
Add a shape MiddleTopLabel {}. Or use HideLabel("MiddleTopLabel"); which has the same effect.

q.

P.S. Not 100% sure whether it's Bottom or Top. Try both.

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Stereotyped InformationItems on Information Flow
« Reply #2 on: June 05, 2021, 03:48:24 pm »
Add a shape MiddleTopLabel {}. Or use HideLabel("MiddleTopLabel"); which has the same effect.

q.

P.S. Not 100% sure whether it's Bottom or Top. Try both.
Apparently, HideLabel is not recommended anymore.  To hide a label, emit an empty string.

Paolo
« Last Edit: June 05, 2021, 09:36:19 pm by Paolo F Cantoni »
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Stereotyped InformationItems on Information Flow
« Reply #3 on: June 05, 2021, 05:55:30 pm »
Hehe. I don't read release notes (any more). How about ShowLabel which was an absolute nonsense operation from the beginning on? It's still there. Well, doesn't do any harm being a no-op.

q.

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Stereotyped InformationItems on Information Flow
« Reply #4 on: June 05, 2021, 09:36:01 pm »
Hehe. I don't read release notes (anymore). How about ShowLabel which was an absolute nonsense operation from the beginning on? It's still there. Well, doesn't do any harm being a no-op.

q.
This is Sparx, it's not in release notes, Eve told me in a post.

Paolo
« Last Edit: June 16, 2021, 08:22:08 am by Paolo F Cantoni »
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Modesto Vega

  • EA Practitioner
  • ***
  • Posts: 1183
  • Karma: +30/-8
    • View Profile
Re: Stereotyped InformationItems on Information Flow
« Reply #5 on: June 15, 2021, 10:53:39 pm »
Thanks for the replies. So essentially this means I need to make it part of our MDG.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Stereotyped InformationItems on Information Flow
« Reply #6 on: June 16, 2021, 07:02:52 am »
Exactly.

q.

Modesto Vega

  • EA Practitioner
  • ***
  • Posts: 1183
  • Karma: +30/-8
    • View Profile
Re: Stereotyped InformationItems on Information Flow
« Reply #7 on: June 24, 2021, 02:12:13 am »
Is there a way to print the names of the name of the InformationItems linked to the relationship?

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Stereotyped InformationItems on Information Flow
« Reply #8 on: June 24, 2021, 02:16:35 am »
I don't think so. Except you use an add-in to get the information. But I would refrain from using that.

q.

Modesto Vega

  • EA Practitioner
  • ***
  • Posts: 1183
  • Karma: +30/-8
    • View Profile
Re: Stereotyped InformationItems on Information Flow
« Reply #9 on: June 25, 2021, 12:09:50 am »
Thanks Qwerty.

Am I correct to assume that there is no way to list the attributes linked to a relationship using a shape script?

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Stereotyped InformationItems on Information Flow
« Reply #10 on: June 25, 2021, 12:28:05 am »
I'm guessing you are going to need an add-in call for that one as well.

Geert

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Stereotyped InformationItems on Information Flow
« Reply #11 on: June 25, 2021, 05:19:49 am »
What exactly do you mean by "attributes linked to a relationship"? Properties? If so, you can query quite a few of these (it's somewhere in the docs under query methods for shape script or so).

q.

Modesto Vega

  • EA Practitioner
  • ***
  • Posts: 1183
  • Karma: +30/-8
    • View Profile
Re: Stereotyped InformationItems on Information Flow
« Reply #12 on: June 25, 2021, 05:42:54 pm »
Sorry qwerty, I meant "elements related to a relationship".

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Stereotyped InformationItems on Information Flow
« Reply #13 on: June 25, 2021, 06:34:35 pm »
So that's source and target (the two elements a connectors connects). See https://sparxsystems.com/enterprise_architect_user_guide/15.2/modeling/displaying_element_properties.html at the lower end. There are quite some properties you can retrieve.

q.

Modesto Vega

  • EA Practitioner
  • ***
  • Posts: 1183
  • Karma: +30/-8
    • View Profile
Re: Stereotyped InformationItems on Information Flow
« Reply #14 on: June 28, 2021, 10:32:14 pm »
From memory not all elements are related using source and target. Some elements are directly related to a relationship via another relationship. I think this may be the case with the InformationFlow element.