Prework and Notes
Sign Up for a Developer Edition Org with Special Configuration
To complete this superbadge unit, you need a special Developer Edition org that contains special configuration and sample data. Note that this Developer Edition org is designed to work with the challenges in this superbadge unit.
Sign up for a free Developer Edition org with special configuration.
Fill out the form. For Email address, enter an active email address.
- After you fill out the form, click Sign me up.
When you receive the activation email (this might take a few minutes), open it and click Verify Account.
Complete your registration by setting your password and challenge question. Tip: Write down your username, password, and login URL for easy access later.
You are logged in to your superbadge Developer Edition org.
Now, connect your new Developer Edition org to Trailhead.
Make sure you’re logged in to your Trailhead account.
In the Challenge section at the bottom of this page, select Connect Org from the picklist.
On the login screen, enter the username and password for the Developer Edition org you just set up.
On the Allow Access? page, click Allow.
On the Want to connect this org for hands-on challenges? page, click Yes! Save it. You are redirected back to the Challenge page and ready to use your new Developer Edition org to earn this superbadge.
Now that you have a Salesforce org with special configuration for this superbadge unit, you’re good to go.
Enter all labels exactly as described in the instructions. Labels are case-sensitive and spelling counts.
When possible, copy and paste the label names from superbadge instructions instead of typing them.
If label or API names are not specified, you can use any name you choose.
Superbadge units focus on very specific objectives; some best practices or typical approaches might not be required in the challenges. For example, activating a flow is an important step; activation is specifically included in the Flow Administration Superbadge Unit. It may not be required to pass the challenge unless specified.
Use the Automatically store all fields option in the Get Record elements.
Make sure you save your work before running the challenge check.
Build your solution according to the requirements; adding more actions or steps can cause challenge checks to fail.
We recommend following best practices and always including descriptions for flow elements. However, we’re not checking for element descriptions in this superbadge unit.
As the Salesforce admin for Main Stage Analytics, you’ve reviewed and improved several flows already. Continue reviewing user requests for assistance and enhancing existing flows to support better user experience.
Flow Interactions with Approval Processes
Case 5612: The sales team leadership wants to review every deal with a discount over 15%. Some team members want to manually submit their deals for approval early in the sales process, which they can do by using the Submit for Approval button on an opportunity record. Records that have been approved have the field Approved (API Name
Approved__c) set to True.
Not everyone manually submits their opportunities for approval, so your task is to automate high-discount opportunity review. Create a new record-triggered flow named
Discount Approval Request. Include the following requirements in the Custom Condition Logic for the Set Entry Conditions in the Start element.
Note: For the purpose of this challenge, do not use the NOT operator in the Custom Condition Logic.
- The automation should fire on opportunity records with Stage set to Negotiation/Review and a discount over 15%.
- In addition, the flow should select opportunities that weren’t already approved, or deals where the discount has changed.
This subset of records should enter the existing approval process
Discount_Approval. Be sure to activate the flow.
Flow Interactions with Assignment Rules and Custom Metadata
Case 5623: The sales team is having trouble properly assigning leads across queues. The team wants to automatically assign leads to one of two queues based on the lead’s country. The following configuration already exists in the org:
- A custom field called Region (API Name
- Two queues representing the two regions:
- Sales EMEA (API Name
- Sales APAC (API Name
- A custom metadata type called Region (API Name
Region__mdt) with two records, one each for APAC and EMEA
- A lead assignment rule Region Assignment that will assign leads to either queue based on the lead’s region
Create a record-triggered flow called
Set Lead Region to set the lead record’s Region based on the lead’s Country field (API Name
Country) by referencing the custom metadata type. The flow should evaluate leads with a country value when they are created or updated, and leads should be re-evaluated if the country value changes. Use the following logic for the entry criteria:
1 AND (2 OR 3) where
Country is not an empty string.
ID is null.
Country is changed.
Refer to the following requirements for the automation.
- Retrieve the Region custom metadata, which associates the following countries with a respective region.
- EMEA: ZM, GB, AE, ES
- APAC: AU, NZ, JP, KR
- Determine whether the lead’s country is included in the EMEA or APAC region.
- Don’t update the lead record if the lead’s country isn’t one of the countries included in either region.
- Update the lead record’s Region field with
Save and then activate the flow. The existing Lead Assignment Rule called Region Assignment will assign leads to the respective queue. To test your work, confirm that the assignment rule can reference the updated Region value on a new lead.
Note: The requirements in this superbadge unit are staged to test your flow interaction skills. The configuration required isn’t intended as any representation of a territory management model that would satisfy any operational requirement.
Flow Interactions with Other Flows
Case 5641: The Sales EMEA and Sales APAC teams have had separate Salesforce admins in the past. These different business processes have been supported with different automations to set the rating of new leads. The teams have reported that leads are updating with the wrong rating. Given existing external factors, the flows can’t be combined into one. Adjust the Sales EMEA Lead Rating and Sales APAC Lead Rating flows so that each automation runs only based on its region. Do not consolidate the flows.