Salesforce Spring ’20 is here, this release delivers expanded innovations across the entire Customer 360 platform, empowering you to get a single shared view of your customer and deliver more moments that matter.
Normally, how a flow is launched determines whether the flow runs in the context of the user or the system. Now you can bypass the running user’s permissions by setting your flow to run in system context with sharing. The flow still respects org-wide default settings, role hierarchies, sharing rules, manual sharing, teams, and territories, but it ignores object permissions, field-level access, or other permissions of the running user
To let users log in with their Apple ID, create an Apple authentication provider from the Salesforce Auth. Providers Setup page. After configuring the authentication provider and adding the Apple sign-in button to your Salesforce and Communities login pages, users can log in with their Apple credentials.
For single sign-on, the Request Signature Method (RSM) applies a hashing algorithm—either RSA-SHA1 or RSA-SHA256—for encrypted requests. You can now apply the selected single sign-on RSM to your single logout (SLO) settings.
All new Salesforce orgs are now set up so that identity verification by email occurs only if the user has no other identity verification methods registered. Possible identity verification methods include Salesforce Authenticator, SMS, time-based one-time password (TOTP), physical key (U2F), and email. The new setting, Prevent identity verification by email when other methods are registered, appears on Identity Verification and Session Settings Setup pages. To increase security in your existing orgs, Salesforce recommends that you enable this setting.
Find and open apps and items quicker with enhancements to the Lightning Experience App Launcher. Search for apps and items and have your top apps right at your fingertips.
The Security.stripInaccessible method for field- and object-level data protection is now generally available. Use the stripInaccessible method to strip fields that the current user can’t access from query and subquery results. Use the method to remove inaccessible fields from sObjects before a DML operation to avoid exceptions. Also, use the stripInaccessible method to sanitize sObjects that have been deserialized from an untrusted source.
This change applies to orgs with Lightning components in Lightning Experience,
Salesforce Classic, and all versions of the Salesforce app. Salesforce plans to end support for Aura components in the ui namespace on May 1, 2021. We can continue to use these components beyond May 1, 2021, but they won’t accept support cases for them after that date. Solution: Replace the deprecated components with their counterparts in the lightning namespace. These components are faster, more efficient, and they implement Lightning Design System styling out-of-the-box.
Need help with the new Salesforce Spring’20 release contact us or comment below . We’d be happy to discuss how we can help you maximize the value of Salesforce.
We acknowledge the Traditional Custodians of country throughout Australia and their connections to land, sea and community.
We pay our respect to their Elders past and present and extend that respect to all Aboriginal and Torres Strait Islander peoples today.
© 2023 TechForce Services. All rights reserved
