When you’re comparing a Flow, it's difficult to work out what’s changed from the XML. Location changes add lots of noise and the XML can seem out of order, making it hard to spot unwanted changes.

Gearset's Flow Navigator makes it easy to see what's new, changed, and deleted. This helps you spot any unexpected differences before deployment. Click the Flow button in your comparison results to get started.

Flow Navigator starts with a high-level overview of the changes to the Flow.

When the comparison source is a Salesforce org, the sidebar shows the version number and status of the Flow in the source org. This helps you verify that you're comparing the Flow version where you made your changes.

Gearset compares the latest version of the Flow in the source org by default. To compare and deploy an earlier version:

Gearset will fetch the selected version of the Flow from the source org, then you can deploy as normal.

Below the version info, the sidebar breaks the Flow into the individual elements and resources. Next to each element and resource is an icon that shows whether it's new, changed, or deleted. This makes it easy to find unexpected changes, such as an element you didn't plan to delete.

You can turn off the Hide no differences toggle to see unchanged elements and resources. Elements appear as unchanged when they are identical aside from location changes.

The main panel in Flow Navigator shows an interactive diagram of your Flow. This makes it easy to explore where new and changed elements fit into your Flow.

The diagram shows the Flow as it exists in the source, with highlighting to show changes:

The diagram behaves in a similar way to Salesforce Flow Builder. You can zoom in and out, and drag to pan around. You can open your Flow in a larger window using the full screen button.

To drill down into the changes for an element, click the element in the diagram or in the sidebar.

When you drill down into an element, the main panel shows the changes to that element. Flow Navigator shows a visual representation of the changes to most elements. This means you don't need to read through XML to work out what's changed.

In this example, we've added a new email action.

Here, we've changed an input value on an email action.

This decision element has a new outcome and a change to a condition on an existing outcome.

We've removed this update records element.

The Flow Navigator is available for all the flows mentioned below as of the time of this writing.
​

Is there something missing or would you like to get access to Flow Navigator?
​Let us know via the in-app chat.