JS renderer fails when sequence flow has no condition

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Fixed
    • Priority: L3 - Default
    • 7.0.0-rc, 7.0.0
    • Affects Version/s: None
    • Component/s: engine, renderer
    • None

      Hi,

      we've experienced that the camunda-bpm-js render fails if a sequence flow doesn't have a condition. The engine on the other side just logs a warning and uses this flow as default flow.

      Engine output:

      org.camunda.bpm.engine.impl.util.xml.Parse logWarnings
      WARNUNG: Exclusive Gateway 'checkRoleNodeIds' has outgoing sequence flow 'SequenceFlow_15' without condition which is not the default flow. We assume it to be the default flow, but it is bad modeling practice, better set the default flow in your gateway.

      JS renderer output/error

      Fehler: uncaught exception: Sequence flow with id 'SequenceFlow_15' has no conditions but it is not configured to be the default flow.

      Note: It would be cool if I can get all problems (warnings) in org.camunda.bpm.engine.impl.bpmn.parser.BpmnParse over a service to show my users such bad practices on deployment time.

        This is the controller panel for Smart Panels app

              Assignee:
              Roman Smirnov
              Reporter:
              Michael Oberwasserlechner
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: