Changed Encryption Method for External Data Credentials
Credentials stored within three external data entities—NamedCredential, ExternalDataUserAuth, and ExternalDataSource—are now encrypted under a framework that is consistent with other encryption frameworks on the platform. Salesforce encrypts your credentials using org-based keys instead of pod or instance-level keys, giving your third-party data an extra layer of security.
Where: This change applies to Lightning Experience and Salesforce classic in all editions.
How: Your secret keys are auto-created by the new encryption framework. Credentials encrypted using the previous encryption scheme are being migrated to the new framework. All new credentials will use the new framework.
Integrate with Third-Party Services without Exposure to Public Internet (Pilot)
When you want to integrate third-party services with Salesforce, it’s essential to be able to communicate securely. With Private Connect, you can increase security on your HTTP/s traffic by setting up a fully managed secure connection between Salesforce data centers and Amazon Web Services (AWS). API calls that run through AWS PrivateLink don’t traverse the internet, reducing exposure to outsider security threats.
Where: This change applies to Lightning Experience and Salesforce classic in all editions.
How: To use Private Connect, your org must be enrolled in the Private Connect pilot. For information about joining the pilot, contact your Account Executive.
Allow Access to Customized Actions Perm Is No Longer Required
The Allow Access to Customized Actions permission is no longer required to access customized actions.
Where: This change applies to Lightning Experience in Group, Professional, Enterprise, Performance, Unlimited, Contact Manager, and Developer editions.
Monitor Your Custom Object and Settings Count in System Overview
Compare the number of custom objects and settings that you’ve created against the total number in your org, including the ones installed from packages. Know when you’re approaching or have reached your limit. System Overview now shows both the number of objects that you created and how many total you have in your org. These values help you understand how many custom objects you can still create or install before you reach the limit.
Where: This change applies to Lightning Experience and Salesforce Classic in all editions.
Why: Each Salesforce edition has a limit on the number of custom objects that you can create in your org. Beyond the edition limit, a hard limit governs how many custom objects you can install from managed packages, such as apps publicly posted on AppExchange.
How: From Setup, in the Quick Find box, enter System Overview, and then select System Overview.
Your Custom Objects + Your Custom Settings shows the number of active custom objects and settings created by you and users in your org.
Total Custom Objects + Total Custom Settings shows the number of active and inactive objects in your org, including the objects created by you, created by users in your org, or installed from packages. This number includes soft-deleted custom objects that are still waiting to be hard deleted. For more information about the hard-deletion process, see Delete Custom Objects.
Keep Sharing Records When Migrating to Enterprise Territory Management
If you’re migrating to Enterprise Territory Management, you can keep your original territory sharing records so that your sales team can continue working. After the migration is complete, use the SharingSettings Metadata API type to delete these records.
Where: This change applies to Lightning Experience and Salesforce Classic in Performance and Developer editions and in Enterprise and Unlimited editions with the Sales Cloud.
Sharing Setting: Set an External Access Level for Leads (Beta)
You can now assign different internal and external access levels for leads. Use external org-wide defaults to set a more restrictive access level for external users without changing the access that internal users have.
Where: This change applies to Lightning Experience and Salesforce Classic in Professional, Enterprise, Performance, Unlimited, and Developer editions.
How: To set the external access level, from Setup, enter Sharing Settings in the Quick Find box, then select Sharing Settings. Under Organization-Wide Defaults, edit the default external access for Lead.
Sharing Setting: Safeguard Your Data by Setting External Access Levels for More Standard Objects (Generally Available)
You can now set external access levels for many more standard objects. Select more restrictive access for external users without changing the default access level for internal users. The objects available for external org-wide defaults vary depending on your org’s licenses and other settings.
Where: This change applies to Lightning Experience and Salesforce Classic in Professional, Enterprise, Performance, Unlimited, and Developer editions.
How: To set external org-wide defaults, from Setup, enter Sharing Settings in the Quick Find box, then select Sharing Settings. Under Organization-Wide Defaults, edit the default external access.
https://help.salesforce.com/s/articleView?id=release-notes.rn_forcecom_sharing_owd_ga.htm&release=222&type=5
Sharing Setting: Secure Guest Users’ Sharing Settings
When you enable the Secure guest user record access setting, you set guest users' org-wide defaults to Private for all objects. This setting also restricts the way you can share records with guest users and lets you create new guest user sharing rules.
Where: This change applies to all communities accessed through Lightning Experience and Salesforce Classic in Essentials, Enterprise, Performance, Unlimited, and Developer editions.
Install Even More Custom Objects in Your Org
We did it again: We raised the total hard limit for custom objects in an org to 3,000 (up from 2,500 in the previous release) so that you can install more custom objects from packages.
Where: This change applies to Lightning Experience and Salesforce Classic in all editions.
Why: Why not? You can do more with more objects. Each Salesforce edition has a limit on the number of custom objects that you can create in your org. Beyond the edition limit, a hard limit governs how many custom objects you can install from managed packages, such as apps publicly posted on AppExchange. The new 3,000 total limit includes the maximum number of custom objects created and installed in your org. For example, in Unlimited Edition, you can create up to 2,000 custom objects in your org. On top of that limit, you can also install up to 1,000 custom objects from managed packages. If your org is approaching the 3,000 total limit, we recommend that you hard delete or erase custom objects that you no longer need.
Stabilize the Hostname for My Domain URLs in Sandboxes (PreviouslyReleased Critical Update)
We’re removing instance names from MyDomain URLs for sandboxes. The instance name identifies
where your Salesforce sandbox org is hosted. Removing the instance name makes the URL cleaner and
easier for users to remember, for example, MyDomain--SandboxName.my.salesforce.com replaces
MyDomain--SandboxName.cs5.my.salesforce.com. This critical update was first made available in
Summer ’18.
https://help.salesforce.com/s/articleView?id=release-notes.rn_security_domains_stabilize_mydomain_cruc.htm&release=224&type=5