Book a Demo

Author Topic: Feature Linked Notes don't cascade  (Read 3494 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Feature Linked Notes don't cascade
« on: December 09, 2009, 04:38:42 pm »
If you link a note to another note and use "Link this note to an Element Feature..." EA copies the current state of the Feature (such as, in this case, the Note Notes column) into the Notes column of the Linked Note.

If you change the origin note, the rendered note will change, but the column value does not.

If you then link a new note to the second (linked) note, you will get the (incorrect) value of the second note column.   The linkages won't cascade.

They should.  If there is an initial copy (which is a dubious concept for a linked note) then it's EA's responsibility to maintain that copy correctly.


Steps:
(see above)

Why do I need Notes linked to Notes?  Well it turns out that if you copy a diagram Note from one diagram to another, the internal texts is NOT maintained.  Since I want to have one place of definition of some information, I thought I'd use the Feature Linked Note to achieve (and it could be argued, the more correct mechanism) effectively the same outcome.  Didn't work - since if I update the origin (in this case diagram Notes) the linked note doesn't update.

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

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Feature Linked Notes don't cascade
« Reply #1 on: December 09, 2009, 05:53:03 pm »
Could this not be solved by making notes, constraints etc... first class citizens in EA model?
If we could see the notes in the project browser, and could (really) reuse a note or a constraint on several diagrams that could already solve a lot of issues.

Ofcourse if we allow even more elements to be shown in the project browser we should have a nifty feature to filter the elements shown in that project browser. Otherwise it would quickly become overcrowded.

Geert

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Feature Linked Notes don't cascade
« Reply #2 on: December 10, 2009, 12:51:01 am »
Quote
Could this not be solved by making notes, constraints etc... first class citizens in EA model?
[size=18]...[/size]
Not in this case, Geert.  This is a coding/design bug pure and simple.

As you know, I support making all elements first class citizens, but I don't think that would help here.

The bug is about the cascading of Feature Linked Notes explicitly.  It doesn't apply to non-linked Notes.

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

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Feature Linked Notes don't cascade
« Reply #3 on: December 10, 2009, 01:00:27 am »
Sure, but would you still have the need to use the "linked notes linked to linked notes" feature if you can just reuse notes...

Geert

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Feature Linked Notes don't cascade
« Reply #4 on: December 10, 2009, 09:52:47 am »
Quote
Sure, but would you still have the need to use the "linked notes linked to linked notes" feature if you can just reuse notes...

Geert
Well, now that I've tried it I think I might... :)  

For example one could conceive of different tagged values containing different parts of a narrative and making them (selectively) visible elsewhere - for example with different stereotypes providing different renderings.  You could maintain them all in one place, but display them where required.

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