Feature: Impact Analysis and Version Diff

Feature: Impact Analysis and Version Diff

Objective:
Implement an "Impact Analysis" tool for the RulesEngine admin portal and API, enabling users to quickly see what has changed between workflow versions and assess the impact of those changes on rule execution and outputs.

Requirements:

• Compute a detailed diff between any two workflow versions (rules, expressions, input schemas, outputs, etc.).
• Highlight changes in rules: added, removed, or modified rules/expressions.
• Optionally, analyze how rule changes could affect dependent rules or workflows (e.g., show which outputs or downstream rules may be impacted).
• Provide a backend API endpoint to retrieve diffs and impact analysis results (JSON structure suitable for UI rendering).
• (Frontend) Integrate a component that visualizes version diffs and summarizes impact (e.g., side-by-side or inline diff views, lists of affected rules).
• Optionally: Allow users to simulate test cases across two versions and compare outputs (A/B test mode).

Acceptance Criteria:

• Backend exposes a version diff and impact analysis API per workflow.
• Admin UI presents a clear, actionable view of changes and their impact.
• Users can test sample payloads against two versions and compare results.
• Documentation updated for this feature.

References:

• RulesEngine Wiki

Start with the RulesEngine Wiki and map the existing workflow versioning, backend API, and admin portal entry points; the issue names no files or tests. Define the diff and impact JSON contract before implementation, then verify that the API, UI, sample-payload comparison, and documentation satisfy the listed acceptance criteria.