Verify how breaking definition changes affect the report editor

XMLWordPrintable

    • Type: Task
    • Resolution: Done
    • Priority: L3 - Default
    • 2.7.0
    • Affects Version/s: None
    • Component/s: frontend
    • None

      Context:
      In the meeting about event based processes we encountered an edge case that can as well happen to reports on engine processes.

      Scenario to verify:
      Given:
      A report exists on a given process that includes process specific configuration, e.g. a flow node filter and the version is set to LATEST. (other possibilities flow node target values, TBD anything else?)

      When:
      I deploy a new process definition with breaking changes (the particular flow node filter does not exist)

      Then:
      ??

      Expected:
      The report editor should still work, you should be able to remove the filter

      Open questions:
      Do we need measures to highlight these incompatible configurations?

            Assignee:
            Unassigned
            Reporter:
            Sebastian Bathke
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: