Activiti
  1. Activiti
  2. ACT-638

Implement non interrupting boundaryEvent (cancelActivity="false")

    Details

    • Type: New Feature New Feature
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.10
    • Component/s: Engine
    • Labels:
      None
    • Number of attachments :
      0

      Description

      see ACT-284, this is currently missing but specified in BPMN 2.0.

      example:
      <boundaryEvent id="escalationMail" cancelActivity="false" attachedToRef="firstLineSupport">
      <timerEventDefinition>
      <timeDuration>PT4H</timeDuration>
      </timerEventDefinition>
      </boundaryEvent>

      Raised by support case https://app.camunda.com/jira/browse/SUPPORT-56

        Issue Links

          Activity

          Hide
          Joram Barrez added a comment -

          I added a failing test to the testcase.

          Coverage is not good enough, so I'm removing the documentation. Postponing to next release.

          Show
          Joram Barrez added a comment - I added a failing test to the testcase. Coverage is not good enough, so I'm removing the documentation. Postponing to next release.
          Hide
          Martin Pradny added a comment - - edited

          Any plans to complete this? Currently it seems to work, but it can't be set in Designer.

          Show
          Martin Pradny added a comment - - edited Any plans to complete this? Currently it seems to work, but it can't be set in Designer.
          Hide
          Nils Preusker (camunda) added a comment -

          I added another failing test case in org.activiti.engine.test.bpmn.event.timer.BoundaryTimerNonInterruptingEventTest. It shows that the execution in a subprocess doesn't accept signals after a boundary timer fires, even if the cancelActivity attribute of the timer is set to 'false'.

          This is because in org.activiti.engine.impl.jobexecutor.TimerExecuteNestedActivityJobHandler, the current activity of the execution in the sub-process is set to the boundary event, regardless of the value of the cancelActivity attribute.

          Show
          Nils Preusker (camunda) added a comment - I added another failing test case in org.activiti.engine.test.bpmn.event.timer.BoundaryTimerNonInterruptingEventTest. It shows that the execution in a subprocess doesn't accept signals after a boundary timer fires, even if the cancelActivity attribute of the timer is set to 'false'. This is because in org.activiti.engine.impl.jobexecutor.TimerExecuteNestedActivityJobHandler, the current activity of the execution in the sub-process is set to the boundary event, regardless of the value of the cancelActivity attribute.
          Hide
          Daniel Meyer (camunda) added a comment -

          Coverage is better now; all failing tests run. I am closing this issue. If problems arise, they can be filed as individual issues.

          Show
          Daniel Meyer (camunda) added a comment - Coverage is better now; all failing tests run. I am closing this issue. If problems arise, they can be filed as individual issues.
          Hide
          Bernd Ruecker (camunda) added a comment -

          I re-added the docs for it (was commented until it leaves experimental stage)

          Show
          Bernd Ruecker (camunda) added a comment - I re-added the docs for it (was commented until it leaves experimental stage)

            People

            • Assignee:
              Daniel Meyer (camunda)
              Reporter:
              Bernd Ruecker (camunda)
            • Votes:
              5 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: