These are the first Salesforce release updates you’ll have already started encountering in your sandboxes.
https://help.salesforce.com/articleView?id=release-notes.rn_ru.htm&type=5&release=232
Disable Access to Non-global Apex Controller Methods in Managed Packages (Update, Enforced)
When: April 4th rolled out to some sandboxes, enforced Summer ‘21
What’s Changing? Methods in managed Apex Classes that do not have the Global access modifier will no longer be available to Aura components.
How do I know if my Org is affected?
- Review your Aura components. Look to see if there are any packaged methods used.
- If any are found, review the packaged class containing the method(s).
- If the Apex Class is managed, and the method used does not have the global identifier, that Aura component will break.
- Alternatively, you can enable the test in the sandbox and test your Aura components in your sandbox to see if they behave as expected.
How do I fix [xyz]? You’ll have to rebuild the method if possible, otherwise, your Aura components will no longer work. Reach out to the package developer and ask them if they are planning on making the methods global in an upcoming release.
What happens if I do nothing? If your org is affected, your Aura components will stop working.
Enforce Access Modifiers on Apex Properties in Lightning Component Markup (Update, Enforced)
When: April 4th rolled out to some sandboxes, enforced Summer ‘21
What’s Changing? Getter methods in Apex Classes will now have their access modifiers respected by the Aura and Lightning Components that use them. If the method is private or protected, it will not be read by the component.
How do I know if my Org is affected?
- Review your Aura and Lightning Web Components. Look to see if they are referencing getter methods from an Apex Class (controller).
- If any are found, review the Apex Class and confirm if the getter method has the access modifier private or protected. If so, the component will not be able to read the value.
- Alternatively, you can enable the test in a sandbox and test whether your Aura and Lightning Web Components behave as expected.
How do I fix [xyz]? Update the access modifiers on the getter method(s) to public.
What happens if I do nothing? Your Aura and Lightning Web Components may break or not behave as expected.
Convert the Read Only Standard Profile to a Custom Profile (Update, Enforced)
When: Available since Spring ‘21, enforced Summer ‘21.
What’s Changing? The Read Only Profile will be editable and customizable to better fit your needs and security requirements.
How do I know if my Org is affected?
- Open the Read Only Profile in setup. Click “Manage Assignments”.
- If any users are assigned, they will be affected by any changes you make. Changes are not applied with the Release Update.
How do I fix [xyz]? If you used the Read Only Profile for any Users, review the permissions and make changes to fit your organization’s needs.
What happens if I do nothing? Nothing will break. You won’t notice any changes.
Require Verification When Experience Cloud Users, Partners, and Customers Change Their Email Address (Update, Enforced)
When: Available since Winter ‘21, original Spring ‘21 enforcement postponed to Summer ‘21
What’s Changing? External Users will now need to verify a request to change their email address as Internal Users currently do. This increases security for External Users and requires them to click a link sent to the new email address to verify the change.
How do I know if my Org is affected? If you have External Users (Customer, Partner, Experience Cloud Users) and you use Aura, LWR, and Visualforce sites accessed through Lightning Experience and Salesforce Classic in Enterprise, Essentials, Unlimited, and Developer editions, you are affected.
How do I fix [xyz]? You can disable this setting after it is enforced, but it is not recommended.
What happens if I do nothing? If your org is affected, External Users will now need to take an extra step when changing their email address associated with your Experience, Site, etc.
NEW! Update Guest User’s Email Address (Update)
When: Available after Summer ‘21.
What’s Changing? Prior to Summer ‘21 the Guest User for a Site, Portal, or Community (Experience) would have the email address for the User that created that Site, Portal, or Community. After Summer ‘21, new Sites, Portals, and Communities Guest Users will be assigned a dummy email address.
How do I know if my Org is affected? If you have a Site, Portal, or Community (Experience), this affects you. Nothing will break, but now you have more control over the Guest User email – which may affect your processes, hopefully for the better. Maybe double-check your reports, assignment rules, etc.
How do I fix my Guest User Email Address(es)? There is nothing to fix, unless you want to assign a specific email address (that is accessible, and not a dummy) to the Guest User, which you can do after Summer ‘21!
What happens if I do nothing? You’ll be fine.
Also enforced… I covered this in the Spring ‘21 release blog. Enforce Data Access in Flow Merge Fields (Update, Enforced)
Coming soon we will discuss the important feature updates in the upcoming Summer 21 Release.
