Screen Flow Fundamentals Superbadge Unit
Work with screen flows and elements to streamline data management.
Screen Flow Fundamentals Superbadge Unit
What You'll Be Doing to Earn This Superbadge
- Configure a screen flow to collect information from users.
- Use Flow elements and actions to create detailed records.
- Use Get Records elements to find and update matching records.
Concepts Tested in This Superbadge
- Screen flows
- Flow elements and actions
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 can take a few minutes), open it and click Verify Account.
Complete your registration by setting your password and challenge question. Tip: Save your username, password, and login URL in a secure place—such as a password manager—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 unit.
Now that you have a Salesforce org with special configuration for this superbadge unit, you’re good to go.
Tips
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; this applies to some screen components.
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.
Make sure you save your work before running the challenge check.
Ensure that you don’t create duplicate records, labels, permission sets, and so on, as part of any challenge.
Build your solution according to the requirements; adding more actions or steps can cause challenge checks to fail.
Use Case
The Hive Foundation focuses on community impact programs to help people experiencing poverty or homelessness. Their leadership are deeply troubled by the rise of adolescent mental health challenges and want to help communities respond. The first step in their plan is to build a tool that anyone in a community can use to contribute local resources, events, and support opportunities. Their vision is that these tools can be deployed in communities around the world to aggregate resources and help build more resilient and well-resourced communities.
Business Requirements
Your first step in helping the foundation is to complete the build of a screen flow. Eventually, this flow will live on the Hive Foundation’s website, but for now it will be used by internal staff. When it’s live, website visitors will be able to enter key information about a variety of community resources. You’ve already created a custom object called Resource to hold this information.
Screen 1: Resource Management
You’ve done quite a bit of work in setting up the Resource Management flow and are looking forward to adding and modifying screens for users to input data. Begin by creating a welcome screen situated between the flow Start and the first Assignment element. Name the first screen Resource Management and add a description of your choosing.
Add welcome text to display a welcome message to users; we suggest something like Welcome to the Hive Foundation community! Thanks for contributing. with API Name Welcome.
Add the Hive Foundation logo under the display text. The logo is already in your special org with the API Name Hive_Foundation_Logo. Set the API Name to hive_logo with alt text Hive Logo and image width to 80%.
Add a Radio Buttons component with label text How may we help you today? with API Name resource_input. Make this Radio Button component required and do not let users select multiple options. Define the first choice as {!StartNewResourceRequest} to allow the user to create a new resource, and define the second choice as {!EditExistingResourceRequest} to allow the user to update an existing resource.
Add a Text component to capture the Resource Name for returning users, with API Name it_resource_name. The resource name should only be visible when the user indicates they are working with an existing resource.
You reviewed the flow and decided to add a way for users to see their overall progress in the process. You’ve already installed the custom Dynamic Flow Progress Lightning web component from the Salesforce AppExchange listing. Add the Dynamic Flow Progress custom component to the top of the screen above the Welcome message. Give it the API Name Dynamic_Progress_Start. In configuring this component, set the list of steps to the {!Flow_Steps} variable. On this first screen, set the Current Step to Step 1. Set the Indicator Type to Bar. Note: It’s up to you whether you configure the Progress component on other screens.
Update Assignment and S2 New Resource Request elements
After completing the initial screen, modify the Assignment element labeled Assign Resource Name in the Resource Management flow, and update the two inputs to values entered in Screen 1: Resource Management.
Next up is the S2 New Resource Request screen. This screen is partially configured. Add more features to the screen so the user can input the needed information. Add a Lookup component with API Name lu_account, which should look up to the Account object that is on the Resource record.
The foundation wants to provide resources that are useful to specific audiences. Add a Multi-Select Picklist component to indicate the target audience, with API Name mspl_target_audience. Set the Choice input to {!choiceset_resource_audience_type}. Next, add a picklist component for Resource Type with API Name pl_resource_type. Set the Choice input to {!choiceset_resource_type}.
Event Details
Some resources will be events, so you add a section to the S2 New Resource Request screen called Event Details with section API Name Event_Details. This section should only be visible if the resource type is Event. In this section, add a component that captures the start date and time; use the API Name idt_Start_Date_and_Time. Add another component that captures the end date and time; use the API Name idt_End_Date_and_Time. Add a validation that makes sure the end date is after the start date; use the formula {!idt_Start_Date_and_Time} < {!idt_End_Date_and_Time} to validate the user’s input. Include an error message for users who enter a start date later than end date. Also include Help text to guide the user who enters a start date later than end date. You can use any text you’d like in the validation error message and Help text.
Assign resource details
Next, configure the Assign Resource Details element in the Resource Management flow. Update the following variables to reflect the value captured in the corresponding component from the S2 New Resource Request screen.
- Target Audience
- Resource Type
- Start Date
- End Date
- Account
Screen 3: S3 Edit Resource Request
Next you move on to S3 Edit Resource Request screen. Replace the placeholder text with appropriate field values in the following elements with the matching field values using the record variable resource.
- “Add Primary Contact Name field value”
- “Add Type field value”
- “Add Account name field value”
One thing the foundation wants is that users should not be able to edit the email address associated with the resource. Modify the Email component to restrict editing to the Email field.
Finally, configure two fields on the S3 Edit Resource Request screen to display default values from the Resource record the user is referencing. Update the default value of the Resource Title and Description input fields to display the value from that Resource record.
Note: If you’re trying to debug the flow for this screen, be sure to update the Primary_Contact_Email__c field on the Resource record to your email address.
After reviewing the screen flow, you’re happy to share the completed work with the foundation. You’re confident this tool will help communities identify and share important resources. Next up: distributing screen flows across the Hive Foundation’s Salesforce instance and Experience Cloud pages.