Install More Custom Fields
Custom fields limit has been increased from 500 to 900.
We can create up to 800 custom fields and can also have 100 fields from the managed package.
Set Expirations for Assignments on Permissions in Permission Sets and Permission Set Groups
When assigning users to a permission set or permission set group, select expiration dates that you specify. Control when a user’s permissions expire based on your business requirements.
We can also Set Expirations for Permission Set Groups
Convert the Read Only Standard Profile to a Custom Profile (Update, Enforced)
This update converts the Read Only standard profile to a custom profile, which allows you to edit permissions in this profile as your business needs require. This update was first available in Spring ’21 and is enforced in Summer ’21.
Securely Call the Visualforce Remoting API
The Visualforce Remoting API uses JavaScript to call methods in Apex controllers directly from Visualforce pages. To ensure that the API is properly secured, calls now have stricter validation. This update is enforced in Winter ’22
To improve security of the Visualforce JavaScript Remoting API, this update modifies how the CSRF token is created for the Visualforce $RemoteAction global variable. This validation adds more protection to API remoting calls by guest users. Also, this update validates the {“apexType”: “Object”} parameter used by the Visualforce $RemoteAction global variable against the Apex method parameter and throws an error if the apexType parameter is invalid. This validation prevents users from providing Apex objects they can’t access or providing Apex objects that don’t satisfy the Apex method parameter.
We recommend performing these testing steps in a sandbox environment to evaluate the release update’s impact and fix any validation errors before it’s auto-enabled in Winter ’22.
Actions to Asynchronous Apex Jobs Using Transaction Finalizers
The System.FinalizerContext interface contains four methods.
- getAsyncApexJobId
- getRequestId
- getResult
- getException
Require Multi-Factor Authentication for Logins to Subscriber Orgs (Update, Postponed)
This update is part of the Salesforce requirement that all customers enable multi-factor authentication (MFA) for their Salesforce products. Released in Winter ’21, this update was scheduled for auto-activation in Summer ’21, but that has been changed to Spring ’22 to align with the larger Salesforce requirement. This update secures access to subscriber orgs by requiring MFA when logging into the License Management Org (LMO).
Where: This change applies to the License Management Orgs used to support first- and second-generation managed packages. 232 Salesforce Summer ’21 Release Notes Packaging
When: Salesforce will enforce this update in Spring ’22. To get the major release upgrade date for your instance, go to Trust Status, search for your instance, and click the maintenance tab.
Why: This change provides subscribers who need assistance with their managed packages an extra layer of security by verifying the identity of the user accessing their org. This change also gives you more control and accountability over which users log into a subscriber org.
How: To test and apply this update, from Setup, in the Quick Find box, enter Release Updates, and select Release Updates. Locate Require Multi-Factor Authentication for Logins to Subscriber Orgs and follow the testing and activation steps. If the License Management Org session hasn’t been established using MFA, this update blocks attempts to access the Subscriber Support Console.
Update Guest User’s Email Address
When you create Salesforce site, Salesforce automatically creates a guest site user. In any site created before the Summer ’21 release, the email address for the site guest user record was that of the Salesforce user who created the site. After the Summer ’21 release, the system generates a dummy email address to use in the guest site user record.
Search : Apex Changes and New Items