Spring '22 Abridged

The Salesforce Discord Collective Presents:
THE SPRING 22 RELEASE NOTES - ABRIDGED
Written by people who think having a proper RSS feed on official release documentation shouldn’t be this hard. (@SFXD_BOT)

CRITICAL STUFF

Mandatory MFA is still coming and now has a Question-based readiness check. The last two releases we highlighted that it wasn’t exactly the best thought-out rollout. Salesforce seems to agree as they are "enforcing" the "mandatory" part this month legally, but aren’t actually activating it forcefully until EoY, and it’ll be deactivatable until… 2023. They’re releasing ways to not use TOTP already anyway.
Maybe that team and the Case Threading one can go have coffee and publish notes on how to do better rollouts. That would be an interesting feedback loop.
Minor critical Flow update: if you use Two-Column Layouts, migrate to Sections ASAP

GENERAL STUFF

Admins get notified if a page takes more than 4 seconds to load on average. Great, but the fact that this is a common enough occurence tells you how well things go when you give non-specialists access to custom page builders with no load checking.
Pardot gets scripts in landing pages and redirects for unpublished Pages which should make quite a few marketeers happy.
Salesforce Voice becomes the first CTI to factor in Agent Omnichannel Work Capacity when routing, allows easier Supervisor Call Monitoring, better status handling between SF and Amazon, and a better transfer UI. Probably the most loved feature this release outside of Flows, with stellar feature releases.
Omni-channel Flows are GA and powerful. Probably makes skill based routing kinda redundant long term.
Lightning Sync be dead, you can turn it off

REPORTING

Reports get some very nicely thought Quality of Life updates, with better Report Type selection, and multi-line data editing in reports
Dashboards get Dynamic Gauge Charts to the great joy of managers who can check Targets easily now

FLOWS

External Services now support OpenAPI 3.0 and unsupported Data Types mapping- meaning you can now (try) to integrate directly with most things that are documented in Swagger. Cool, seeing as Guest Users can use those now.
You can open Subflows from Main Flows, which makes that function much better (but still missing an easy way of viewing all the ways a Subflow is called to make it really useful)
Collections can now be used as a choice option and can also be filtered, which isn’t exactly a map (I still want maps plz) but is still a VERY powerful improvement. Nice.
Flow Trigger Explorer, a better view of Record-Triggered Flows that Admins will love, as well as this minor update that allows viewing Flow information in browser tab names, and the ability to shortcut Flow elements. Screen Readers are also supported now
Orchestrator allow distribution of labor via queue assignation, and become even more code-like with custom Evaluation ~~methods~~ Flows that you can ~~invoke~~ call from Orchestrator and Debugging, Deployment. For Admins, you can now view Orchestrations and Work Items to ensure things are running smoothly (or cancel them if they don’t).
The bell tolls for Workflows which can now be converted to Flows (beta).
You can define Orders of execution for Flows. I am visibly alone in hating this change, but I still say that relying on specific orders of execution for Admin-built automation is a highway to useless complexity. If you’re at the point where you need actions to be sequential, they should be refactored into their own logic which forces the order. Fight me.
Speaking of Order of Execution, Flow API v54 changes the After-Save order, specifically related to Entitlements

DEVELOPMENT

Packagers get a GREAT Documentation Upgrade, much easier to navigate and review
Write More Robust UI Tests with UTAM
LWR comes to Node.JS. Get your LWCs on local webservers!
Light DOM now available for better script injection, also applies to Experiences
LWCSecurity kills Locker, is future, has new tools to ease seeing security settings
Full-fledged Interface Support means more manageable code for enterprise-class projects

EXPERIENCES

Guest User Permissions Crackdown continues.
You still can’t delete Experiences but you can archive them so they don’t count against your Experiences limit.
You can access labels more easily from Experiences. This release note also wins the “moar JPG for ants” award for its screenshot.
Role-based licenses get Optimization enabled by default which is meant to reduce the amount of Roles created in single-contact Accounts with Roles.
LWR Experiences can now be translated, allow searching within Components, get a Marketing Cloud connected data collection form

CPQ

DOGELAND

:doge: Salesforce keeps pushing Scheduler as part of “Overall Features”, also Paid Einstein Stuff, hell why not add Paid Data Pipelines. Literally just advertising in Release Notes. It’s still disgraceful.
:doge: Salesforce continues rebranding features no one cares about and makes it easier to buy licenses at market price lol to maybe stop hiring AEs
:doge: “We didn’t publish anything but here’s something our marketing team drafted back in December so we don’t lose our precious Release Notes spot”.
:doge: “We fused the help sections of two slightly different things and made knowing which license you need harder”
:doge: Scoping Rules are so confusing that even the team can’t explain it well “yeah it doesn’t restrict access, it just hides records, but I mean by default only, you know?”
:doge: A few people used FSL a bit too well and will now have to pay for the same function
:doge: If you don’t want your user to see ~~ads~~ helpful suggestions you might want to deactivate in-app guidance which just gets auto-enabled

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 ~8500 members in the most active chat-based community around Salesforce these parts of the web at http://join.sfxd.org/

Spring '22 Abridged

No Comments