Cloudy standing beneath text that says "Introducing Flow Trigger Explorer."

Introducing Flow Trigger Explorer: View All Your Triggered Automation in One Place

By

When the Flow team talked to our #AwesomeAdmins about what it would mean to retire Workflow Rules and Process Builder, we kept hearing about a recurring challenge: how will admins manage the complexity of a large implementation, where multiple people may have built triggered automation at different times or in different places? The Trailblazer Community has been full of creative solutions to this problem. Some of you have built single “mega-flows” using sub-flows to create order, some have used the Orchestrator beta just to be able to see all related flows in one place, and a couple of you have built entire custom frameworks!

Well, we heard you. We put our heads together with our design team and—after a lot of user feedback, prototypes, and virtual sticky notes—we’re excited to introduce Flow Trigger Explorer in the Spring ’22 Release!

The new Flow Trigger Explorer.

Flow Trigger Explorer is accessible from the Flow Setup page or within a record-triggered flow.

Flow Trigger Explorer lets you view all the flows that will trigger in a particular object/trigger situation, such as when an Opportunity is updated or a Case is created. It gives you a bird’s eye view of all your triggered automation and also lets you dig into specific versions and activate accordingly.

Flow Trigger Explorer showing the Flow Details panel for an individual record-triggered flow.

Did we forget to mention that Explorer will show you your record-triggered orchestrations as well?

Flow Trigger Explorer with a record-triggered orchestration.

But that’s not all!

The other new feature in Spring ’22 that will help you wrangle your record-triggered automation is a little harder to find but no less powerful. If you open Advanced Properties on a flow, you’ll see a new setting called Trigger Order. This allows you to number your flows and ensure that Flow A always runs before Flow B, eliminating the need to combine disparate sections of automation just to control the order of execution.

The Trigger Order field in Advanced Properties of a record-triggered flow.

To get started with trigger ordering, check out our release notes.

Admins with an eagle eye may look at these two new features and see a future where they would be better and more powerful together…

Stay tuned—the Flow team is still hard at work!

Resources

Greenery and text that says, "Why Admins Should Create Flow Tests."

Why Admins Should Create Flow Tests

Summer ’22 introduces a new feature—Flow Testing! The Summer ’22 Release brings admins the ability to create tests for record-triggered flows with Flow Testing. This beta* feature is a great productivity gain for admins! First, you create positive test scenarios for your flow in advance. This includes setting up a test record to use and […]

READ MORE
Computer monitor and text that says, "Automate with MuleSoft Composer."

Automate Your Business Process with MuleSoft Composer

Importing and exporting data is incredibly useful. But as any admin can tell you, it can also be very time-consuming. Data loads often require manual adjustments, ID mappings, and troubleshooting. Your time is valuable, and automating this process can make you a more efficient admin, freeing you up for important feature requests or maintenance. Historically, […]

READ MORE

Have an Idea for a Story?

We are all about the community and sharing ideas.
Do you have an interesting idea or useful tip that you want to share?

SHARE YOUR IDEA