Use the same account next time to pick up where you left off.
|Production Salesforce account||Developer Edition or Admin Playground|
|Do I need to be a Salesforce customer?||Yes||No (It's free!)|
|Can I use it to create my Trailhead profile and store my badges?||Yes||Yes|
|Can I use it to complete Trailhead challenges?||No (except for multiple choices quizzes)||Yes|
|Can I keep my Trailhead badges if I leave my company?||No||Yes (use a personal email address)|
Salesforce has two different user interfaces: Lightning Experience and Salesforce Classic. It’s easy to switch between the two. You can learn about switching between interfaces, enabling Lightning Experience, and more in the Lightning Experience Basics module here on Trailhead.
This module is designed for Salesforce Classic.
Salesforce provides multiple tools to automate your org’s repetitive business processes: Lightning Process Builder, Visual Workflow, Workflow, and Approvals. The automation tool that you need depends on the type of business process that you’re automating.
Example: Notify the account owner when a related case is escalated.
Example: Customer support uses a wizard to step through a call script, and cases are created based on the information that they enter.
Example: Managers approve their direct reports’ requests for vacation.
Three of our tools can address this use case: Workflow, Process Builder, and Visual Workflow. Respectively, these tools create workflow rules, processes, and flows.
We recommend starting with Process Builder, especially for business processes that can be simplified to if/then statements. For example: if a case is escalated, then notify the account owner.
Process Builder includes almost all the functionality that’s available in workflow rules, and more. In fact, a single process can do what it would normally take multiple workflow rules to do. The only thing you can do with workflow that you can’t do with processes is send outbound messages without code. However, you can work around this limitation by calling Apex code from a process.
Example: First, check whether a case is escalated. If the case is escalated, check the account’s region and route the case accordingly.
Example: After an opportunity is closed and won, calculate the opportunity’s discount. Then apply that discount to all the related opportunity products.
If you need to build a wizard to collect information, Visual Workflow is the tool for you. Create a flow that displays information to and requests information from a user. Then take the information that they enter and perform actions in Salesforce with it.
For example, create a flow that walks customer support representatives through a call script. The flow uses information that the representative entered, such as the caller’s name and account number, to create a case that’s assigned to the right person.
For example, when an employee requests time off, that time has to be approved by the employee’s manager. You need to ensure that when a time-off request is submitted for approval, the right person (the employee’s manager) receives the request.
To automate your organization’s processes for approving records, create approval processes.
Here’s a breakdown of all the features and actions that are supported in each automation tool. Use it to determine which tool is best for your business needs.
|Process Builder||Visual Workflow||Workflow||Approvals|
|Complexity||Multiple if/then statements||Complex||A single if/then statement||A single if/then statement|
|Browser support||All (Chrome recommended)||All (Safari not recommended)||All||All|
||Record is changed||
|Supports time-based actions|
|Supports user interaction|
|Call Apex code|
|Create records||Tasks only||Tasks only|
|Launch a flow||(Pilot)1|
|Post to Chatter|
|Send email||(Email alerts only)||(Email alerts only)||(Email alerts only)|
|Send outbound messages without code|
|Submit for approval|
|Update fields||Any related record||Any record||The record or its parent||The record or its parent|
1The Process Builder has superseded flow trigger workflow actions, previously available in a pilot program. Orgs that are using flow trigger workflow actions can continue to create and edit them, but they aren’t available for new orgs.
Here are some tips: