DMN XML is re-fetched unnecessarily on filter changes

[pedesen]

To Reproduce

Steps to reproduce the behavior:

1. Go to decisions view
2. Select a decision and version from the filter panel
3. Change a filter which is not related to decision or version (for example: "evaluated" checkbox"

Current behavior

• The same DMN XML is re-fetched
• The decisions panel shows a loading spinner and re-renders the same decision

Expected behavior

Whenever a filter is changed which is not related to the decision and version, the DMN XML should not be re-fetched and no loading spinner should be shown in the decision panel.

Environment

• OS: [e.g. MacOS]
• Browser: [e.g. chrome, safari]
• Operate Version: [e.g. 8.1]

Additional context

---

Acceptance Criteria

Definition of Ready - Checklist

• [ ] The bug has been reproduced by the assignee in the environment compatible with the provided one; otherwise, the issue is closed with a comment
• [ ] The issue has a meaningful title, description, and testable acceptance criteria
• [ ] The issue has been labeled with an appropriate Bug-area label
• [ ] Necessary screenshots, screen recordings, or files are attached to the bug report

For UI changes required to solve the bug:

• [ ] Design input has been collected by the assignee

Implementation

:mag: Root Cause Analysis

:thought_balloon: Proposed Solution

:point_right: Handover Dev to QA

• Changed components:
• Side effects on other components:
• Handy resources: BPMN/DMN models, plugins, scripts, REST API endpoints + example payload, etc :
• Example projects:

• Commands/Steps needed to test; Versions to validate:

• Docker file / HELM chart : in case that it needed to be tested via docker share the version contain the fixed along with version of other services .

• Release version ( in which version this fixed/feature will be released):

:green_book: Link to the test case

[ThorbenLindhauer]

Moving into backlog to stay focused. Can be re-evaluated if we get more input on importance.