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

History view of a multi-instance subprocess shows no tokens and a forever loading spinner

XMLWordPrintable

      Environment:

      Camunda Platform 7.17.0-ee

      Description:

      The history tokens are not shown for a completed multi-instance subprocess and a loading indicator that never ends is also visible.

      Steps to Reproduce:

      1. Deploy printer.bpmn as Printer
      2. In Tasklist->Start a new process for Printer
      3. Once the task has started go to Cockpit->Running Instances
      4. Find your Printer process definition
      5. Navigate to the completed process instance

      Observed Behaviour:

      No history tokens and a constantly loading spinner in the history view.

      Expected Behaviour:

      All history tokens should be displayed in the history view, and without a loading indicator present.

      Root Cause:

      With 7.17, we introduced the feature to drill down into embedded subprocesses. This changed the behaviour of the statistics badges that are generated on the process instance history diagram. The new logic iterates through all flow-nodes that are returned by the historic activity statistics request and maps it with the flow-nodes present in the BPMN XML model registry.

      When viewing a process with a multi-instance subprocess, the multiInstanceBody is returned by the historic activity statistics request. However, this flow-node is an execution detail and therefore not part of the BPMN XML model registry. When trying to get the #businessObject of the non-existing multiInstanceBody, an error is thrown that leads to unexpected behaviour.

      Solution Ideas:

      Prevent further operations, such as annotating an element, if the activity is not present in the element registry.

      Hints:

      • The issue is isolated to the history view of the instance
      • REST endpoints currently return the relevant historical data
      • Check how the history token data is passed to the history view of the instance

        This is the controller panel for Smart Panels app

          1. multi-instance.bpmn
            3 kB
          2. printer.bpmn
            4 kB
          3. SUPPORT-13681.mp4
            1.25 MB

            [CAM-14652] History view of a multi-instance subprocess shows no tokens and a forever loading spinner

            Clifton Davies created issue -
            Clifton Davies made changes -
            Link New: This issue is related to SUPPORT-13681 [ SUPPORT-13681 ]
            Clifton Davies made changes -
            Description Original: h3. Environment:

            Camunda Platform 7.17.0-ee
            h3. Description:

            The history tokens are not shown for a completed multi-instance subprocess and a loading indicator that never ends is also visible. This is the case when the parent process is completed or still running.
            h3. Steps to reproduce:
             # Deploy multi-instance.bpmn and printer.bpmn, as a single deployment called *Multi Instance*
             # In Tasklist->Start a new process for *Multi Instance*
             # Once the task has started go to Cockpit->Running Instances
             # Find your *Multi Instance* process definition
             # Navigate to the running or completed process instance
             # Open the *Print lots* multi-instance subprocess

            h3. Observed behaviour:

            No history tokens and a constantly loading spinner in the history view.
            h3. Expected behaviour:

            All history tokens should be displayed in the history view, and without a loading indicator present.
            h3. Root Cause:

            TBD.
            h3. Hints:
             * The issue is isolated to the history view of the instance
             * REST endpoints currently return the relevant historical data
             * Check how the history token data is passed to the history view of the instance             		New: h3. Environment:

            Camunda Platform 7.17.0-ee
            h3. Description:

            The history tokens are not shown for a completed multi-instance subprocess and a loading indicator that never ends is also visible. This is the case when the parent process is completed or still running.
            h3. Steps to reproduce:
             # Deploy multi-instance.bpmn and printer.bpmn, as a single deployment called *Multi Instance*
             # In Tasklist->Start a new process for *Multi Instance*
             # Once the task has started go to Cockpit->Running Instances
             # Find your *Multi Instance* process definition
             # Navigate to the running or completed process instance
             # Open the *Print lots* multi-instance subprocess

            h3. Observed behaviour:

            No history tokens and a constantly loading spinner in the history view.
            h3. Expected behaviour:

            All history tokens should be displayed in the history view, and without a loading indicator present.
            h3. Root Cause:

            A change to the way we retrieve historic statistics for each activity (since 7.17.0) now results in an activity being present in the resource execution context but not necessarily in the BPMN element registry. Currently, an error is thrown when an attempt is made to access an activity that does not exist in the element registry, as was the case for the *Multi Instance* process.

            Implementation:
             * [Prior to 7.17.0|https://github.com/camunda/camunda-bpm-platform-ee-maintenance/blob/4e3e713c95630e0a41d7102a3a20bb01976c690f/webapps/camunda-webapp/plugins/src/main/resources-plugin/cockpit/history/app/views/processInstance/diagramPlugins/stats.js#L53]
             * [From 7.17.0|https://github.com/camunda/camunda-bpm-platform-ee/blob/80e097cb8eb54d11d7d752746bc4fbf01e42c3e9/webapps/camunda-webapp/plugins/src/main/resources-plugin/cockpit/history/app/views/processInstance/diagramPlugins/stats.js#L84]

            h3. Solution Ideas:

            Prevent further operations, such as annotating an element, if the activity is not present in the element registry.
            h3. Hints:
             * The issue is isolated to the history view of the instance
             * REST endpoints currently return the relevant historical data
             * Check how the history token data is passed to the history view of the instance
            Clifton Davies made changes -
            Description Original: h3. Environment:

            Camunda Platform 7.17.0-ee
            h3. Description:

            The history tokens are not shown for a completed multi-instance subprocess and a loading indicator that never ends is also visible. This is the case when the parent process is completed or still running.
            h3. Steps to reproduce:
             # Deploy multi-instance.bpmn and printer.bpmn, as a single deployment called *Multi Instance*
             # In Tasklist->Start a new process for *Multi Instance*
             # Once the task has started go to Cockpit->Running Instances
             # Find your *Multi Instance* process definition
             # Navigate to the running or completed process instance
             # Open the *Print lots* multi-instance subprocess

            h3. Observed behaviour:

            No history tokens and a constantly loading spinner in the history view.
            h3. Expected behaviour:

            All history tokens should be displayed in the history view, and without a loading indicator present.
            h3. Root Cause:

            A change to the way we retrieve historic statistics for each activity (since 7.17.0) now results in an activity being present in the resource execution context but not necessarily in the BPMN element registry. Currently, an error is thrown when an attempt is made to access an activity that does not exist in the element registry, as was the case for the *Multi Instance* process.

            Implementation:
             * [Prior to 7.17.0|https://github.com/camunda/camunda-bpm-platform-ee-maintenance/blob/4e3e713c95630e0a41d7102a3a20bb01976c690f/webapps/camunda-webapp/plugins/src/main/resources-plugin/cockpit/history/app/views/processInstance/diagramPlugins/stats.js#L53]
             * [From 7.17.0|https://github.com/camunda/camunda-bpm-platform-ee/blob/80e097cb8eb54d11d7d752746bc4fbf01e42c3e9/webapps/camunda-webapp/plugins/src/main/resources-plugin/cockpit/history/app/views/processInstance/diagramPlugins/stats.js#L84]

            h3. Solution Ideas:

            Prevent further operations, such as annotating an element, if the activity is not present in the element registry.
            h3. Hints:
             * The issue is isolated to the history view of the instance
             * REST endpoints currently return the relevant historical data
             * Check how the history token data is passed to the history view of the instance             		New: h3. Environment:

            Camunda Platform 7.17.0-ee
            h3. Description:

            The history tokens are not shown for a completed multi-instance subprocess and a loading indicator that never ends is also visible. This is the case when the parent process is completed or still running.
            h3. Steps to reproduce:
             # Deploy multi-instance.bpmn and printer.bpmn, as a single deployment called *Multi Instance*
             # In Tasklist->Start a new process for *Multi Instance*
             # Once the task has started go to Cockpit->Running Instances
             # Find your *Multi Instance* process definition
             # Navigate to the running or completed process instance
             # Open the *Print lots* multi-instance subprocess

            h3. Observed behaviour:

            No history tokens and a constantly loading spinner in the history view.
            h3. Expected behaviour:

            All history tokens should be displayed in the history view, and without a loading indicator present.
            h3. Root Cause:

            A change to the way we retrieve historic statistics for each activity (since 7.17.0) now results in an activity being present in the resource execution context but not necessarily in the BPMN element registry. Currently, an error is thrown when an attempt is made to access an activity that does not exist in the element registry, as was the case for the *Multi Instance* process.

            Implementation for Historic Activity Statistics:
             * [Prior to 7.17.0|https://github.com/camunda/camunda-bpm-platform-ee-maintenance/blob/4e3e713c95630e0a41d7102a3a20bb01976c690f/webapps/camunda-webapp/plugins/src/main/resources-plugin/cockpit/history/app/views/processInstance/diagramPlugins/stats.js#L53]
             * [From 7.17.0|https://github.com/camunda/camunda-bpm-platform-ee/blob/80e097cb8eb54d11d7d752746bc4fbf01e42c3e9/webapps/camunda-webapp/plugins/src/main/resources-plugin/cockpit/history/app/views/processInstance/diagramPlugins/stats.js#L84]

            h3. Solution Ideas:

            Prevent further operations, such as annotating an element, if the activity is not present in the element registry.
            h3. Hints:
             * The issue is isolated to the history view of the instance
             * REST endpoints currently return the relevant historical data
             * Check how the history token data is passed to the history view of the instance
            Clifton Davies made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]
            Clifton Davies made changes -
            Fix Version/s New: 7.18.0 [ 17394 ]
            Fix Version/s New: 7.17.2 [ 17692 ]
            Clifton Davies made changes -
            Fix Version/s New: 7.17.x [ 17395 ]
            Fix Version/s Original: 7.17.2 [ 17692 ]
            Clifton Davies made changes -
            Description Original: h3. Environment:

            Camunda Platform 7.17.0-ee
            h3. Description:

            The history tokens are not shown for a completed multi-instance subprocess and a loading indicator that never ends is also visible. This is the case when the parent process is completed or still running.
            h3. Steps to reproduce:
             # Deploy multi-instance.bpmn and printer.bpmn, as a single deployment called *Multi Instance*
             # In Tasklist->Start a new process for *Multi Instance*
             # Once the task has started go to Cockpit->Running Instances
             # Find your *Multi Instance* process definition
             # Navigate to the running or completed process instance
             # Open the *Print lots* multi-instance subprocess

            h3. Observed behaviour:

            No history tokens and a constantly loading spinner in the history view.
            h3. Expected behaviour:

            All history tokens should be displayed in the history view, and without a loading indicator present.
            h3. Root Cause:

            A change to the way we retrieve historic statistics for each activity (since 7.17.0) now results in an activity being present in the resource execution context but not necessarily in the BPMN element registry. Currently, an error is thrown when an attempt is made to access an activity that does not exist in the element registry, as was the case for the *Multi Instance* process.

            Implementation for Historic Activity Statistics:
             * [Prior to 7.17.0|https://github.com/camunda/camunda-bpm-platform-ee-maintenance/blob/4e3e713c95630e0a41d7102a3a20bb01976c690f/webapps/camunda-webapp/plugins/src/main/resources-plugin/cockpit/history/app/views/processInstance/diagramPlugins/stats.js#L53]
             * [From 7.17.0|https://github.com/camunda/camunda-bpm-platform-ee/blob/80e097cb8eb54d11d7d752746bc4fbf01e42c3e9/webapps/camunda-webapp/plugins/src/main/resources-plugin/cockpit/history/app/views/processInstance/diagramPlugins/stats.js#L84]

            h3. Solution Ideas:

            Prevent further operations, such as annotating an element, if the activity is not present in the element registry.
            h3. Hints:
             * The issue is isolated to the history view of the instance
             * REST endpoints currently return the relevant historical data
             * Check how the history token data is passed to the history view of the instance             		New: h3. Environment:

            Camunda Platform 7.17.0-ee
            h3. Description:

            The history tokens are not shown for a completed multi-instance subprocess and a loading indicator that never ends is also visible.
            h3. Steps to Reproduce:
             # Deploy printer.bpmn as *Printer*
             # In Tasklist->Start a new process for *Printer*
             # Once the task has started go to Cockpit->Running Instances
             # Find your *Printer* process definition
             # Navigate to the completed process instance

            h3. Observed Behaviour:

            No history tokens and a constantly loading spinner in the history view.
            h3. Expected Behaviour:

            All history tokens should be displayed in the history view, and without a loading indicator present.
            h3. Root Cause:

            With 7.17, we introduced the feature to drill down into embedded subprocesses. This changed the behaviour of the statistics badges that are generated on the process instance history diagram. The [new logic|https://github.com/camunda/camunda-bpm-platform-ee/blob/80e097cb8eb54d11d7d752746bc4fbf01e42c3e9/webapps/camunda-webapp/plugins/src/main/resources-plugin/cockpit/history/app/views/processInstance/diagramPlugins/stats.js#L84-L87] iterates through all flow-nodes that are returned by the historic activity statistics request and maps it with the flow-nodes present in the BPMN XML model registry.

            When viewing a process with a multi-instance subprocess, the _multiInstanceBody_ is returned by the historic activity statistics request. However, this flow-node is an execution detail and therefore not part of the BPMN XML model registry. When trying to get the _#businessObject_ of the not existing {_}multiInstanceBody{_}, an error is thrown that leads to unexpected behaviour.
            h3. Solution Ideas:

            Prevent further operations, such as annotating an element, if the activity is not present in the element registry.
            h3. Hints:
             * The issue is isolated to the history view of the instance
             * REST endpoints currently return the relevant historical data
             * Check how the history token data is passed to the history view of the instance
            Clifton Davies made changes -
            Description Original: h3. Environment:

            Camunda Platform 7.17.0-ee
            h3. Description:

            The history tokens are not shown for a completed multi-instance subprocess and a loading indicator that never ends is also visible.
            h3. Steps to Reproduce:
             # Deploy printer.bpmn as *Printer*
             # In Tasklist->Start a new process for *Printer*
             # Once the task has started go to Cockpit->Running Instances
             # Find your *Printer* process definition
             # Navigate to the completed process instance

            h3. Observed Behaviour:

            No history tokens and a constantly loading spinner in the history view.
            h3. Expected Behaviour:

            All history tokens should be displayed in the history view, and without a loading indicator present.
            h3. Root Cause:

            With 7.17, we introduced the feature to drill down into embedded subprocesses. This changed the behaviour of the statistics badges that are generated on the process instance history diagram. The [new logic|https://github.com/camunda/camunda-bpm-platform-ee/blob/80e097cb8eb54d11d7d752746bc4fbf01e42c3e9/webapps/camunda-webapp/plugins/src/main/resources-plugin/cockpit/history/app/views/processInstance/diagramPlugins/stats.js#L84-L87] iterates through all flow-nodes that are returned by the historic activity statistics request and maps it with the flow-nodes present in the BPMN XML model registry.

            When viewing a process with a multi-instance subprocess, the _multiInstanceBody_ is returned by the historic activity statistics request. However, this flow-node is an execution detail and therefore not part of the BPMN XML model registry. When trying to get the _#businessObject_ of the not existing {_}multiInstanceBody{_}, an error is thrown that leads to unexpected behaviour.
            h3. Solution Ideas:

            Prevent further operations, such as annotating an element, if the activity is not present in the element registry.
            h3. Hints:
             * The issue is isolated to the history view of the instance
             * REST endpoints currently return the relevant historical data
             * Check how the history token data is passed to the history view of the instance             		New: h3. Environment:

            Camunda Platform 7.17.0-ee
            h3. Description:

            The history tokens are not shown for a completed multi-instance subprocess and a loading indicator that never ends is also visible.
            h3. Steps to Reproduce:
             # Deploy printer.bpmn as *Printer*
             # In Tasklist->Start a new process for *Printer*
             # Once the task has started go to Cockpit->Running Instances
             # Find your *Printer* process definition
             # Navigate to the completed process instance

            h3. Observed Behaviour:

            No history tokens and a constantly loading spinner in the history view.
            h3. Expected Behaviour:

            All history tokens should be displayed in the history view, and without a loading indicator present.
            h3. Root Cause:

            With 7.17, we introduced the feature to drill down into embedded subprocesses. This changed the behaviour of the statistics badges that are generated on the process instance history diagram. The [new logic|https://github.com/camunda/camunda-bpm-platform-ee/blob/80e097cb8eb54d11d7d752746bc4fbf01e42c3e9/webapps/camunda-webapp/plugins/src/main/resources-plugin/cockpit/history/app/views/processInstance/diagramPlugins/stats.js#L84-L87] iterates through all flow-nodes that are returned by the historic activity statistics request and maps it with the flow-nodes present in the BPMN XML model registry.

            When viewing a process with a multi-instance subprocess, the _multiInstanceBody_ is returned by the historic activity statistics request. However, this flow-node is an execution detail and therefore not part of the BPMN XML model registry. When trying to get the _#businessObject_ of the non-existing {_}multiInstanceBody{_}, an error is thrown that leads to unexpected behaviour.
            h3. Solution Ideas:

            Prevent further operations, such as annotating an element, if the activity is not present in the element registry.
            h3. Hints:
             * The issue is isolated to the history view of the instance
             * REST endpoints currently return the relevant historical data
             * Check how the history token data is passed to the history view of the instance
            Thorben Lindhauer made changes -
            Remote Link New: This issue links to "Page (camunda confluence)" [ 17440 ]

              clifton.davies Clifton Davies
              clifton.davies Clifton Davies
              Clifton Davies Clifton Davies
              Tassilo Weidner Tassilo Weidner
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: