Stitcher for Podcasts

Get the App Open App
Bummer! You're not a
Stitcher Premium subscriber yet.
Learn More
Start Free Trial
$4.99/Month after free trial
HELP

Show Info

Episode Info

Episode Info: Today on the Salesforce Admins Podcast, we’re joined by J Steadman, Senior Solution Engineer at Salesforce, to talk through flows, processes, and the easiest way to move things from workflows to Process Builder. Join us as we talk about the tools in your toolbox and how to view them as different things for different jobs, getting technical about workflows, Process Builder, Flows, and more. You should subscribe for the full episode, but here are a few takeaways from our conversation with J Steadman. J’s winding path to becoming a Solution Engineer. J is a Solution Engineer at Salesforce, but what exactly does that mean? “I help people who are not yet Salesforce customers become Salesforce customers by building out demos of our technology to their specific requirements,” J says. The way he got to where he is now is one of those classic accidental admin stories we hear so many times on the pod. He didn’t get his first sit-down office job until he was thirty, working the front desk for an organization that happened to use Salesforce. He soon found himself as an admin, and that lead to a career as a Salesforce consultant. The next stop for J in his career path was as a product manager for an enterprise customer with about 2,000 licenses in a big, shared, multi-tennant org with thirteen business units. From there it was a matter of time until he came over to Salesforce, first as a Success Specialist and now in his current role as a Solution Engineer. “It’s really fun in that for our strategic retail accounts, we’ve got a longer deal cycle so it’s not turn and burn,” J says, “so I get to spend time with these customers, learn their use cases, and actually present them functional technology before they even implement anything.” Why you need to transition from workflows to Process Builder. Right now, J is focused on how to transition workflow rules to Process Builder. “We had somewhere around 80 workflow rules that were all active on the opportunity object,” he says, “and I was tasked with not only taking those and migrating them over to Process Builder but also to add a bunch of new logic and functionality.” The fact is that in today’s Salesforce environment, workflows are limited—it can’t do everything that Process Builder can do. For admins looking for fast and efficient automation, Process Builder is the answer, but that can put legacy admins in a difficult spot where they’re split between the new solution and their old automations in workflows. The biggest challenge that J has identified is order of execution. If you have a dozen workflow rules all firing on the same criteria on an object, you aren’t able to control the order in which those rules fire. Between Process Builder and Flow, that order can become very important as we build new solutions because legacy workflow processes can start to get in the way. While you can do all kinds of things to make things work, “when I look at the kinds of orgs I work...
Read more »

Discover more stories like this.

Like Stitcher On Facebook

EMBED

Episode Options

Listen Whenever

Similar Episodes

Related Episodes