Version Compare
Three-way diff. Permanent URL. One click from a review thread.
The Compare page produces a structured diff between any two ruleset versions. Every comparison is deep-linkable — drop it into Jira, Slack, or a review email and the recipient opens the exact same comparison. No PDFs. No "send me the link" follow-ups.
Three comparison views
Changes view
Shows only what's different: added rules (green), removed (red), modified (yellow). Row-level diffs for decision tables. BAL statement diffs for action rules. The reviewer's primary view.
Structured view
Both versions side by side as their fully resolved logical structure. Unchanged content appears at reduced opacity. Used to understand the full context of a change, not just the delta.
Raw view
Underlying JSON diffed at the field level. Escape hatch for debugging serialisation issues, verifying metadata-only edits didn't touch rule logic, or consuming the diff in external tools.
Every comparison is a permanent URL
The URL encodes the full comparison state:
/compare?ruleset=<id>&base=<versionId>&target=<versionId>&view=changes
Drop it into a Jira comment, a Slack message, or an email. The recipient opens the exact comparison — same ruleset, same base, same target, same view. No "send me the link" follow-up required.
Branch Center — three-way merge
For branch-level comparison (feature branch vs main before merging), use the Branch Center. It shows three-way merge context: common ancestor + both branches, with conflict highlighting where both sides modified the same rule.
/branches?tab=compare&ruleset=<id>&source=main&target=<branchId>
The three-way context explains why a conflict occurred — not just that it occurred. You see what main changed, what the branch changed, and what the original was.
ODM Change Report parity
ODM Change Report
Generated PDF document; no link sharing; requires Rule Designer IDE
DecisionManager Compare
Live, interactive; permanent URL; accessible to business reviewers in the browser; no IDE install