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

In Batch Operation View, only a subset of historic decision instances are shown

    XMLWordPrintable

Details

    • Bug Report
    • Resolution: Fixed
    • L3 - Default
    • 7.9.0, 7.9.0-alpha2
    • 7.9.0-alpha1
    • cockpit
    • None

    Description

      Steps to reproduce:
      1) open the batch operation view in cockpit
      2) select the batch operation "Delete decision instances"
      3) add a criteria "Process Definition Key = invoice"
      4) Change the batch operation to "Delete running process instances"
      5) Switch back to batch operation "Delete decision instances"

      Observed Behavior:

      • In step 4, the following error is logged in the browser console
        Cannot read property 'groups' of null
            at cam-widget-search.js:178
            at Array.map (<anonymous>)
            at getTypes (cam-widget-search.js:177)
            at Object.fn (cam-widget-search.js:537)
            at Scope.$digest (deps.js?bust=1516387311481:12691)
            at Scope.$apply (deps.js?bust=1516387311481:12956)
            at HTMLSelectElement.<anonymous> (deps.js?bust=1516387311481:21824)
            at HTMLSelectElement.dispatch (deps.js?bust=1516387311481:143518)
            at HTMLSelectElement.elemData.handle (deps.js?bust=1516387311481:143204)
        
      • In step 5, only a subset of decision instances are shown, because the filter criteria "Process Definition Key = invoice" is applied, but the filter criteria is not shown

      Expected Behavior:

      • the error is not thrown
      • the filter criteria is not applied, so that all decision instances are shown

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Activity

            People

              michael.schoettes Michael Schoettes
              roman.smirnov Roman Smirnov
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Salesforce