Not sure if I get this, what is the difference with the capabilities we already have since day one to compare the current or (any module) with another model?

Hi Daniël,

Good point – I’m aware of Compare and Merge, but what I’m suggesting is a different workflow:

Compare and Merge requires me to explicitly pick a target and then go through the compare flow. It’s great, but it’s a separate, manual step. 

What I’m asking for is a built‑in “Changes since last publish” view that’s always available for the current module state, without having to select another version.

Concretely, the differences would be:
1. Zero setup: no need to save a baseline or choose a version – it automatically compares against the last published version of the same module.
2. Quick overview: a single panel listing “everything I changed since last publish”.
3. Targeted revert: from that list, I can directly revert/discard specific changes and keep working, instead of running a full compare/merge operation. 

So it’s not about new diff capabilities, but about a faster, more integrated change‑review experience before publish, similar to what developers are used to in Git clients and IDEs.

Hi Ranu,

This capability is already built into Service Studio. It's called "Compare and Merge", and it's available from the "Module" menu ("Compare and Merge with Published Version", Ctrl-M short-cut key, and "Compare and Merge with Another Version or File") and the icon bar ("⇅" icon).

Hi Ranu,

In reply to your second post, you do not need to select a version, that's only the "Compare and Merge with Another Version or File" option. The Ctrl-M short-cut, the toolbar icon and the "Compare and Merge with Published Version" all compare directly with the published version.

The only difference with your idea seems to be that you want only the changes, not everything else. But in that case, you should describe it better.