Flow Diff

What differs between two tenants, two states or two artifacts, file by file.

When to use it

• Does PROD have the same content as DEV for this artifact, and what differs if not?
• What changed between this flow and a copy of it under another ID, or an earlier state of itself?

How it works

1. Pick the artifact on one side, by typing any part of its name, or by choosing the package first. The other side then offers the same artifact on the next tenant.
2. The page lists the files that differ. “Identical” is decided on content, not on version numbers: two sides can be identical with different version numbers.
3. Open a file for a line-by-line comparison. Flow models are sorted first, so you see the real change and not the reordering the flow editor does on every save.

Swap the sides with one click. The comparison is part of the URL, so you can send someone the link to exactly this diff.

Both sides come from the artifact sync of their tenants. The cards above the diff say when each side was read.

Community and enterprise

The community license compares the current state of an artifact or the one before, on either side. The enterprise license offers every recorded state.

Good to know

• Each side is as of its tenant’s last artifact sync, which may be hours apart.
• Binary files are reported as different, but not shown.
• Line numbers in a flow model refer to the sorted XML.

Credits

An old blog post about this feature: Flow Diff tool for comparing Cloud Integration flow versions.

Special thanks to Raffael Herrmann! This feature is heavily inspired by his blog post.