stereotypedrelationship for ActivityParameter-Pin not taken

[qwerty]

I have added a stereotypedrelationship  between a stereotyped ActivityParameter and a metaclass ActionPin representing an ObjectFlow. However, when I create that connector (it's present in the QL) EA complains about Invalid combination...

If I report this as bug, would there be a chance to see it fixed in V17? (My customer seems to skip the even releases and not in my wildest dreams I would expect to see a fix for that already in V16.)

q.

P.S. Yes, yes. I have told him to turn off strict connector syntax. But where's the point in adding constraints if in the same way you need to turn off the checks at all???

[Eve]

It's likely if you gave a report that gave us everything we need to reproduce it that it would be fixed in 16.

[qwerty]

I don't have the best experience with my bug reports (that is most of them were gone with the wind). Anyhow I'll make up a report with some sample and send a report. Let's see what happens. Things might have changed.

q.

[qwerty]

Well, I sent the bug report. It was not possible to attach the prepared MDG/profile source with the report. They'll likely ask for it.

q.

P.S. I uploaded the sample here. There's a sample diagram at the very top where you can draw an OF (object flow) from an activity parameter towards an action pin (the filter to toolbox must be disabled). Unless you disable the strict connector check it will croak.

[qwerty]

I got confirmation that this is a bug which eventually will find a fix in V16. Hoping the best, so my customer can benefit of that in V17.

q.