Spring '21 Abridged

The Salesforce Discord Collective Presents:
THE SPRING 21 RELEASE NOTES - ABRIDGED
As Exciting as the new Samsung WF50R8500A release

CRITICAL STUFF

• CRUD permissions fully removed from Guest User. Last release, they only set it to FALSE. Yes, it’s always been good practice to not have Unauthenticated Users view and delete your data on a public endpoint. Yes, we already called it last release. Yes, some of y’all decided "eh i’ll just turn it back on". Well now you can’t. FIX. DEM. PERMS.

GENERAL STUFF

• Official Release Notes move to a slightly better looking but slower website. Doesn’t change the hidden advertisement for paid features though.
• Dynamic Forms check Dupes before save you time. I wanted to reuse the word “save” to make the sentence shorter, realized it wasn’t intelligible, and committed anyway.
• In-App Guidance gets snooze capabilities, and you can now share them manually to someone. Trailhead also now is present in Salesforce, to ease User Onboarding. All of these should be free of myTrailhead licensing.

SALESFORCE CORE

• Recently Viewed now supports Actions, making the view less useless great again ffs I give up on the joke here useful.
• Opportunity Products can now be the Parent of a Relationship This was listed for Winter21, pulled (with actually great communication as highlighted in the thread), and is now available. Yay :)
• Lightning Email Templates are now set to replace ye olden classic ones. Considerations to be read
• Dashboards now expose filters as URL parameters so you can actually do “dynamic”-ish dashboard filters.
• Dynamic Actions now available on mobile. To avoid further confusion with Dynamic Dashboards, we’d like to offer to Rebrand it to Lightning Actions, can’t go wrong with that, guaranteed no confusion. Yessir.
• New Limit on inactive picklist values. Great for people that don’t sanitize data before loading it to SF. I’m looking at YOU, Rob. You know what you did.
• Enhanced Domains change how My Domains work a bit, required reading for users, some nice perks.
• Help Texts go BRRR but don’t go <BR/> which is nice but also too bad ^Please ^let ^^me ^^^line ^^^^break

SERVICE

• Service Cloud Voice QoL changes include some good stuff, but the real thing is their new Documentation including a learning portal. Also their API changes so if you’re one of the two devs that already used it already, read that.
• Einstein Bots support more languages (some more stuff in Pilot) and Predictions can be turned on with fewer Transcripts available
• That Email RefId update is now delayed by a year because turns out they didn’t think people had automation building the RefId. :Kekw:
• Minor nice change: you can now change NoReply email addresses on some Service notifications.

FLOWS

• Record-Triggered Flows can now have Delayed Actions but I find the example they give really unfortunate - for one week before the Opp Close date, you should use a Scheduled Flow that queries records matching specific criteria instead, which will avoid the undue Flow Scheduled Interviews. Great for low-delay dynamic dates though.
• PriorValue in Record-Triggered Flows to most admin’s glorious celebration.
• SendEmail with Rich text from Templates. So Pretty.
• Screen Flows get nice polish with pretty screens, many columns and the ability to control how Screens behave on revists
• Debugging gets better and supports Scheduled Flows. Debug Logs also get more accurate
• The first Flow API Version is here with mostly QoL updates.

For anyone who cares, we consider Flows a valid replacement for some Processes starting this release, with the caveat of more testing in Sandbox required compared to Processes. We still recommend wariness for enterprise orgs though, and do not consider it ready for prime-time in all contexts.

FIELD SERVICE

• Shift patterns solve a major pain point, and being able to mass create them is a big time saver and likely the first flow a consultant would have to build for dispatchers/territory managers. Combined with Shift Criteria this makes the entire concept a thoroughbred workhorse of a solution.
• Advanced recurrence is ‘Pretty big’ according to @lookasavage, but he ain’t saying why, so… IT’S BIG I TELL YOU.

DEVELOPMENT

• Salesforce Functions will shortly be open as Beta. You might remember them as Evergreen. Would I use this in prod, or even sandbox, yet ? Nah. Would I research it for fun ? HELL YASS.
• FIELDS(ALL) / FIELDS(CUSTOM) etc now exist (but have a lot of limitations). Are meant to replace describes, not to replace field selection in actual SOQL queries. Mostly because there’s a 200 record limit on SOQLs that use it.
• CI/CD starting to get easier, faster. Source Tracking between Local and SDB, and Org-dependent Unlocked Packages come expand your toolkit.
• Transaction Finalizers feature is in beta. Dev guide here. TL;DR you can know the status of a Queuable once it finishes without polling.
• Apex upgraded to 51.0 have some important behavioral changes to System and Schema functions, scroll to the bottom so you’re aware.
• Minor changes to Lead Conversion that require analysis as it can simplify stuff for a lot of orgs
• SOQL for loop syntax, for (Account acc : [SELECT ...), is now better optimized
• Platform Events can now be configured with a <user> and <batchSize> property.
• CMDT accessible via Static Methods, no need for SOQL anymore
  *SLDS gets a few more styling hooks and has breaking CSS changes
• ISVs, there’s new APEX Analytics for you and better Release and Error handling. You also get Free Platform Cache in a small amount. Now you too can experience this beautiful website
• Shield Subscribers, RTE Monitoring Setup now available via MDAPI

DOGELAND

• :doge: I think I’ll leave this in as long as it’s not fixed: STOP PUTTING PAID ADDONS IN CORE FEATURE RELEASE NOTES WITHOUT FLAGGING THEM AS SUCH THANK YOU.
• :doge: There was a bug in a function so we removed the function yo
• :doge: “Optimize” by adding LIGHTNING in places Users don’t care about

OTHER

• CPQ as usual has the best release notes format Check that out I can’t summarize it more than it is.
• Accounts can be Campaign Members because… you can contact Companies now ? I don’t really understand that one, like you’re calling a business that has no one in it ? Not a single contact or lead ?

Useless fact of the day: This ARN is 27% shorter than last release, and 48% shorter than Spring20.

This abridged version was graciously written up by the SF Discord

We have a nice wiki: https://wiki.sfxd.org/

And a linkedin page: https://www.linkedin.com/company/sfxd/

Join the ~2500 members in the most active chat-based community around Salesforce these parts of the web at http://join.sfxd.org/