Learn what’s new for App Builders in Winter '21
After completing this unit, you’ll be able to:
- Locate Lightning App Builder header and toolbar buttons.
- Deploy organization-wide defaults and criteria-based sharing rules together.
- Develop flow screen components that work for multiple objects.
- Break up your record details with Dynamic Forms.
- Debug flow errors in a sandbox org as another user.
If you hold the Salesforce Platform App Builder credential, keep in mind that you need to complete this module by the due date to maintain your certification. Another important part of maintaining your credential is ensuring your Trailhead and Webassessor accounts are linked.
Interested in learning more about getting certified? Check out the Salesforce Platform App Builder credential.
Salesforce introduced a ton of great feature enhancements. Let’s take a look at some of the more important ones for this release.
Note: While anyone can earn this badge, this module is designed for those who hold the Salesforce Certified Platform App Builder certification.
Lightning App Builder Header and Toolbar Changes
We updated the Lightning App Builder header and toolbar and moved some items around.
How Does It Work?
In the header, we moved the Back button to the far left (1).
In the toolbar, the Refresh button is now a simple arrow icon (2). We also added an Analyze button to record pages for the new Performance Analysis in App Builder (3). We switched the places and colors of the Save and Activation buttons (4). The Save button is now the rightmost button and is blue, and the Activation button is now white.
Deploy Organization-Wide Defaults and Criteria-Based Sharing Rules Together
You can now simultaneously update the
sharingModel field for an object and create new criteria-based or guest user sharing rules via the Metadata API.
How Does It Work?
Previously, you deployed these changes in separate packages, but now you can deploy these changes simultaneously. You still deploy owner-based sharing rules separately from organization-wide default changes.
Develop Flow Screen Components That Work for Multiple Objects
Now you can create reusable flow screen components that use the generic
sObject data types.
How Does It Work?
Build one component that works for multiple objects, rather than one for each individual object. For example, you can build a data table component that works with any collection of records, from accounts and contacts to custom objects.
Break Up Your Record Details with Dynamic Forms
Dynamic Forms is the next step in the evolution of Lightning record pages. It adds the ability to configure record detail fields and sections inside the Lightning App Builder. This feature, which is now generally available and enabled for everyone, includes some changes since the beta release.
The more fields on your page layout, the more that the Record Detail component becomes a monolithic block of fields that you can’t customize. With Dynamic Forms, you can migrate the fields and sections from your page layout as individual components into the Lightning App Builder. Then, you can configure them just like the rest of the components on the page, and give users only the fields and sections that they need.
How Does It Work?
Dynamic Forms is now enabled for everyone! As a result, you see new features available in the Lightning App Builder. A new Fields tab in the component palette contains Field and Field Section components, which are the building blocks for Dynamic Forms. And as you configure fields and sections, you get help from in-app tips, created just for Dynamic Forms–driven pages.
How do you get started? Open an existing record page in the Lightning App Builder, then click Upgrade Now from the Record Detail properties pane to launch the Dynamic Forms migration wizard. With only a few clicks, the wizard adds fields and field sections to the page for you.
Migration isn’t the only path, however. You can also build your pages from scratch. Create a fresh Lightning record page, then drag fields and sections anywhere you want onto the page.
Changes Since Beta
- Dynamic Forms is now on for everyone in supported editions. The ability to turn it on and off for your org from the Record Page Settings node in Setup is removed.
- Universally required fields moved to their own section of the palette and have distinctive icons.
- Packaging is now supported for pages that contain Dynamic Forms components (Field, Field Section).
- Enhanced support for Dynamic Forms during edit, create, and clone.
- Several limitations and known issues are resolved.
Debug Flow Errors in Sandbox Org as Another User
In Setup, go to Process Automation Settings and select the Let admins debug flows as other users checkbox.
Next, open a flow in Flow Builder and click Debug. Select the Run flow as another user checkbox, and choose a user to impersonate.
The flow debug run then starts with you as the impersonated user. Review the debug details.
Debugging a flow as another user is available only for screen flows and autolaunched flows in nonproduction orgs. This feature supports flow elements and actions only. Any operations performed by screen components are performed as the logged-in user and not as the impersonated user. These screen components include custom Aura components, custom Lightning web components, and some standard flow screen components such as Lookup components.