Drill-down into composite diagram not working - EA 16.1, BPMN 2.0

[Ian Mitchell]

Somehow I seem to have lost the ability to double-click on any element which has a composite structure diagram, and open the child diagram.
As a test, I tried the BPMN 2.0, 'Sub-Process' example from EAExample.qea from EA 16.1, and even that doesn't work. So it must be a something in my local setup of EA.
Also just noticed that I also can't double-click on hyperlinks (where a diagram has a hyperlink to another diagram).

Does anyone know if there is a switch/setting/preference which I have messed-up which has disabled this ?

[Ian Mitchell]

Update on this - taking the same content via copy/paste into v15.1 and everything works fine - so it's just something stupid I've done in V16.
Any ideas?

[Guillaume]

Hi Ian,

Isn't it related with the following instead of EA 16 ?
When you create a BPMN activity, you can change the "activityType" tagged value from Task to Sub-Process which leads to render the task node with a +, yet this is not a composite element (set with the right click > new child diagram ..)
In BPMN a sub process task and a composite element task are both rendered the same way i.e. with the "+"

[Ian Mitchell]

Hi Guillaume - Happy New Year to you.
I don't think it's related - I moved the package, with all diagrams and composites - to EA 15.1, and everything worked ok. Even diagram hyperlinks are not working. Very strange.

[Takeshi K]

Hi Guillaume,

I think current behaviour of EA is not correct. The + mark should be related to the activityType in the BPMN specification.

The specification does not consider implementation of tools, so I think it is okay to show the mark if an Activity is composite. But if do so, the activityType value should be 'Sub-Process'. In this point, EA does not match the specification since EA shows the mark but activityType is still 'Task'.

[Ian Mitchell]

OK - this is a bit embarassing....
Finally traced the issue to one of my own addins, which when responding to the EA_OnContextItemDoubleClicked event had a default response of 'true', which says to EA 'I have handelled the event - you don't need to', rather than FALSE, which means 'EA - please deal with this double-click'.
Boy, do I feel stupid.

[Geert Bellekens]

OK - this is a bit embarassing....
Finally traced the issue to one of my own addins, which when responding to the EA_OnContextItemDoubleClicked event had a default response of 'true', which says to EA 'I have handelled the event - you don't need to', rather than FALSE, which means 'EA - please deal with this double-click'.
Boy, do I feel stupid.

I'm glad it's not an EA problem.
Thanks for the update

Geert

[wivel]

OK - this is a bit embarassing....
Finally traced the issue to one of my own addins, which when responding to the EA_OnContextItemDoubleClicked event had a default response of 'true', which says to EA 'I have handelled the event - you don't need to', rather than FALSE, which means 'EA - please deal with this double-click'.
Boy, do I feel stupid.

Thanks for the information. Was worried that it was yet another EA 16.x issue.

Henrik