Demonstration – Flow Concepts

I’m going to pick up where we left off in our last demo where I had created a button flow that creates an account based on the name that you input. I’m going to open that up in the designer. And, remember, this is a manually triggered flow that takes a name of the account and then it does a create record. And what I’m going to add is a couple of things on here. I’m going to add on here a action to go ahead and send me a notification if it creates OK.

I’m going to go ahead and also add a query in, a very simple query. Now, I could do this, turn on duplicate detection in the platform, but I want to do my own query to see if the count already exists. So I’m going to do a list record. I’m going to label this as default and accounts. And in the advanced options, I’m going to do a query. And we’ll explain more about the queries a little later in this module. And I want to check to see if that name– I’m going to do exact match for right now– is equal to the name that was created. And what I want to do is I want to do a condition.

So I’m to add a condition action. And what I’m going to do in this is I’m going to actually use an expression to check if that list of accounts returned any records. So I’m going to say if that’s empty. And then if it– it’s going to check against– so I’m using the dynamic panel to bind against the value from that list. And we’re going to check to see whether that is true, so, in other words, if the list is empty. And I’m going to go ahead and rename this because it’s always a good idea to rename some of these things. So I’m going to rename this as CheckIfAccountExists.

And notice that it created an if yes, so, in other words, if it is empty or if it’s not empty, but there’s no actions in them. I’ve already had my actions down here. What I want to do is I want to go ahead and move this into there. So I’m going to drag this up and drop it in there. I’m going to drag this one up also and that’ll connect those in. Now, what I want to do is if this works– in other words, if it creates the account, I want to send the notification. But if it fails, I want to let me know that it failed also.

So what I’m going to do is I’m going to add a parallel branch. And on this one I’m going to send another notification just to keep it simple. Create failed and then I’ll tell them what account name. And now in order for this to run when it fails, I need to go ahead and configure the run after. Otherwise, it will also run when it’s successful and I don’t want this to run when it’s successful. I wanted to run when it’s failed or when it’s timed out. And so now we’ve set that up. Now, just to have some fun, I want to go into this create record. Now you’ll notice that I can’t rename this one now.

I’ve missed my window and opportunity. So you always want to rename the step right away to give it the good name. But what I’m going to do is come down here and find a field that I can put some bad data in to cause this to fail. So we’re going to scroll down and we’re going to go to customer size value. This is normally something you’d pick from a list or bind it to another field. I’m going to enter a custom value. Now you notice if I do something really crazy like try to put my name in there, it’s going to tell me it needs to be an integer.

So it does do some basic checking, but it doesn’t know that 15,000 or 150,000 is not a valid value. So that should help us create a problem when we go to run this. Now I’m going to go ahead and save this. And let’s real quick go ahead and collapse some of these things so we can see things a little bit better. I’m going to collapse the list record. Notice if I collapse that all the way down so we’ll check if the account exists. We’re going to– if not– if no, then we’ll do nothing for right now. And let’s go ahead and run this.

Now before I can run this, I’m going to have to go ahead and activate because my flow is disabled right now. So what I’m going to do is go ahead and go over and re-enable my flow.