Gearset Flow Navigator

Salesforce Flow enables teams to create complex business automations with clicks, not code. This approach allows admins to manage more of the business logic, reducing the dependency on developers and increasing project velocity, thus delivering value to the business more quickly. However, deploying Salesforce Flows often poses significant challenges. In this article, we’ll explore why deploying Flows can be tricky and how Gearset Flow Navigator simplifies the process with visual comparison tools for easy, declarative deployments. Join us to learn about tackling Flow deployments.

Challenges in Deploying Salesforce Flows

Deploying Salesforce Flows can be complex, particularly when using change sets, due to several issues:

Dependencies: All referenced items within a Flow must be included in the deployment, but these dependencies aren’t always displayed in the Component Dependencies page.
Versioning: With multiple team members working on different versions of a Flow, it can be challenging to determine which version is being deployed.
Flow Activation: Deployed Flows are initially inactive and require manual activation as a post-deployment step.
Visibility: It’s difficult to see the differences between Flows in the source and target environments.
Rollback: There’s no built-in rollback feature with change sets, complicating the process if something goes wrong.
Destructive Changes: Change sets do not support deploying deletions, requiring manual corrections in production.

While tools using the Metadata API offer an alternative, they typically represent Flows as XML, which has its drawbacks:

Order and Noise: XML elements are often arranged differently from Flow Builder, and the files can be cluttered with minor changes, making it hard to discern actual differences.
Complexity: The XML can contain thousands of lines, making it intimidating, especially for no-code developers.
Version Issues: The Metadata API may return the latest version of a Flow, including drafts, which can complicate deployments.
Activation: As with change sets, manual activation of Flows is required after deployment, often leading to complaints if this step is missed.

A New Solution for Salesforce Flow Deployments

Despite Flow Builder’s user-friendly design for no-code admins, deployment can still be a challenging and frustrating experience. This affects the entire team and the broader business. Gearset’s new Flow Navigator addresses these pain points with industry-first functionality designed to simplify Flow deployments.

Key Features of Flow Navigator

Visualize Differences in Flows Between Environments:
Gearset’s Flow Navigator offers a visual interface to compare source and target environments, such as Salesforce orgs or Git branches. The tool highlights new or changed elements in the Flow, making it easy to identify changes. A sidebar provides a detailed breakdown of changes, allowing users to quickly spot any unintended modifications.

Detailed Breakdown of Changes:
Users can drill down into specific Flow elements to review changes in a simple, tabular format. This ensures that only the intended changes are deployed.

Switch Versions with a Click:
The tool allows users to compare different versions of a Flow, which is particularly useful if the latest version includes in-progress work that shouldn’t be deployed.

Automatic Flow Activation:
Gearset can automatically activate Flows post-deployment, eliminating the need for manual activation steps and reducing the chance of errors.

Flow Deployments that Resemble Flow Builder:
Flow Navigator provides a more familiar and accessible deployment experience for no-code developers, avoiding the complexity of XML. Gearset offers a 30-day trial, allowing users to explore the platform and its Flow Navigator feature at no cost.

By addressing these common challenges, Gearset’s Flow Navigator ensures smoother and more reliable Flow deployments, enhancing the overall efficiency and productivity of teams working with Salesforce.