Linked Doc marker missing on BPMN activities

[Guillaume]

Hi

Once a linked document is created on any EA element such as a class, use case, etc, a marker ('A' character in red) is displayed on the element to indicate that a linked doc exists.
When using BPMN2, the marker is missing on the activity elements.

Is this a bug?
thanks

[StefanPears]

Sorry, all, for reopening this old issue. I am currently working with EA 12.0 and the problem still exists. If it's a bug I would be pleased if it will be fixed.

[Glassboy]

Sorry, all, for reopening this old issue. I am currently working with EA 12.0 and the problem still exists. If it's a bug I would be pleased if it will be fixed.

I suggest you log a bug report with Sparx.  There's a link in the bugs forum description.

[RoyC]

Also, at the foot of this page there are several columns of links. In the Support column there are links for reporting a bug and for submitting a feature request.

[StefanPears]

done. Let's see what will happen.

[StefanPears]

fyi:

Hi Stefan,
 
Thank you for your note.
 
This behaviour is being investigated and we will provide you with a further response as soon as possible.
Best Regards,

<...>
Sparx Systems Pty Ltd

[StefanPears]

... and this is their answer:

<...>
Unfortunately BPMN Activities do not currently support the display of the Linked Document marker (the red 'A') as you mentioned. I will submit a feature request on your behalf so that this is considered for implementation in a future release.
<...>

[Graham_Moir]

Not sure I completely understand how this has been translated into a 'feature request' when it's clearly inconsistent behaviour and therefore a bug?

[Geert Bellekens]

Graham,

I think at Sparx they define a bug as "not working as designed".

So the shape scripts for BPMN were never designed to include the little red A, therefore it currently works as designed 

I actually have stopped caring about the difference bug/change a long time ago, as long as it is implemented...

Geert

[Glassboy]

I feel you Geert, I logged a support request with a vendor today and had to endure three rounds of links to help centre articles only vaguely related to my fault before they'd acknowledge and pass it onto an engineer.  I'm happy that Sparx tries to recreate issues and doesn't quibble.