Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-14712

Output values not recognized by conditional flows

    XMLWordPrintable

Details

    • Bug Report
    • Resolution: Duplicate
    • L3 - Default
    • None
    • None
    • None
    • None

    Description

      Environment (Required on creation):

      Camunda Engine 7.17.0

      Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):

      When setting an output value, it is recognized by an XOR-Gateway, but not by a conditional flow

      Steps to reproduce (Required on creation):

      Run the following processes:

      When setting the output in a task it is recognized by a an XOR-Gateway:

      Attachment: taskOutputSetsFoobar.bpmn

      When setting the output in a task it is not recognized by a conditional flow:

      Attachment: taskOutputSetsFoobarConditionalFlowError.bpmn

      Observed Behavior (Required on creation):

      Error is thrown:

      Caused by: org.camunda.bpm.engine.impl.javax.el.PropertyNotFoundException: Cannot resolve identifier 'taskOutput'

      Expected behavior (Required on creation):

      No error should be thrown and Token should arrive at "Stop: Foobar"-UserTask

      Root Cause (Required on prioritization):

      It seems that conditional flows are evaluated before outputs are set

      Solution Ideas (Optional):

      Set outputs before conditional flows are evaluated

      Hints (optional):

      There already exists a forum post where I started to discuss this issue:

      Output values not recognized by conditional flows - Camunda Platform 7 Topics / Camunda Platform 7 Process Engine - Camunda Platform Forum

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            Activity

              People

                nikola.koevski Nikola Koevski
                krisMeta Krzysztof Franek
                Votes:
                1 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce