Validating Flow Input Part 2: Special Cases

Hi there Flow Friends! In my last post I talked about validating user inputs. Several folks sent me messages asking about validating inputs that don’t have built-in validation or making the validation dependent on multiple selections. We can do that by building our own validation process using a decision loop. Let’s get started!

Validating Flow Input : An Ounce of Prevention

Last time we talked about handling those pesky “Unhandled Fault” errors in Flow. After you’ve been tracking your errors for awhile you’ll start to notice a pattern. Most of your errors will be from either Bad Data or Permissions issues. We’ll talk about permission issues another time, but for now lets focus on preventing those data issues.

If we’re creating flows with user input, we have to help our users enter the data correctly. There’s nothing worse than having your beautifully crafted flow come crashing down because your user put 11 characters into a text box when the field can only hold 10 characters. So how do we keep this from happening? Input validation to the rescue!

Handling the “Unhandled Fault” in Flow

When you start doing a little work in Visual Workflow aka “Flow”, you are going to run into the dreaded “Unhandled Fault” sooner or later.

How to Supercharge Your Salesforce Knowledge, Like a Dude

Salesforce is my job, it’s what I do 8+ hours a day, 5 days a week. And I LOVE it!! But many of you wear multiple hats – who has time to learn all Salesforce can do, keep up with new releases, figure out formulas, etc..? What if I told you that you can supercharge your knowledge of all things Salesforce in 10-15 minutes a day, without even trying?

Here’s the secret.. read the Success Community. Hmm.. not much of a secret you say? Everyone knows there’s lots of good info in the Success Communities, you say? Yes – but how often do you read them? Do you only go there when you have a problem, hoping for a quick fix? If so, then you are missing out on a golden opportunity.