We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
We couldn't load the project sidebar. Refresh the page to try again.
If the problem persists, contact your Jira admin.
Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-8462

I can collect multi-instance activity results

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • engine
    • None

      There exists two extensions attributes which can be used in combination with the <bpmn:multiInstanceLoopCharacteristics/> element:

      • camunda:resultVariable: declares a variable which exists in the scope of the multi-instance activity, whereby the value of it should be collected.
      • camunda:resultCollection: declares a collection which will be available in the process instance as a variable. This collection collects the values of the result variables.

      An example could look like this:

      <bpmn:multiInstanceLoopCharacteristics camunda:resultVariable="foo" camunda:resultCollection="bar" ...>
  ...
</bpmn:multiInstanceLoopCharacteristics>

      Semantic:
      Whenever an instance of the specific activity completes, then the value of the variable foo declared by the attribute camunda:resultVariable will be added to the declared collection bar by the attribute camunda:resultCollection.

      Hint:

      • There is a similar limitation in serialization of the collection declared by camunda:resultCollection like it already exists for the mapping of decision results [1].
      • The properties must be exposed in the Camunda modeler.

      [1]: https://docs.camunda.org/manual/7.7/user-guide/process-engine/decisions/bpmn-cmmn/#limitations-of-the-serialization-of-the-mapping-result

        This is the controller panel for Smart Panels app

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

            I can collect multi-instance activity results

            XMLWordPrintable

              • Icon: Feature Request Feature Request
              • Resolution: Unresolved
              • Icon: L3 - Default L3 - Default
              • None
              • None
              • engine
              • None

                There exists two extensions attributes which can be used in combination with the <bpmn:multiInstanceLoopCharacteristics/> element:

                • camunda:resultVariable: declares a variable which exists in the scope of the multi-instance activity, whereby the value of it should be collected.
                • camunda:resultCollection: declares a collection which will be available in the process instance as a variable. This collection collects the values of the result variables.

                An example could look like this:

                <bpmn:multiInstanceLoopCharacteristics camunda:resultVariable="foo" camunda:resultCollection="bar" ...>
  ...
</bpmn:multiInstanceLoopCharacteristics>

                Semantic:
                Whenever an instance of the specific activity completes, then the value of the variable foo declared by the attribute camunda:resultVariable will be added to the declared collection bar by the attribute camunda:resultCollection.

                Hint:

                • There is a similar limitation in serialization of the collection declared by camunda:resultCollection like it already exists for the mapping of decision results [1].
                • The properties must be exposed in the Camunda modeler.

                [1]: https://docs.camunda.org/manual/7.7/user-guide/process-engine/decisions/bpmn-cmmn/#limitations-of-the-serialization-of-the-mapping-result

                  This is the controller panel for Smart Panels app

                        Unassigned Unassigned
                        roman.smirnov Roman Smirnov
                        Votes:
                        2 Vote for this issue
                        Watchers:
                        4 Start watching this issue

                          Created:
                          Updated:

                              Unassigned Unassigned
                              roman.smirnov Roman Smirnov
                              Votes:
                              2 Vote for this issue
                              Watchers:
                              4 Start watching this issue

                                Created:
                                Updated: