Learning Objectives

After completing this unit, you'll be able to:

• Create a custom formula field and use the formula editor.

• Explain why formula fields are useful.

• Outline at least one use case for formula fields.

• Create simple formulas.

Learning Objectives

After completing this unit, you'll be able to:

• Describe what a roll-up summary field is.

• Create a roll-up summary field.

• Apply field-level security to your roll-up summary field.

Learning Objectives

After completing this unit, you'll be able to:

• Describe two use cases for validation rules.

• List the elements of a validation rule.

• Create a validation rule.

Learning Objectives

After completing this unit, you'll be able to:

• Explain the importance of giving the right people access to the right data.

• List the four levels at which you can control data access.

• Describe a typical scenario for limiting data access at each of the four levels.

Learning Objectives

After completing this unit, you'll be able to:

• Create, view, and manage users.

• Set password policies.

• Limit the IP addresses from which users can log in.

• Limit the times at which users can log in.

Learning Objectives

After completing this unit, you'll be able to:

• View existing profiles and create new ones.

• Modify access to objects using profiles.

• View all assigned users in a profile.

• Create new permission sets.

• Assign permission sets to single and multiple users.

Learning Objectives

After completing this unit, you'll be able to:

• List reasons to limit access to specific fields.

• View and edit field-level security settings.

Learning Objectives

After completing this unit, you'll be able to:

• List the four ways to control access to records.

• Describe situations in which to use each of the four record-level security controls.

• Explain how the different record controls interact with each other.

• Set org-wide sharing defaults to control access to records.

Learning Objectives

After completing this unit, you'll be able to:

• Explain how a role hierarchy is different from an org chart.

• View and modify a role hierarchy.

• Create and assign roles to simplify access to records.

Learning Objectives

After completing this unit, you'll be able to:

• Use sharing rules to extend access beyond the role hierarchy structure.

• Create a public group that includes users with different profiles and roles.

Learning Objectives

After completing this unit, you’ll be able to:

• Decide when to add a picklist field.

• Decide which type of picklist you need.

• Create a custom picklist.

Learning Objectives

After completing this unit, you’ll be able to:

• Manage values for picklists.

• Use formulas to define picklist values dynamically.

• Explain what happens to existing data as you change picklist values.

Learning Objectives

After completing this unit, you’ll be able to:

• Create global value sets.

• Manage global value sets.

• Promote an existing field’s values to a global value set.

Learning Objectives

In this project, you’ll:

• Create a Salesforce app that includes standard collaboration and analytics features.

• Familiarize yourself with the app’s user interface in the browser and in the Salesforce mobile app.

Learning Objectives

After completing this unit, you'll be able to:

• List the tools included in Lightning Flow.

• Describe the tools available for automating guided visual experiences.

• Describe and compare the tools available for behind-the-scenes automation.

• Describe the tools available for approval automation.

Learning Objectives

After completing this unit, you'll be able to:

• List the types of processes that you can build in Process Builder.

• Define the key components used to create a process.

• Build a process that updates the addresses for an account's contacts when the account’s address is updated.

Learning Objectives

After completing this unit, you'll be able to:

• Define a flow and list its key components.

• Describe the types of flow elements.

• Build a flow that creates a record and uploads files.

YOUR CHALLENGE

Guide users through creating a lead

Build a flow that creates a lead with user-entered information and uploads a related file for the lead. Then add the flow to a Home page.

Before You Start

• In Setup, go to Process Automation Settings

• Select Enable Lightning runtime for flows and Save

Challenge Requirements:

• Create a flow:

  • Label: New Lead

  • Type: Screen Flow

• Add a screen:

  • Label: Lead Screen

• Add two text fields to the New Lead screen:

  • Label: Last Name

  • Label: Company Name

  • Mark both text fields required

• Add a Create Records element:

  • Label: Create Lead

  • Select: Use separate variables, resources, and literal values

  • Object: Lead

  • Use the screen fields to set the Lead's Last Name and Company.

  • Store the Lead's ID in a new resource (Variable) called leadId with type of Text.

• Add a second screen:

  • Label: Component Screen

• Add a screen component to the second screen:

  • Choose the File Upload screen component

  • API Name: Upload_File

  • File Upload Label: Upload Related Files

  • Related Record ID: {!leadId}

  • For Allow Multiple Files, select {!$GlobalConstant.True}

• Activate the New Lead flow.

• Create a new Lightning page:

  • Type: Home Page

  • Label: Process Automation Home

  • Page Template: Standard Home Page

  • Add a Flow component that references the New Lead flow

  • Activate the page and assign it as the org default

Learning Objectives

After completing this unit, you'll be able to:

• Describe a business process that can be automated using a process and a flow.

• Define what a flow variable is.

• Build a flow that iterates over a group of records.

• Build a process that starts a flow.

Learning Objectives

After completing this unit, you'll be able to:

• Describe a business process that can be automated using a process and a flow.

• Define what a flow variable is.

• Build a flow that iterates over a group of records.

• Build a process that starts a flow.

Learning Objectives

After completing this unit, you'll be able to:

• Define an approval process, and list its key components.

• Describe a business process that can be automated using an approval process.

• Set up an approval process to automatically manage when an account changes from a prospect to a new customer.

Make sure that prospect accounts are approved before they’re converted to customers

Due to local regulation, new customers must be approved by the legal team. When a user creates an account that has a type of Prospect, they manually submit it for approval by clicking Submit for Approval on the account. The record is evaluated only if its type is Prospect and there are more than 500 employees. When the account enters the approval process, Type gets set to Pending and the record is locked. If approved, Type gets set to Customer and the record is unlocked. If not approved, Type gets set back to Prospect and the record is unlocked.

Before You Start
Verify that the Account object's Type field has the following picklist values: Prospect, Customer, Pending.

Challenge Requirements:

• Use the Jump Start Wizard to create a new approval process for the Account object

• The approval process name must be Approve New Account

• Pick any email template for approval assignment email template

• For Entry Criteria, use the following criteria.

  • Account: Type equals Prospect

  • Account: Employees greater than 500

• For Approver, choose Automatically assign to approver(s) and assign yourself as the approver

• Click View Approval Process Detail Page and finish off the remaining requirements.

  • In the Initial Submission section, add a Field Update action that updates the Account: Type field to Pending. The name of the action must be Account Type To Pending.

  • In the Final Approval Actions, add a Field Update action that updates the Account: Type field to Customer. The name of the action must be Account Type To Customer.

  • In the Final Approval Actions section, edit the Record Lock action to unlock the record

  • In the Final Rejection Actions section, add a Field Update action that updates the Account: Type field to Prospect. The name of the action must be Account Type To Prospect

• Activate the approval process

Learning Objectives

After completing this unit, you’ll be able to:

• Explain what AppExchange is.

• Describe how Salesforce organizes AppExchange listings.

• Describe pricing on AppExchange.

Learning Objectives

After completing this unit, you’ll be able to:

• Develop an AppExchange strategy using your business requirements.

• Describe the key elements of the AppExchange home page.

• Describe the key elements of an AppExchange listing.

• List the ways you can try an AppExchange solution.

Learning Objectives

After completing this unit, you’ll be able to:

• Describe the differences between managed and unmanaged packages.

• List key questions to ask before installing a package.

• Install a package in your org.

• Describe how to connect with other superheroes and AppExchange.

Learning Objectives

After completing this unit, you’ll be able to:

• Explain what an external service is.

• Identify use cases for external services.

• Describe the high-level flow of an external service.

Learning Objectives

After completing this unit, you’ll be able to:

• Describe the purpose of the schema definition.

• Explain elements of a good External Services schema definition.

• Name three issues that can cause your schema to fail.

Learning Objectives

After completing this unit, you’ll be able to:

• Define a Named Credential for your external service.

• Add an external service using a provided schema.

• Explain how the Apex actions relate to the schema you use.

Learning Objectives

After completing this unit, you’ll be able to:

• Find your External Services-generated Apex actions in the Flow toolbox.

• Create a simple flow with your External Services–generated Apex actions.

• Get Started with Your Salesforce App Rollout

• Craft Your Rollout Strategy

• Become a Mobile Expert and Evangelist

• Test Your Mobile Customizations

• Plan Your Rollout

• Communicate the Rollout to Your Company

• Roll Out the Salesforce App to Your Users