Well, this is a big day. Harry is finally letting other Gearys help write his…
1. Salesforce Winter 22 Features – Lightning Sales Cloud, Einstein Sales Cloud, and General Enhancements
2. Salesforce Winter 22 Features – Service Cloud, Service Cloud Voice, Surveys and Service Cloud Einstein
5. Salesforce Winter 22 Features – Experience Cloud, Salesforce CMS, Salesforce Anywhere, Chatter & Files
“He likes me, he really likes me!” That’s how I’m feeling now that I have been chosen by our fearless leader to participate in the release blogs TWICE IN A ROW! Guys, is this a thing now? Am I getting ahead of myself? I’m so honored. I promise I won’t let it get to my head.
:: starts planning for a new career as an Influencer and Blogger ::
Of course, I only blog where I know, so we will of course be discussing my favorite cloud and all of its “friends.” We’ve hit Sales Cloud, Service Cloud, Salesforce Flow, and Salesforce Field Service. Today’s post is number 5 of our Release Recap series and centers around Experience Cloud (looking for all of you that are having trouble NOT calling it Community), Salesforce CMS, Chatter, Salesforce Anywhere (Quip, for those of you who struggle with change), and Files! Whew!
Caveat: **Friends is in quotes because, well, Salesforce CMS is a total close friend of Experience Cloud, but the others are like, TOTALLY just random people that show up to the party and everyone is like, “who invited them, this party is exclusive?” And they are like, “but we don’t really have any other friends so can we just come to this party of misfits?” And Experience Cloud is all, “come on in, the more the merrier,” because in my head, Experience Cloud is just… the best and obviously welcoming and inclusive. So let’s get into it, shall we?
At this point, I think it’s obvious that Experience Cloud is my favorite of the clouds. Of course, I look for the shiny stuff with every release… new standard components, new automation, an updated self-registration that does not create duplicates (a girl can dream)!
However, I am noticing a trend in the last couple of releases. We are seeing a lot of attention being paid to the new Lightning Web Runtime template. So, I wanted to spend some time summarizing what we are seeing there.
Lighting Web Runtime
First, a reminder of what LWR is. Lightning Web Runtime is a Build Your Own Template that allows you to build your own customized sites with your own design system and component library. No need to use SLDS (Salesforce Lightning Design System), and you can now include your own components and design system to achieve pixel perfection. From our experience thus far, we are finding that this is a very lightweight template, with increased performance and more branding options.
First and most important, we have another…
NAME CHANGE! The original Build Your Own template is now called Build Your Own (Aura). This rename makes it easier to distinguish between Aura and LWR when choosing a Build Your Own template. Of course, if it wasn’t obvious, the other choice is Build Your Own (LWR). Not as exciting as Quip becoming Salesforce Anywhere, or Communities becoming Experience Sites, or Field Service Lightning becoming Salesforce Field Service.. but I digress.
Now that we have cleared up that confusion, let’s dive into the LWR enhancements and optimizations. Honestly, my biggest concern with this template has always been the lack of out-of-the-box components it came with (having to build everything from scratch? Yuck!).
However, I am seeing with this release that there is a lot of attention being paid to shrinking that gap. First, we are now seeing the ability to capture leads with a new standard Lead Form. On top of this, we are also seeing the following components: Header, Banner, Tile, Image, Video, Text, Button, and Horizontal Line.
We are also seeing more options with branding/styling! With Winter 22, you can now customize the size and shape of the buttons and input fields. For buttons, you can adjust the look and size of the button text, as well as the width, font size, and edges. For Forms, you can adjust the rounding of the corners on input fields, and adjust the field borders as well. You can now customize the colors of these elements (text, heading, link, button), and form colors. There is also a new site spacing panel that allows you to adjust the widths of the site and spacing between components within each section.
Some additional updates and enhancements for LWR:
- Prior to this release, LWR only supported English. With Winter 22 you can now set your LWR’s site default language to any language that Experience Cloud supports
- Using Lightning Message Service you can also communicate between Aura and Lightning web components
- To improve page load times for LWR sites, HTML document caching is now enabled in orgs that use Salesforce’s included CDN for Digital Experiences
- Use data binding to quickly select content to dynamically populate your LWR sites
General Experience Cloud
There are a handful of optimizations and enhancements that are not LWR specific. For one, with Winter 22, when site users begin to enter an address on the site, it will be completed using Google location services.
My favorite enhancement though is that Salesforce going totally META. We can now use audiences as criteria for OTHER AUDIENCES! For our customers who are utilizing Audiences like they are going out of style, this will most likely allow them to take their list of audiences down and simplify their rules for dynamic experiences. Much less to manage, and more time to, oh I don’t know… geek out over the Developer Productivity enhancements coming with the Winter release!
Developer Productivity Enhancements
- You can now use expression language with Data Binding in LWR Sites
- Page references now support external record routes
- You can Set Up Tab Bar Navigation for Mobile Publisher Apps in ExperienceBundle
- You can get information about the current site in Lightning Web Components
- Now you can incorporate user-authorized cookie consent into your sites/components
- You can use the @salesforce/apexContinuation Scoped Module in LWR Sites
There are a couple of interesting enhancements coming with Self-Registration (no, not duplicate prevention… sigh).
For one, there is a PILOT for B2C experiences that have a large amount of registration traffic. With this pilot, you will be using bulk processing so you aren’t processing one request at a time.
There is also an improvement around the self-registration process for orgs using account role optimization for their high-traffic sites. The registration process is now 10x faster than before.
Security and Sharing
Lastly, it wouldn’t be an EC release without some updates to Security and Sharing. There are no major updates like the Armageddon of the Guest User Lockdown, but notable mentions are:
- We have a new setting: Enhanced Personal Information Management. What this will do is block view access to 20 fields that are considered personal information. This will prevent external users from viewing personal information within user records and will ensure that no one can accidentally expose that information in a page layout or report, etc.
- Say “Peace Out” to the Run Flows for Guest Users permission. Now you can use the more granular permission flow that comes with Flows.
- Badge visibility now defaults to authenticated users only. You can turn this off, but just a heads up on the default, if your Badges are visible to guest users.
- This is another update to guest user security/visibility and PRODUCT records. The Product org-wide sharing default for external users is no longer applied to guest users, and guest user access is set to Private. This setting can’t be changed. To prevent guest users from losing access to products, create and test guest user sharing rules.
- There has been an enhancement around the device activation email template (if you are using it). With Winter 22, you will be able to have consistent branding with the ability to customize the email to tailor your communication with site users.
- You can now specify a language for emails and texts. If you are using Apex to manage identity verification for your sites, you can guarantee that the verification emails are sent in the right language (using the initSelfRegistration method to detect the user language through the user object).
- Lastly, Files Connect for SharePoint On-Premises and Secure Agent will be retired on October 1, 2021. Salesforce is recommending that you move to Files Connect for SharePoint Online or plan for an alternative solution.
So, my mind is blown. With all that CMS has to offer, Salesforce didn’t really spend much time on it in this release. You know how highly I think of CMS and the opportunity it has to be a total game-changer (and if you don’t, check out this sweet blog post) so I am hoping they are just planning for more exciting and sexy stuff in the Spring release. Ready to be underwhelmed? Here goes:
You can now preview your CMS content, responsively, before you publish.
Yup, that’s it. You can see how your content will look on different screen sizes. And yes, yes, yes – I see the value, but that’s it? As any parent would say “No, I’m not mad, just disappointed.“
:: gazes out the window with the silent treatment ::
CMS: Hey Jill.. are you ok?
Jill: Yup, I’m FINE.
I am going, to be honest, I’m feeling a bit meh about the Chatter release as well, but this one doesn’t surprise me. Years ago, releases would have been chock-full of Chatter updates. However, with the investment in other products/integrations related to communication (I’m looking at you, Slack keep an eye out for our blog post next week, Slack gets one all to itself after all the Dreamforce announcements), maybe it is losing its shine?
However, I do love this update: you can copy and paste images directly into your Chatter posts!
Hallelujah! But yes, JUST THAT ONE IMPROVEMENT… so nothing else to see here folks, move along.
Slowly but surely, I am becoming an avid user of Qui… umm, Salesforce Anywhere (habits are hard to break, trust me, just look at the Release Notes, Salesforce even has trouble doing it). Honestly though at Gears, we are now using Salesforce Anywhere to document account notes, collaborate on planning, store templates, etc.
So, the first thing to note about The Artist Formally Known As Quip is that it’s a TOTAL REBEL. It throws caution to the wind and goes by its own release schedule. You can see here when to expect any of the below features.
Interestingly enough, much like we tell our customers to reduce “swivel chair” anywhere you can, Salesforce is making the effort to do that with this release. One of the big improvements is being able to access your documents and galleries right from Salesforce so you don’t need to continually swivel between Salesforce and
Quip Salesforce Anywhere. You can also add the New Document global action to your global publisher layouts so your users can create a document wherever they are in Lightning Experience, link it to a record, and collaborate with their teams.
Another pretty cool update is that your users can create documents from templates in Salesforce Anywhere that autofill directly from a record in Salesforce. Also in that vein, you can add Salesforce data to your templates more easily by associating new templates with a Salesforce org and object (via @mentions). Previously, you configured this link every time you added Salesforce data to a template.
With this release, your users can access their Template Library galleries, such as the Created by Me or company galleries, in Lightning Experience. Users can create documents from templates and stay in Salesforce, making it easier to keep their free-form content and Salesforce data in context.
While reducing the need to “swivel chair” is always a welcome addition, Salesforce also paid attention to the downstream effects in regards to security. With all these changes, users can now see when others can access their documents linked to a record. Also, when a user links their document to a record, that user can also see what level of access has been granted to other users. So while Salesforce is making things more connected, they are realizing that they need to give users visibility into the access on those documents/spreadsheets/etc. Like Diddy says “easier access, more security problems,” or something very very similar to that.
We have a lot of updates to the Quip API Methods (SF called it Quip in the release notes, so I feel justified in going back to my roots):
- Identity Management (SCIM) API method: you can now update or disable multiple Quip user accounts at the same time with the Bulk System for Cross-domain Identity Management (SCIM) API method. You can use this API method to fulfill your compliance and user-management service-level agreements (SLAs)
- Create Bulk Expert PDFs Request API method: you can export multiple Quip threads such as documents or spreadsheets to PDFs with this method. You can also get your requested PDFs by calling the Retrieve Bulk Export PDF Response API method
- Quip Automation API Method: with this method, you can now add rows to spreadsheets, create export PDF requests, retrieve export PDF Responses, and Edit Documents
- They have put some maximum limits on several automation API inputs to help with performance issues and errors. You can see that list here
Well there you have it, Experience Cloud and all its “friends” for Winter ’22. Definitely a more “technical” release overall, with no huge drops or game-changers, but lots of enhancements and optimizations nonetheless. I do think we will continue to see a lot of focus on that LWR template, so I highly recommend you spend some time getting your arms around it!
As always, if you want help with any of these new features, please reach out and one of our Solution Architects (me, if you’re lucky) will get in touch! Stay tuned for Harry’s overview of the new(ish) Workforce Management functionality and Winter ’22 updates.