Future of Lightning Flow
On Monday, 11/6/17, I was invited to join a small group to meet with Salesforce’s Flow team at Dreamforce. The Lightning Flow Builder Happy Hour was to thank some of the community members who have participated in helping the Flow feature grow at Salesforce and give a sneak peek in what’s to come.
The following information is super-duper-Safe-Harbor/Forward-Looking-Statements. I would love to be sharing things that are “For Sure” going to happen, but the fact is that this is very much an ebb and flow (ha!) process (double ha!). Scott Kozinchik asked us very nicely not to share any pictures. I’m free to talk about it, the team simply wants to make sure none of the images would be taken out of context.
Some Flow Background
Here are some important things to know about the future of Flow:
- The Flow Builder is currently built within Flash
- Browsers are aggressively moving to not allow Flash in their applications
- The Flow Builder must be rebuilt
This is where I’m obligated to make a Six-Million-Dollar-Man joke: We can rebuild Flow. We have the technology. We can make Flow better than it was. Better, stronger, faster.
To be clear, a lot of this is going to be about the look and feel of the Flow Builder and not underline engineering changes.
They have five categories the team is considering as part of this rebuilt;
- Visuals & Aesthetics
- Ease of Use
- Document & Understand Flows Later
- Testing & Debugging
- More Flow Engine Capabilities
From that, here’s some general examples.
- A familiar interface. By now, most of us has seen Engagement Studio in Pardot and Journey Builder in Marketing Cloud. The thought is to borrow elements (ha) from those tools so the feel of the new builder is similar. Pretty icons. Informational icons. Clear lines. Very obvious start and stop images. The team wants someone to come to Flow and immediately feel comfortable because the look is similar to other tools.
- Improve debugging tools. Anyone who has built a Flow knows it can be arduous at best to debug a Flow. So the team is thinking of how they can add to the User Interface to help with the Debug process. An example would be allowing you to specify values for your input variables so we don’t have to use variable defaults just to debug
- Documenting for now and the future. There’s been a few times I built something. Came back and thought “What the heck was I doing here.” The team is looking at ways to allow us to annotate our Flows and potentially group a selection of elements together to make really large flows easier to navigate and review.
- Ease of Use. The team wants to make Flow more accessible to everyone. I’m no going to provide specifics, but this is a great goal for this tool.
I know I didn’t provide many specifics. Part of this is intentional, and part is because I honestly don’t remember some of the details. I’m sorry Scott, but I purposefully didn’t take any photos so I wouldn’t be tempted to share them. Now I wish I took some so I can recap a bit better.
Don’t expect this changes soon. We’re not talking about the Spring or even Summer releases. This is a huge overhaul of Flow. The good news is the team has the resources to do it. The bad news is it’s going to take quite some time. The also good news is they have a team that is very eager to listen to user’s feedback. They want to see samples of complicated Flow we’ve built. They want to hear our use cases of what would make our lives easier in a new builder. These are good things.
I did ask Scott to come on the WizardCast to share more details when the team is ready. So stay tuned to the podcast for more insights.
What would you want the new Flow builder to look like if you got to build it? Remember, we’re talking User Interface details and not engineering changes like being able to compare collection variables (which would be amazing). Let me know in the comments.