Output Variable Mapping is not applied when the event is thrown from a concurrent execution

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Fixed
    • Priority: L3 - Default
    • 7.10.0, 7.9.4, 7.10.0-alpha4
    • Affects Version/s: 7.7.0, 7.8.0, 7.9.0, 7.10.0-alpha3
    • Component/s: engine

      Problem:
      The output variable mapping of a call activity is not applied when the error/escalation event is thrown from a concurrent execution of the child instance.
      Note that it is applied when the event is thrown from a non-concurrent execution. (see the attached processes)

      AT:

      • the output variable mapping of a call activity is executed with the variables of the child process when the error/escalation event is thrown from a concurrent execution of the child instance

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Philipp Ossler
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: