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

Call Activity Output Parameters are propagated on uncaught error event in called process

    XMLWordPrintable

Details

    • Bug Report
    • Resolution: Unresolved
    • L3 - Default
    • None
    • None
    • engine
    • None

    Description

      • Variables are propagated while the error event definition is looked up.
      • If no error handler is found, the throwing execution ends, but not necessarily its process instance (e.g. in case of concurrency)
      • In consequence, the process instance may not end but variables are propagated nonetheless

      Related code:

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            is related to

            Bug Report - A problem which impairs or prevents the functions of the product. CAM-6143 Call Activity Output Parameters are propagated on escalation event that is caught non-interruptibly in the parent process

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Open

            Feature Request - A new feature of the product, which has yet to be developed. CAM-5300 Propagate Output Variable Mapping of a Call Activity when a thrown Error Event is catched

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Open
            links to

            Web Link https://github.com/camunda/camunda-bpm-platform/issues/2088

            Web Link https://github.com/camunda/camunda-bpm-platform/issues/2248

            Activity

              People

                Unassigned Unassigned
                thorben.lindhauer Thorben Lindhauer
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:

                  Salesforce