v15.2 - Allow BPMN Shapes to display Notes

[Paolo F Cantoni]

We document our BPMN process diagram with explanatory notes (held, naturally enough, in the Notes field).  However, there doesn't seem to be any way to display them except as a "Feature Linked Note".  This is both cumbersome and frustrating.

Can we please allow BPMN shapescripts to allow the (conditional) display of notes compartments?

Reported,
Paolo

[Ian Mitchell]

+1. Wanted to do that for a long time.
With BPMN, this would means we can get the users to use a much smaller set of modelling constructs, then, if they really want to be clever, they can just add something in the notes, and everyone's happy.

[Paolo F Cantoni]

I have heard from Sparx Support:
Apart from linking element's note, you can also display notes within by custom draw style.
Use BPMN process object context menu "Enable Custom Draw Style", then enable 'Notes' compartment  (Ctrl+ Shift+y)


To which I replied:
I didn't know that!  That may be useful in some circumstances, but it doesn't quite reflect the specific need.  We need the standard BMPN shape with visible notes compartment.

The Custom Draw Style is VERY simple, and (IIRC) makes ALL objects so converted look the same - regardless of metatype.

Does that encapsulate the requirement?

Paolo

[OpenIT Solutions]

It would also be nice to have configurable tooltips that show in WebEA when you mouse over an element. Ie configure to show notes when you mouse over an Activity.

[Geert Bellekens]

One could argue that a standard BPMN shape, with a notes compartment, is no longer a standard BPMN shape.

Geert

[Paolo F Cantoni]

One could argue that a standard BPMN shape, with a notes compartment, is no longer a standard BPMN shape.

Geert

I'm not asking to change the standard, I'm asking to change EA 

I (as always) have an aphorism:  "A picture is worth a thousand words - until there are more than 6 shapes and 12 lines; when all bets are off".

Most BPMN diagrams fall into this category.  You NEED narrative to provide additional information that cannot be converted by the diagrammatic elements.

The notion that you should have to create a NEW item (separated from the "item under inspection") and a NEW relationship, MERELY to document the description of the item under inspection is ludicrous.