Closed original issue as only one simple change has not been addressed. The description can be found bellow. +++ This bug was initially created as a clone of Bug #1091374 +++ Description of problem: - change the label "Cancel Activity" for "Is Interrupting" in the events which can be set to be non-interrupting as it is in the Web BPMN Designer. It is more clear according to BPMN Specification. E.g. the Plain 'Start' event still contains 'Cancel Activity' instead of 'Is Interrupting' and there are others.
Hmm, I think I was confused about exactly what was the desired label because I had added some code to display "Cancel Activity" instead of the default "Is Interrupting". So, just to be sure: Cancel Activity = BAD Is Interrupting = GOOD Does that about sum it up?
I'm confused too now :D Let's ask the original reporter.
Hi Bob, yes that is exactly how I meant it. The "Is Interrupting" is more approriate for the activities that can be non-interrupting. You might look at the BPMN Web Designer in Business Central where you can find the same label "Is Interrupting" (e.g. in the intermediate catching timer event). Thanks
OK, I think I have a better understanding of this "Cancel Activity" vs "Is Interrupting" issue: "Is Interrupting" is a Start Event attribute, and it only applies if the Start Event is contained in an Event SubProcess. It should NOT be displayed for other types of Start Events. "Cancel Activity" is a Boundary Event attribute, and indicates whether the Activity to which it is attached should be canceled or not. If the Activity is not cancelled, multiple instances of the handler connected to the Boundary Event can run concurrently. This attribute cannot be applied to Error Events (where it’s always true), or Compensation Events (where it doesn’t apply) and should NOT be displayed. In any case, the BPMN2 spec uses the terms "Interrupting" and "Non-Interrupting" for Boundary Events, and these are interpreted as Cancel Activity = true, and Cancel Activity = false, respectively. These terms do NOT have the same meaning as "Is Interrupting" used for Start Events. So, I think it's possible that the Web Designer might be using the term "Is Interrupting" incorrectly in some cases. Arghhh! This is going to take a bit of time because I'll have to add more logic to untangle this mess.
Hi Bob, I looked again to the specification and you are right. The problem is mainly in the Web BPMN Designer because it uses "Is Interrupting" almost everywhere (sometimes together with "Cancel Activity"). Therefore, I will update BZ 1091366. To paraphrase, according to the descriptions, the start event should not have the "Cancel Activity" attribute at all (it is not a boundary event) and instead "Is Interrupting" should be there if the start event is in an event sub-processes. There should be anything else to change, should not be? I checked it in JBDSIS 8.0.0.Alpha2. Thank you
OK, I'll make these changes in the BPMN2 Modeler. I have reopened and updated https://bugs.eclipse.org/bugs/show_bug.cgi?id=433704 to include this conversation. Once it's fixed, I'll close 1150074 (this BZ).
This is now fixed in 1.1.1 (luna) and 1.0.3 (kepler). The "Is Interrupting" checkbox for Start Events is now correctly displayed, as per the BPMN2 spec. Same thing for "Cancel Activity".
Hi bob, in jbdsis-8.0.0.Beta1, attribute 'Cancel Activity' is shown correctly on boundary event, but If I create subprocess with for example Message Start Event inside, I don't see 'Is Interrupting' attribute anywhere in properties of Message Start Event. I hope, I understand correctly your discussion with Ivo. I have deduced, that Start Event should have attribute 'Is Interrupting' if it is inside Sub Process.
Sorry, it was my mistake, I did not use Event Sub Process, then it works.
Verified on jbdsis-8.0.0.Beta1.