Salesforce Release

Summer ’20 Community Highlights

Summer20ReleaseLogo

The list of Spring ’20 features below apply to Community enhancements.

There are additional Spring ’20 features available to Salesforce Classic only, Lightning Experience and Salesforce Classic, Lightning Experience only, Mobile Enhancements, Other Enhancements in the Summer ’20 Release Highlights post.

Note: These features are not listed in any specific order.

  1. Create custom Lightning components to override the New or Edit standard forms. Select Override standard actions with a Lightning component in the Administration | Preferences | Community Management section.
  2. Personalize the navigation menus, tile menus and CMS collections by audience. Previously, you could only personalize page variations, branding sets and components.
  3. Improved Community Pages Menu allows you to search for the page, see where the folder it resides in and edit the page right from the search results.
  4. Initiate a manual refresh of your SEO sitemap outside the automated sitemap generation process that occurs every Sunday. Note: This applies to Salesforce CMS and Lightning communities.
  5. Add dynamic SEO properties to your content detail pages for improved search engine results.
  6. Customize the tile formatting and text formatting with the revamped tile menu. Note: To use the new version, you need to delete the old component and add the new one. Once you delete the old component, you cannot restore it.
  7. The new user profile menu component allows you to configure menu items, add personalization and show the user’s company logo and name.
  8. Add the multi-level navigation that allows you to show one level of menu at a time, up to 5 category levels.
  9. (Pilot) Use Build Your Own (LWC) template to create fast and efficient communities. Note: This minimal template provides a few components and is best for developers who build LWC components.
  10. ExperienceBundle now includes the theme layout properties.
  11. Guest User Security Policies Enforced:

a. Option to hide certain personal information on the user record from external user view.

b. Automatically assign records created by a guest user to a default user. Note: You can opt out of this security policy before Summer ’20 but will need to remediate this when it is enforced in Winter ’21.

c. Give yourself more time by opting out of guest user security policies before Summer ’20. By activating this update, you will automatically opt out of these settings that will be auto-enabled with Summer ’20: secure guest user record access, assign new records created by guest users to a default owner and assign new records created by Salesforce Sites guest users. Note: You must comply with the new guest security policies before Winter ’21 when they are enforced in all orgs.

d. Guest users can’t be assigned as an owner of existing records in the org. Note: You can opt out of this security policy before Summer ’20 but will need to remediate this when it is enforced in Winter ’21.

e. Secure guest users’ OWD and sharing model is enforced. This sets private OWD for guest users and restricts sharing tools you would use to grant record access to guest users. Note: For more information, view this Guest User Security Policies and Timelines Help article.

f. View all users and other permissions disabled in the guest user profile. Other permissions: Can Approve Feed Post and Comments, Enable UI Tier Architecture, Remove People from Direct Messages, View Topics, and Send Non-Commercial Email.

g. (Orgs created in Summer ’20 and beyond) Allow guest users to only create and read records in objects. You cannot provide View All Data, Modify All Data, update or delete permissions on custom objects.

h. (Security Alert) Starting with the Winter ’21 release, View All Data, Modify All Data, delete permissions on standard and custom objects will be removed from the guest user profile.

i. Buy yourself more time by opting out of turning off community specific setting for guest users to see other community members. Note: This will be automatically disabled in Winter ’21.

j. (Security Alert) Restrict access to @AuraEnabled apex methods for guests and portal users based on the user profile. When activated, this update will enforce user profile restrictions for apex classes used in aura and LWC.

k. (Security Alert) Restrict access to @AuraEnabled apex methods for authenticated users based on user profile. When activated, this update will enforce user profile restrictions for apex classes used in aura and LWC.

  1. Enable 2FA (two factor authentication) for external users via the External Identity license.
  2. Partners and customers can share data with other external accounts using external account hierarchies.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s