Walkthrough of how to set up your Salesforce Trailhead account, which will be used for the duration of the course to build your own Salesforce Flows.

An overview of upcoming lectures in the Salesforce Flow course. We'll discuss some of the key items like Salesforce Flow Types and Salesforce Flow data elements, then we'll log into our Salesforce Trailhead environment for a tour.

Learn how to get started building a Salesforce Lightning Flow. We'll cover the common Salesforce Flow types that a Salesforce Administrator or Developer might utilize. Then we'll begin building our very first Salesforce Screen Flow.

Deep dive into the Salesforce Flow Builder canvas, with a focus on the Salesforce Lightning Flow screen element. We'll add a Display Text component to our Lightning Screen Flow and output the words "Hello World!".

Explanation of the Salesforce Flow data element called the Get Records. This data element allows us to find Salesforce records, and store their field values to use later in the Salesforce flow. It is one of the most commonly used data elements in the Salesforce Flow Builder.

Explanation of the Salesforce Flow data element called the Update Records. This data element allows us to update Salesforce records, using values from the Salesforce flow. We combine this with our Get Records element from the previous video to update a lead record in Salesforce.

Explanation of the Salesforce Flow data element called the Create Records. This data element allows us to create Salesforce records, using values from the Salesforce flow. We combine this with our previous Screen Element to create a new lead in Salesforce.

In this lecture we summarize the basics of the Lightning Flow Builder, discussing the key Salesforce Flow data elements and Salesforce Flow types we learned about in this section.

Get into the role of a Salesforce professional at Universal Containers and understand our first Salesforce flow requirements

Build out the needed fields that our Salesforce Lightning Flow will use leverage inside our solution

In-depth description of the Salesforce Record Triggered Flow configuration screen

Learn how to use an Assignment Element inside our Salesforce Flow in order to set a value on a field and perform an update to the Lead record

Test our Salesforce Flow in the UI to make sure the functionality is working as expected

Put on our Salesforce Administrator hats and make updates to the Lightning Page layouts on both Leads and Opportunities

Recap of the business challenge and the Salesforce Flow we built in our first challenge

Understand the business requirements of this Salesforce Flow challenge by reviewing a fictional Help Desk case from a Universal Containers team member.

As a Salesforce Administrator, we'll need to create two new user records and a picklist field in order to build this Salesforce Flow.

We'll take a quick pause here to review the challenge requirements and make sure that as a Salesforce Administrator we fully understand the reason we're building this Salesforce Flow.

We'll configure the start screen of another record triggered flow, as well as using the Salesforce Flow Get Element to find the appropriate user record.

We'll drag an Assignment element to the Salesforce Lightning Flow canvas in order to perform an update on the Task record we found while working with our Get Element.

Next we'll test our solution in the UI. We'll spend some time discussing best practices as a Salesforce Administrator specifically when it comes to working with Salesforce Flows

A comprehensive breakdown of the Salesforce Flow debugger tool and how you can use it to solve problems as a Salesforce Administrator

Review some of the key things we learned about Salesforce Flows in this challenge.

We discuss the needs of this challenge scenario and talk about best practices for gathering requirements as a Salesforce professional or Salesforce Administrator

In this video we complete the challenge prework by building a new field on the contact object. This is what you would do as a Salesforce Administrator in the business scenario.

We'll walk through the flow challenge in the UI to ensure we understand the requirements. This is a best practice you'll want to pick up as a Salesforce Flow builder. Then, we'll start working on the Salesforce Flow itself.

We'll use a Get Records inside our Salesforce Flow to lookup the contact record we want to populate on the case.

Next we'll use an Update Records inside our Salesforce Flow to update the case from our Record-Triggered Flow. We also discuss important testing scenarios, the positive, negative, null, and bulk tests.

We update our record-triggered flow based on the feedback we get from Sherri. To do this, we use a decision element and another Get Element in order to find the oldest contact record.

We spend more time learning how to sort records retrieved by the Get Element inside our Record Triggered Flow. Then we use a Flow Formula in order to update our case record.

We'll do some final debugging before calling our record-triggered flow "done".

We'll summarize the steps we took to build our Salesforce Flow in this challenge.

We introduce our challenge where we're looking to build a call script inside of a Salesforce screen flow in order to help Pedro, who is the sales manager at Universal Containers.

We use our ability as Certified Salesforce Administrators to create two new fields on the Lead object that we'll use to complete the Salesforce Screen Flow in this challenge.

In this video we spend some time talking about configuring the Salesforce Flow screen element, and also discuss how to configure the Screen Flow Call Script component.

In this video we add more fields to the Call Script screen inside our Salesforce Flow. We learn how to use a record single variable to make creating screen flows simple.

For the first time in the course, we discuss using a Fault Element inside our Screen Flow. Fault elements are powerful ways to gracefully handle errors that might occur inside a Salesforce Flow.

We introduce another brand new data element in our Salesforce Flow - the Roll Back Records. Roll Back Records come in handy when debugging Screen Flows or when using fault elements to prevent unneeded database updates from happening.

We continue configuring our Salesforce Screen Flow and go into detail on how the Lookup Screen Component works. This component can often be confusing, but after this video, you'll know exactly how it works.

After putting the finishing touches on our Salesforce Flow, we configure our final screen element. Then, we do what any good Certified Salesforce Administrator does and deploy our Screen Flow to end users in an easily accessible way!

In this video, we end our Challenge Four story with you as the Certified Salesforce Administrator at Universal Containers.

We'll provide a concept overview of using loops inside flows, and then we'll begin building a screen flow that will help us apply what we learned.

We've started our screen flow, built a record collection, dragged a loop to the canvas, and created a number variable - now it's time to set up our loop logic!

We built our first loop inside a Salesforce screen flow and now we'll define some logic for the loop to execute after it completes.

With our primer on Salesforce Loops out of the way, we can get back into the role of the Salesforce Administrator at Universal Containers and gather some requirements for our next challenge!

As Salesforce Administrators at Universal Containers, we'll build 3 new fields to support the requirements of this challenge. We'll also make some Salesforce Lightning Page updates and briefly review the challenge requirements.

We start building our Record Triggered Flow in the Salesforce Flow Builder. We configure our start element and then set up our first Get Records element

Continuing with our flow, we drag a loop element to the flow builder canvas and use an assignment element to set up our loop logic.

Previously we configured our loop element and our assignment logic, and now we need to use a record collection variable to store our records and then update them with an update element.

We've configured our Salesforce Flow and now we need to test our flow in Salesforce!

After we've successfully tested our loop flow, we can move on to building a before save record triggered flow that will populate the fields Pedro requested we populate on a new Opportunity. All we need is one assignment element!

We test our before save flow and learn an important lesson about optimizing for fast field updates.

Two out of three Salesforce Flows have been built and now its time for the final flow in the challenge. Here, we using a record triggered flow to update related Opportunity records when an Account changes in Salesforce.

We discuss a best practice that good Certified Salesforce Administrators and Salesforce Flow builders use which is to find the right tool for a job. In this video we cover an alternative solution an explore the philosophy of building solutions on the Salesforce platform.

We recap all we learned about Salesforce Flows in Challenge 5.

We'll introduce a brand new Salesforce Flow type - the Scheduled Triggered Flow!

We'll navigate to the Salesforce Flow builder and begin building our first scheduled trigger flow as part of the challenge primer.

We'll add an update element to our Salesforce Flow with the intention to set the Rating field on lead records at the end of each business day.

We'll activate our Salesforce Flow and then validate that it ran as expected by updating the Salesforce lead records we defined in our entry criteria.

We gather our Salesforce Flow requirements from the VP of Marketing, Naomi, and talk about the reverse engineering design principle.

We begin building our Salesforce Flow and review two options for identify records to work with in the scheduled triggered flow 1) a decision element and 2) a formula field.

We'll review how to use the Email action inside a Salesforce Flow, and build an email template that will reduce the amount of maintenance we have to do in the long term.

We spend 5 minutes covering an essential Salesforce Administrator settings screen which allows admins to configure several important automation settings that affect Salesforce Flows

We begin testing our Salesforce Flow, and discuss best practices around successfully debugging a scheduled triggered flow in Salesforce.

We introduce an advanced fault handling mechanism in our Salesforce Flow by creating a custom Error Log object to hold information about Salesforce Flow errors. Very few Salesforce Administrators use this concept and it will be very useful for you to implement in the future.

We review everything we learned about the Salesforce Flow builder in this challenge.

Introduce challenge seven in the Salesforce Flow Course where we work with Lisa, the Vice President of Sales at Universal Containers.

In this pretend discovery call we gather all the requirements we need to successfully build our Salesforce Flow.

We regroup to discuss what we learned about Lisa's requirements and how we will approach building our Salesforce Flow in this challenge.

We create an Opportunity stage and build email templates to support our Salesforce Flow building later in the challenge. Also, we introduce the Salesforce Inspector Extension for the first time.

We build a custom object that we will use inside our Salesforce Flow to track the impact of our new Flow on the Sales Team.

We begin building our Salesforce Flow by discussing the reverse engineering principle, which leads us to creating our send email action.

We build a Get Records element in our Salesforce Flow to query for the contact once we realize that the Send Email action can't be saved without it.

We build another Get Records element in our Salesforce Flow to query for the oldest contact. We also use the Salesforce Inspector extension to experiment with writing SOQL queries.

We use a Create Records element in our Salesforce Flow to log the time saved by our automation to the Automation Analytics custom object.

We introduce the scheduled path inside a Salesforce Record-Triggered Flow, and built out the several scheduled paths we need for our Salesforce Flow to work.

We debug our Salesforce Flow and experience an error which we work to correct.

We build a decision element in our record triggered flow to handle the scenario where a contact record does not exist or does not have an email address. Using a decision to validate certain data has been found will often occur in Salesforce Flows.

We clone our immediate run path to our 2 days later Scheduled Path inside our Salesforce Flow and the rename the elements so that the flow is easy to understand.

We clone our 2 days later Scheduled Path inside our Salesforce Flow, the rename the elements, and debug the functionality.

We clone the 4 days later path to the 6 days later path in our Salesforce Flow, rename the elements, and debug the functionality.

We clone the 6 days later path to the 8 days later path in our Salesforce Flow, rename the elements, and debug the functionality.

We build our final path in our Salesforce Flow by adding an update element to the Closed Lost path.

In this video we dive deep on the four common test scenarios you'll want to remember when working with Salesforce Flows. We activate our flow and then trigger it by updating an Opportunity to the "Working" stage.

We go step by step through the different actions we expect our Salesforce Flow to perform so that we can confirm everything is working.

With everything working as expected, we take a look at the Automation Analytics records created by our Salesforce Flow, to see how they can help us quantify our impact on the business.