Our Lead Salesforce Consultant, Leon, and Head of Salesforce Development, Mark, have put together their top new feature picks from the Spring ’20 Release notes.
Here’s what they’re getting all excited about this Spring…
In-App Guidance is a series of hints, instructions, tips, videos, pictures etc that can be launched from within specific Salesforce pages to help users get to grips with things. This is a fairly recent feature, and now Salesforce is improving it — you’ll be able to set it by Profile and it can also be translated through Translation Workbench! Perfect for multi-country orgs.
This will probably be the first thing that end-users notice when they get their Spring ’20 update. Instead of the App Launcher being a huge page of options, you will now get a search bar and a handful of your top Apps. You can still get to the full menu with a click of a button.
We’re split in the office on this one. Some of us love the change, others are not so sure. This is going to be one of those “it depends on how you use it” kind of things that people will just eventually get used to.
Cloning a record has been possible since approximately the dawn of time, but we’ve never had an out of the box solution for deep cloning – for example, you have an Opportunity you want to clone, you would have previously had to manually clone every individual Opportunity Product and Contact Role, or write a Flow to do the heavy lifting for you.
Not any more, now you can do this out of the box using the new “Clone with Related Records” feature. Great time saver for end users.
Yes yes yes yes yes yes YES! Finally!
This one has been requested for so long that I think some of us thought it would never actually happen. To fill in the blanks for those not in the know, Queues act as a holding pot for records that haven’t been given to a specific owner. People can then dip in to those queues and pick stuff out, or it could be automatically distributed by a feature like Omni Channel.
Until now, only Leads and Cases have been queueable. Now we can add Tasks to the list, which is a big step forward. Got a load of jobs that just need doing, doesn’t matter by who as long, as someone picks them up? Tasks in queues are the way to go!
Salesforce has been very busy with Flows again – every release sees this tool grow in power and capabilities. My personal favourite changes this time around are Run flows in System mode. You can now set a Flow to run as the user or as the system – running it as the system bypasses pesky things like the end-user permissions.
It’s not all gravy, you’ll still have to consider sharing, roles, teams and territories, but object permissions, field-level access and other general running user permissions get ignored.
This is a massive change. Now, before any data comes into contact with the database, flows can run and set specific values on the record – look forward to genuinely lightning speed with your updates, because Before Save updates in a flow are 10 times faster than a Process Builder record change.
As an Admin or Consultant, there has literally never been a better time to get to grips with Flow.
One of the aggravating things about Flow is having to create lots of variables. For those who haven’t used Flow much, a variable is essentially a bucket that you use to store records, field data and so on, in order to use it later down the line in the flow.
Creating variables is time-consuming and boring, and you had to choose which fields to save and which to ignore, making it all too easy to miss off a critical field and break your Flow. Not any more – now Flow will create those variables for you. Thanks, Flow.
Now generally available, service and support centres can start using WhatsApp through Salesforce to communicate with customers in realtime. They can already do this via SMS or Facebook Message, so this is a very cool addition!
Another Service-specific improvement, I wanted this 5 years ago when I was a Customer Service agent! Duplicate cases are a massive pain in the backside. You have to close them, or get them deleted – and then you have situations where half the information is in one case and half has been added to the duplicate.
Now, you’ll be able to merge up to three duplicate cases into one so that they can focus on the “master” case. Lovely little addition!
The maximum length of SOQL statements has been increased from 20,000 to 100,000.
- Use more relationships in queries
The maximum number of child-to-parent relationships in a query has been increased from 35 to 55.
The maximum length of SOSL statements has been increased from 20,000 to 100,000.
The default daily API request allocation has been raised from 15,000 to 100,000.
Salesforce Data Mask is a powerful new data security resource for Salesforce admins and developers. Instead of manually securing data and access for sandbox orgs, admins can use Data Mask to automatically mask the data in a sandbox.
We plan to end support for the deprecated components on May 1, 2021.
Use the new lightning/pageReferenceUtils module or lightning:pageReferenceUtils Aura component to build navigation links in your components that prepopulate a record’s create page with default field values.
No more guessing about whether to use @track to make a field reactive. All fields in a Lightning web component class are reactive. If a field’s value changes and the field is used in a template or in a getter of a property that’s used in a template, the component rerenders and displays the new value.
A Lightning web component’s CSS file can use a custom Aura token created in your org or installed from an unmanaged package. Tokens make it easy to ensure that your design is consistent and even easier to update it as your design evolves.
Lightning Web Components now offers Local Development so that you can build component modules and view your changes live without publishing your components to an org.
Use the Lightning Message Service API to communicate across the DOM, between Aura components, Visualforce pages, and Lightning web components.
Using the new Apple authentication provider, your customers can log in to a Salesforce org or Community with their Apple ID.
Develop and test your Salesforce Sites and communities within your sandboxes using custom domains. This feature allows you to test new custom domains in a sandbox before deploying them to Salesforce production.
To help you better reach your customers, you can now specify multiple email addresses or phone numbers for an individual or person account. Previously, our data model only allowed for one phone number or email to be associated with a single customer. Now, using contact point email and contact point phone, you can also add details such as the best time to reach out to a contact or how they prefer to be contacted.
The components available for a changeset vary by edition. These components are now available for changesets.
This allows users to make updates to Salesforce all by voice. Einstein Voice Skills lets you build custom skills tailored to your users’ most common tasks, generating more high-quality Salesforce data to inform decision making.
The CMS Home welcome mat greets you at the door with helpful pointers and links to help topics to make your stay more comfortable. A navigation tab and a new entry into CMS Workspaces and Experience Builder help you get where you want to go.
The ExperienceBundle metadata type, which was previously available as a pilot program, is now generally available. ExperienceBundle provides human-readable, text-based representations of the different Experience Builder settings and site components, such as pages, branding sets, and themes.
Use the latest Build Your Own (LWC) template to develop communities that load quickly and scale well. Based on Lightning Web Components (LWC), a new programming model that delivers exceptional performance, this lightweight template supports fully customized LWC solutions.
Turn Lightning Locker on and off for all components in a community, regardless of API version, with a simple switch in Experience Builder.
Permission set groups are an ideal way to consistently and reliably assign permissions to a group of users. Assign users a single permission set group instead of multiple permission sets.
What are you most pumped about from this Salesforce release? Let us know in the comments below!