Salesforce Certified Platform App Builder – 5 – Business Logic and Process Automation Part 6
- Introducing the Lightning Process Builder
Introducing the Lightning process builder. In order to find the Process Builder, just simply search on the word Process and Setup. And down in the Setup menu you’ll find the Process Builder link. And that’s under process automation. And so we talked previously about flows in the Cloud, Flow Designer and Visual Workflows in order to do Stepbystep Wizard type interfaces. Now, another functionality available in Process automation is the Process Builder.
And so from the exam guide for this platform, App Builder certification, one of the specifications that they state that you need to know is that given a business requirement, recommends solutions to automate business processes using the Process Builder. And so the first screen that we come to when we click on the Process Builder menu item and Setup is the screen that shows my processes.
And it’s a welcome screen to explain what the Process Builder is. And then as well, some helpful links such as using the Process Builder documentation, a Process Builder Overview video, and then as well, learning about the Process Builder using an interactive learning path called Trailhead. And so Salesforce Trailhead does give you useful hands on activities that you can do to further your understanding of these topics. But we will go through the Process Builder the next few lectures so you become familiar enough for what’s covered on the exam. And then as well, you can explore doing other trailhead trails if you’d like, in order to get more hands on experience. It’s always a good idea to get whatever hands on experience that you can.
There’s an example as well here as far as what you can do with the Process Builder. And what happens here is it’s saying that you select an object such as an opportunity, then you define your criteria. And that criteria in this example is that it starts the process when the Opportunity stage is closed one and its amount is greater than $500,000. And then you can choose what to automate. And in this example, it’s creating a contract and associated it with the Opportunities account. And then as well, you can congratulate the owner by posting to the Salesforce Chatter group and create a follow up task scheduled to execute six days after the Opportunities Close day. So we’re going to go through the steps of creating this actual process in the Process Builder.
That’s our first process that we create in order to get some hands on experience. So I’m going to click new. And so we’re going to start this process by entering in the name for this process. And then I’ve tapped over to fill in the API name and then we can enter in a description and then you select when the process starts. And so we’re going to select that this process will start when a record changes and then click Save. So now that we’ve entered the preliminary information on this process for the Process Builder, we now get into the interface of the Process builder so now, in the next lecture, we’re going to continue on and complete the task of creating this basic flow in the lightning process. Builder.
- Creating a Basic Process in the Lightning Process Builder
So now we’re going to create a basic process using the Lightning Process Builder. And so we’re in the Process Builder, the one opportunities process that I created previously in the previous lecture. We’ve got our start point of this process and then we click on the Add Object link here and this is where we specify the object. And then we as well specify when to start this process. And so I’m going to locate Date, the opportunity object. You could either click and scroll down to find or you can start to type to start to narrow the results. So I’m going to select Opportunity and then we start the process either only when a record is created or when a record is created or edited.
Now, in the grand scheme of things in our example that we’re going to build over this lecture in the next, we’re wanting to deal with opportunities when they are one. And so we don’t want this to only fire when an opportunity is created, but also every time it’s edited so that we can check to see if the opportunity has been one. We want to do some sort of actions after that. So then you can go on the advanced options here to see recursion allow processes to evaluate a record multiple times in a single transaction. And so one thing to keep a note of or a mental note of is that if you select this, this process can evaluate the same record up to five times in a single transaction. It might reevaluate the record because a process workflow rule or Flow updated the record in the same transaction.
And so that means that there may be some workflow or some other process or flow that flips an opportunity to the one stage. And so then this would reevaluate again in the same transaction to see if maybe it wasn’t a one opportunity, but it will flow back through again and allow you to check a second time. But for now we’re not going to check that. But you may be asked like how many times can you go back through in the Process Builder? And that’s up to five times in a single transaction. Now that we’ve selected our opportunity and that we’ve selected that, we want this process to start when a record is created or edited, let’s go ahead and click Save. And so we’ve saved that specific element in this process to signify the object of opportunity.
So that’s a consistent thing you’ll see in the Process Builder is one of the first things in this diagram will be what object this works on. Then you want to add the criteria. This is a decision element and we want to add the criteria to decide if this opportunity is one or not. And so then for the criteria for executing the actions that will happen after this and here’s immediate actions when you follow the example here of if this criteria is true, we want to either have the criteria be when conditions are met or when a formula evaluates to true or no criteria just execute the actions. Which would mean regardless of what happens, it’s always going to do these actions. Now we need some conditions to be met and so we want to set these conditions down here below. So I’m going to scroll down a little bit to see this a little easier. So for the field, we can click on this to find a field and it defaults to opportunity because we selected opportunity here previously.
And so I’m looking for the stage of the opportunity. So I typed that in to narrow down my results. I’m going to select Stage and choose that for the field, for the criteria or the conditions for this criteria. And so when the opportunity stage equals there’s a lot of other options here for the operator, but I want to look for when the opportunity stage equals and it’s a picklist value of closed one, I want to do an action. And so you can do these conditions and add multiple rows to do ands, or ors and this can get very complex, but right now we’re just going to leave this to where all of the conditions are met, which will be all of this one condition and click Save. In the next lecture. We’re going to customize this further to get a little more advanced in the Process Builder.
So now we’ve got the object that we’re working on, which is opportunity, and then this decision element here to see if the opportunity has a stage of closed one. You can do additional things in the Process Builder. If it’s not, which we don’t want to do in this example, we just want to deal with the true condition. So basically if it’s false, it’ll just stop and it won’t do anything. It evaluates and says, oh, the opportunity is not closed one, do nothing and move on through the next thing in this transaction, whatever process automation remains. But if it’s true and it is closed one, we want to add an action by clicking Add Action. And so in this example, to start off with, what we’re going to do is we’re going to select an action type. Now, these action types may be on the Process Builder exam. And so if you remember, there’s certain actions you can do with a workflow rule. There’s four specifically. We looked at those before and that has to do with email alerts tasks, outbound messages and field updates. Well, in the Process Builder you can do more than that. You can actually have action types of calling it some Apex code or creating a record or sending an email alert, which is like what you can do in a workflow rule. You can launch a Flow, which is an important functionality and helpful. You can also post a chatter. You can launch other processes, you can perform quick actions, you can submit records for approval, for an approval process and you can update records. It’s here with update records that you can do cross object updates and do greater functionality than you can through a workflow rule as well. So the thing to keep in mind with the Process Builder is that you can do more actions, you can get more granular in some of the criteria and the branching and get more complex behaviors. And then as well, some of the things you can do here you cannot do through a workflow rule. And so one of the things that I want to do is post a chatter because you can’t do in a workflow rule but you can do in a process. And so I’m going to call this action name congratulate on Chatter.
And this asks me where I want to post this to. I want to post this either to a user’s chatter feed or I could post to a chatter group or I could post to this particular record and this will change depending on what I select. If you notice with this record, I could do a message and do a merge field. And so for the opportunity, I could do the Opportunity owner, for example. And you notice if you select these with the arrows next to them, you can keep branching further. I’m looking for this person’s name, so I’m going to select their username and choose that. Then I’m going to finish out this message by typing in some text. Then I click save. And so now what I can do is I can activate this process and so activating this process automatically, deactivates any other active versions.
This is a new one, so I’m just going to click Confirm and not worry about that. I’m going to click on View All Processes to see now that this is my list of processes in my I have the one, which is one Opportunities. I’ve got the one version and we’re going to get into more details on specifics of this opportunity and branch out into when it’s greater than 500,000 in the next lecture. But for now we just have it to where when an opportunity is one, it posts a chatter message to the opportunity records. So if I go back to set up, I’m going to go to an opportunity and close it as one. And so for this Phyllis Cotton Abbott insurance opportunity, it’s in the prospecting stage. So I change this to closed one and click OK. And then click save. Now, in order to see the Chatter feed, I’ve got to click on Show feed. And so you’ll see here that there’s a few things in my chatter feed where I changed the closed date. It closed to today because it was closed one and so it reverted backwards some because when I’m recording this, it’s before what the closed date was set to and so it’s actually set the closed date to today. It’s showing that I’ve closed this opportunity as one.
The thing to really highlight, though, however, is this chatter post. It says Congratulations to and then my username, because that was a merch field that I selected. I could have selected the user’s name. Instead, I did the username. So that’s a fake email address that I’ve been using. The chatter matches just saying congratulations to me for closing this opportunity. So if you wanted to go in, you could actually edit this flow. You could actually go in and edit this process by going back into Setup and clicking on Process Builder. And then in order to make an edit, another thing that’s important to highlight here is when you click on this, you can deactivate this. You cannot edit an active flow. You’ve got to create a new version. But even though I’ve been activated this process, it’s still read Only. It’s saying that this process is in Read only mode because the status is active or has been active in the past. You can’t edit this process, but you can create a new inactive copy. So I can’t actually do an edit of this process. I’ve got to clone to create a new version. So I want to save a clone as either version of the current process or make an entirely new process. I’m just going to do a version of this and you could change the description here and click Save. And so what I want to change is this congratulate Merge field here. I could select a different field. So I’m going to do first name and choose that. And then I’m going to replace the username with the user’s first name or the owner’s first name, I should say. And then what I’m going to do is I’m going to do a space and then put their last name in.
Now, I happen to know that the API name for Last Name is this. I’m going to click save. Then I’m going to activate this and confirm. Now, if I view all processes, we’ll see now that I’ve got two versions of the One Opportunities process and so the Active one is version two. I could make version one active. And so as you have these different versions, you can go back and forth through time and activate different versions. So if I go back to set up and if I go to another opportunity and so let’s go to the Example Name Opportunity and let’s do a stage of Closed one so that it meets the same criteria as well. And click OK. And click save. We see in the feed here that it’s congratulating me for closing this opportunity. Now, I failed to add a space after the Merge field for the Last Name name and so I could go in and clone a version. So in the next lecture, we’re going to adjust this process further by cloning a new version of it and activating it and we’ll get into more advanced features of processes so that we can then get back to only doing these actions once an opportunity exceeds $500,000 or more. So stay tuned for the next lecture where we create an advanced process.
- Creating an Advanced Process in Lightning Process Builder
So now we’re going to create an advanced process in the Lightning Process Builder. And we’re going to do that by deactivating this current version two of this process that we built previously, or actually rather than even deactivating at this point, we can just clone this version to create a new version of the current process. And so I’m going to call this advanced one Opportunities and then click Save. And so now if you recall previously we talked about the we need the ability to only fire this process when an opportunity is closed in one, but also additional criteria that the opportunity has to exceed $500,000. And so for our conditions, in order to execute the actions in this process, we’ve got our opportunity stage name equal to a picklist value of closed one.
And then we want to add an additional row and have the opportunity amount exceed $500,000. And so for the operator, we want it to be greater than and then the currency amount of $500,000. And for the conditions, we want both of these conditions to be met. And so we want to leave this to be all of the conditions are met. So this is an and so if conditions one and two are met, we’re going to save that other criteria that we had as far as actions that we wanted to perform, we want to do an additional immediate action of creating a contract that’s associated with the account that this opportunity belongs to. So for the action type, previously we did a post to Chatter. Now another action that we can do through the Process Builder that you can’t do through a workflow rule is create a record. And so for this action name, we’re going to call this Create a contract. And so for the record type, we want to find a record type of contract. And that’s basically the object that we’re wanting to create. And then down here to set the field values, the account ID that is defaulted and we can’t change that. That’s because contract is in the master detail relationship with account and is the child object of an account. And so the value needs to be that of a reference to the account that the opportunity belongs to.
And so we’re going to select the account ID that this opportunity belongs to and choose that. And you notice that the type was a reference. We could potentially do a formula as well and build a formula. So I’m going to use that formula instead. And then as well, you can set some field values. Here the currency ISO code. We’re just going to do US dollars and then the status, I’m going to give it a status of Activated and click Save. So now we’ve added the action of creating a contract. We click show more, we can see the two immediate actions congratulate on Chatter and then now as well, creating a contract. All right, so let’s go ahead and let’s activate this process.
Now this will be version three and it’s Active. If we go back to view all processes and expand this, we see version three and it is the Active version. So now if I go to an opportunity, let’s go to this opportunity here, pyramid emergency generators. And so it’s not in a closed status, I’m going to change the amount to $501,000 so that it will meet the criteria once we set this to closed and one. And so the stage closed one and clicking okay and then save. So as you can see, we’ve thrown an unhandled exception or an error that happened here so the record could not be saved. And so when that happens with a process or with a flow and actually behind the scenes, one thing to mention is that processes you build in the process Builder are known as flows as well, or flow definitions.
And so it’s kind of confusing. And I may have referred to some processes in these lectures as flows, but it’s saying that a record couldn’t be saved and a flow trigger failed to execute the flow with version ID, et cetera. And so what happens whenever you receive one of these errors is you’ll receive an email with further troubleshooting information. So let me bring up that email real quick and show you what went wrong with this. Here’s the actual email and it’s saying that the insert failed. And so the problem here, or the thing to know, to really highlight is on this error insert, it says choose a valid contract status and save your changes. For a new or cloned contract, choose Draft and activated. Contract status can’t be edited. And so previously when I created this process, I set the status of the contract to Active. And so I need to change that to Draft, otherwise this won’t possibly work.
So going back to my salesforce instance here, and here’s an example of where I would want to do an error screen to handle these exceptions so that I could provide the user with further guidance. And so I could tell them in that example that they need to go back and change this to a draft status instead of Active. But really I need to change that in my process. And so I’m going to go back to processes and set up. We’ll try and correct this and see if this will work. And now if I go to my version three, I’m going to clone in order to do edits, you see how you can have a lot of versions of these processes over time. And so for this action, it’s to create a contract action, I need to change the status to Draft. And so now I’m going to click save. And now I’m going to activate this process.
And so now if I go back to set up, and if I go back to my opportunity that I was on here, let’s try and change that so you see the amount is the 501,000, the expected revenue is 50,100. That’s because the probability is 10%. If I change this to closed one, this should work now and change this expected revenue to 501,000 because it’ll be the amount times the probability and hopefully we won’t throw an error. So I’m going to click save. And so now I’m getting a validation error, my account number. And so the account number error has to do with a problem on the account level. So if I click through on the account, this is kind of an obtuse validation rule that we’re hitting here. I could just disable that validation rule, but I’m going to go ahead and change that account number to seven characters long and save that and then we’ll go back to our opportunity and try this again.
And so probability closed one, okay, and save. And so now finally we’ve cleared all our errors and validation rules and you see that we’ve got our congratulations message on Chatter and then as well, we should see a contract on the account. And so let me go to the account again. And that’s one of the reasons that the account validation rule fired, was because we were updating the account by adding a contract to the account. And so we don’t have contracts on the related list on the account level. And so I’m going to edit the layout of the account and go to related lists when drag contracts down into the related list section of the page, layout and release and then save and then yes to confirm the customizations.
And now finally we go back to our account for Pyramid Constructions and we see the new contract that’s just been generated and that was via the process. So it’s very cool functionality that the Process Builder can give you. And this was done dynamically whenever we closed the opportunity as one. And the opportunity revenue amount was over $500,000. So this is a good example then of an advanced process that we just created here in the Process Builder. And so you could do other things through a process and you see now we’re on version four and you can begin to get a sense of how this is more of an Iterative approach when you’re building processes and then over time, you can do testing and troubleshooting until you get everything just right.
And so I want to clone our active process here and you notice that we’ve got immediate actions, but we don’t have the ability to do time based actions. I’ll show you why that is here in a moment. But let’s clone this to do a version five and let’s save this the way that we can get some time based actions here. So let me show you how to do this. If we click on our decision element here for Opportunity One and scroll down in this advanced option, if we drop that down, this yes checkbox is not checked. And so it says, do you want to execute the actions only when specified changes are made to the record? And so hovering over that, that tells you that when you select yes, the actions are executed only if the record meets the criteria. Now, but the values that the record had immediately before it was saved didn’t meet criteria. This means that these actions won’t be executed when irrelevant changes are made. So it’s usually a good idea to go ahead and check yes on this advanced option here.
What that will do then, is that it will update this area here. This will give us scheduled actions as well. So not only do we have the immediate actions that we can do as far as congratulating on chatter, and then also we have the creation of a contract, but we have the scheduled actions that now appear. Now, real quick, while I’m here, I’m going to adjust this to add a space in this chatter message because that’s bothering me, frankly. And clicking save. And now we’re going to do our scheduled action and setting a schedule of six days after the close date. Now that we’ve set our schedule, we can do an action with that scheduled time lapse. We’re going to add the action. We’re going to create a record. And for this record, we’re going to do a task. Now, we’ve selected the task. Here’s some of the values that we need to select. Now, the currency ISO code, that’s just something that’s by default on most all records and isn’t really it doesn’t come into play a lot of times, especially on a task.
But we’re going to assign this task. And so part of the criteria we had in the example of this advanced process is to create a follow up task six days after the close date. And so I’m selecting the ID of the owner of the opportunity. And so I’ve selected there, that was the Opportunity owner ID field there. You hover over that to see what I selected. And then for the priority on the task, we just want to use a priority of low and then the status we’re going to set it to not started and click Save. And so now we’ve added our scheduled action for this follow up task six days after the close date of the opportunity. So if I activate this and confirm if I go back to set up and go to an opportunity, we want to do another opportunity and make sure that it’s over $500,000 and do it as closed one. Now I’ll show you that follow up task and where that’s set. So if we edit this, so now I’m going to make this a larger amount so that it will trigger this process. And then the closed date, I’m setting that to today or sometime in the future. And then the stage, I’m going to set that to closed one and I’m going to click Save and so now the thing that I want to show or explain is with this time based action here from a process, it actually does not display in the time based workflow queue. And so if we do a search here, we won’t see this assigned task pending in the time based workflow.
And that’s because that shows workflow rules and not processes or flows. And the way you get to or see things that are set in the future from a process or a flow. If you search for the word flow and set up and go to the flows section under workflow and approvals, here’s how you can look into the future. Here’s all the different flows that are live in our own salesforce instance right now. And if you scroll down here, here’s a few paused and waiting interviews. And so these are items that are waiting to be fired. And so if you click on one of these you can view it.
And so this is the flow name of one opportunities and it’s this Flow interview detail. It’s number six here and the pause date and the version. And so this is actually the only way currently that you can see upcoming tasks being assigned to people in the future. It doesn’t give you a lot of details around when that’s going to actually fire, so it’s not super helpful. I found something in the Success community around a suggestion or an idea as to making those time based assignments for tasks and other future scheduled activities available in the time based workflow queue. But for now you can only get to it from the Flows section of Setup.
Okay, so we’ve done a lot now through our different processes, we’ve built through the Process Builder and as you see, I’ve got several different versions and the most recent one is active. And so now in the next lecture we’re going to do a helpful practice activity and we’re going to be using a process in order to call and trigger a flow. And that way you’ll begin to understand how processes and flows can work together to add more or extended functionality for your workflow and automation needs.
- Workflows vs. Flows vs. Process Builder – What to Use When
Okay, so in this lecture we’re going to talk about how to decide which of the automation tools to use in salesforce. So I’ve called this workflows versus Flows versus Process Builder and it can get very confusing in order to know which of these tools to use in certain scenarios. And I wanted to point out a help topic that’s available to you and I’ll make this available as a link in the resources section, section of this lecture. But if you just search for which automation tool do I use and then the term salesforce, you should be able to pull it up via a search engine as well. And so I want to scroll down to this table here in this help topic. That’s very helpful.
These are automation tool features and this table shows four different automation tools. There’s the Process Builder, there’s the visual workflow which I’ve been referring to as Flows a lot of times in this course. And then workflows that would be Workflow rules would be this third column and then finally approvals or approval processes. So this gives you an idea as to which of the four solutions should you use depending on what your requirements are. And so we’ve got at the top here things such as the complexity and then if it provides a visual designer, the browser support and signifies when these different things can be started, if they support time based actions and if they also support user interaction. And then the supported actions below such as calling Apex code, or creating records or invoking processes or deleting records, or launching a flow, posting to chatter, sending an email and sending outbound messages without code, submitting for approval and updating fields. So I highly recommend that you become familiar with this chart here, but become familiar with it and understand it in practice, in creating various scenarios for yourself and then figuring out why certain tools are best for certain situations.
And so some of the high level things, though that may appear on the exam, would be one of the primary things that help you decide whether to use a Workflow rule or the Process Builder is if you have just a single if then statement, the workflow rules will be adequate for that. But if you have multiple if then statements you want to use the Process Builder and then as well, if you want a visual interface to design your automation around, then you’ve got to use either the Process Builder or Visual Workflow. And workflow rules do not have a visual designer component.
And then as well, understanding when these different things can be started is helpful such as the Process Builder, that’s when a record is changed or when it is invoked by another process. So one process can invoke and call another process, for example, whereas a workflow will only fire when a record is changed and then with a visual workflow that does enable or supports user interactions. So therefore it can be started when a user clicks a button or a link, or when a user accesses a custom tab. Also as well, a visual workflow can be called and started by a process. And then also Apex can call a visual workflow as well. And then as well, we looked previously at what these different things can do. And if you recall, like a workflow, it can’t create records, it can create a task which is a type of record. So that’s the only record that it can create.
Whereas both the Process Builder and Visual Workflow can create other records for different objects and different record types. And so then another thing to note is the visual workflow often just referred to as Flow or Flows. It’s the only automation tool that can actually delete records. And so as well as time progresses, this table will be updated. Like right now, you’ll notice that in Pilot is the ability to launch a Flow can be done through a workflow rule that’s in a Pilot project you’ve got to contact salesforce support and they’ve got to enable that in your own organization if they allow you to be part of their pilot program. And so over time, Workflow rules will be able to launch a Flow as well. And then as well, through our previous practice activities and lectures that we worked through, we posted a chatter from the Process Builder and showed that as well.
And then as well you can send email alerts for three out of these four. But for the visual workflow you can send other types of emails as well. So when it comes to figuring out workflows versus flows versus process builder, the rule of thumb is try to use a workflow that seems to be the lowest common denominator and the easiest to work with and is the most bulkified in that it doesn’t bomb out with too many records when you’re doing bulk operations with workflow rules. And so if you have a single a thin statement and you just need to do certain actions that are supported for a workflow rule, then that’s the way to go. But if you have a more complex requirement, then you need to explore Process Builder versus a Visual Workflow. If it’s something that the user needs to interact with, or if it’s a screen based wizard, then the visual workflow is the way to go.
If it’s something that’s more just multiple if then statements and when a record is changed, then the Process Builder will be adequate as well. And then if none of these fit the bill for what you’re needing to accomplish, that is the line at which you’ll need to cross over into Apex code and creating triggers and potentially Apex classes as well, which goes beyond the scope of this exam and this certification. But knowing where this line ends is very important. And then what the differences are between the Process Builder Visual Workflow and Workflows as well. And then as well, approvals do have a certain amount of automation around them as well. We don’t talk a whole lot about approval processes in this particular course that’s more covered in the admin and advanced admin. But there is some in this course that on the exam related to approval processes. But don’t worry about that so much as it relates to this help topic of which automation tool do I use? That’s why I chose to call this workflows versus Flows versus Process Builder. And so in the next lecture we’re going to be getting into another concept that has to do with the ramifications of field updates and the potential for cars.
- Ramifications of Field Updates and Potential for Recursion
So one of the things in the exam guide that it’s specifically spelled out is that you need to understand the ramifications of field updates and any potential for recursion. Now I’m going to demonstrate what that is and how that works and how it relates to filled updates. And so a thing to bear in mind is that you can do filled updates from workflow rules. And so I’ve, I’ve done a search and set up for workflow rules and clicking on that brings up my list of all workflow rules in my own organization. I’ve got my currency updater. That is a managed package. It’s an app that I installed previously. And the other workflow rule that we previously created was for an account and it’s active in our here. And it’s a workflow rule for accounts that have a rating of Cold.
And if I click on this, it’ll bring me to the details of this workflow rule. And I’ve got the evaluation criteria, which is when an account rating equals Cold, it performs these particular actions. These actions are the first one is an immediate one of an email alert and it sends an email alert to someone that this account is rated Cold. And then there’s a one day rule trigger to create a task. Now I want to add a field update to this workflow rule and then we’ll get into the possibility for recursion and reevaluating workflow rules as a result of field updates.
So if we click on Edit, we could add an additional workflow action to add a filled update. I’m going to select an existing action and I’ve previously created this. As far as a filled update, you notice here I’ve got several different filled update actions available to set the account, either Cold or Warm, for instance. And so I could actually select multiple actions and click Save. And these are conflicting things as far as these filled updates are set to conflict with one another.
So that’s a bad idea. And you could actually get caught in like an infinite loop here if you were to have other workflow rules looking for other conditions such as rating equals Warm, for instance, instead of Cold. Let’s say if we were to edit this, the thing that I really want to highlight here as it relates to recursion is this checkbox that says reevaluate workflow rules after field changes. And you can check that. And what that does is that if the field update changes the field’s value, all workflow rules on the associated object are reevaluated.
And then any workflow rules whose criteria are met as a result of the field update will be triggered. And so this is kind of an excessive example here as far as these filled updates firing and setting things back and forth. I’m not going to go through the process of testing this out or trying to reach a limit or cause an error or break anything. But the main point I wanted to make was just understanding the ramifications of field updates and potential for recursion, and just that you have the ability to reevaluate workflow rules after field change and fire additional workflow rules. So what you want to avoid is this ping pong effect or an infinite loop, if you will. And you could do this inside of one workflow rule, or maybe inadvertently through multiple workflow rules. You could have one where the rating equals cold and you want to flip it to warm, and then a different workflow rule that’s checking to see when an account is rated warm and flip it to cold. So that’s what this particular concept is talking about in the exam guide as far as understanding the ramifications of field updates and the potential for recursion. And the thing to be aware of is this checkbox to reevaluate workflow rules after field changes. So now that we’ve talked about recursion and filled updates, let’s now get into launching a flow via a process.