Skip to main content

Salesforce Summer '22 Release - Experience Cloud Top Features

 Summer '22 release is round the corner. Below is my top pick from Experience Cloud perspective:-

Redirect Your Previous Force.com Site URLs

To minimize the potential disruption for visitors to your previous *.force.com site URLs after you enable enhanced domains, choose whether to redirect those public-facing URLs to your current site URL.

Let Your Site Users Deactivate Their Account

Late in Spring ’22, the Customizable User Settings component was updated to include new properties that let your users deactivate their account from within Aura sites.

Where: This change applies to Aura sites accessed through Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions.

How: First, to allow your users to deactivate their account, in User Management Settings in Setup, enable User Self Deactivate. Then, in Experience Builder, configure the new Account Details properties of the Customizable User Settings component. Make sure to deselect the Hide the Deactivate Account section checkbox so that your users can see the Deactivate My Account button.
No alt text provided for this image








@salesforce/community Supports 18-Character IDs

For consistency with other Salesforce APIs, the @salesforce/community scoped module now returns IDs that are 18 characters long. Previously, the scoped module returned 15-character IDs.

Tell Customers When There’s Too Much Traffic

When your site has higher than usual traffic, customers see the Too Many Requests (TMR) page. The page refreshes every 30 seconds and redirects customers when the site is available. You can customize the page to fit your brand, or use it as is. Find it in the Pages menu in Experience Builder. The TMR page is enabled for sites using enhanced domains and Salesforce’s CDN for Digital Experiences.

How: The Too Many Requests page is enabled for all sites that use Salesforce’s CDN for Digital Experiences.
No alt text provided for this image

Cache Apex Calls for Guest Users Only (Beta)

Control whether Apex requests for guests are cached on CDN for Digital Experiences. Caching requests improves the performance of your LWR site.

Where: This change applies to LWR sites accessed through Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions.

How: To enable caching for guest users, select Cache public data from Apex methods for guest users in Preferences on the Administration tile of your site’s workspaces. Use @wire (in LWC) to invoke publicly cacheable Apex actions. Only Apex methods annotated with @AuraEnabled(cacheable=true scope=’global’) are cached.

Complete release notes can be found here.

Comments

Post a Comment

Popular posts from this blog

Mashup Integration in Salesforce

During preparation for TA certification exam, I came across a word Mashup for integration a number of times. I explored about it and below is description:- Mashups, sometimes called “composites,” are hybrid applications created by bringing together several data sources and Web services to create a new application or to add value to an existing application. Behind the scenes, mashups may require different levels of integration, depending on whether the mashed-up data is only meant to be viewed, whether it can be edited, and whether data is actually transferred between systems. There are three types of mashup:- Client Presentation Mashup - In this type of mashup the integration takes place strictly at the visual level. It makes possible to view data from two or more applications in a browser,  without actually moving data between the applications. Example - Google Maps. Client Service Mashup - As mashups evolve, they are becoming more complex and sophisticated. Client...
15 comments
Read more

ReadOnly Annotation

Use Case:- You want to show up to 10000 record on single VF page. Count of records based upon some business requirement where number of records could go up to 1 million. So far, it was not possible to achieve above in VF page because of following limitations:- The maximum number of items in a collection that can be iterated over using components such as <apex:dataTable> , <apex:dataList> , and <apex:repeat> is 1000. Normally, queries for a single Visualforce page request may not retrieve more than 50,000 rows. Solution:- But with API version 23.0 , salesforce has introduced ' ReadOnly ' annotation which has following functionality/restriction:- The @ReadOnly annotation allows you to perform unrestricted queries against the Force.comdatabase. All other limits still apply. It's important to note that this annotation, while removing the limit of the number of returned rows for a request, blocks you from performing the following operations ...
Post a Comment
Read more

Grant Access Using Hierarchies

Problem There is a custom object say 'XYZ' and OWD for this is set to ' Private ', which means record of this can be seen by only owner and users above in role-hierarchy and territory. However, to share this with other user, we can manually share it. The problem is that I don't want other users, who are above in role-hierarchy and territory of the user with whom record has shared, can see it. Solution We can un-check ' Grant Access Using Hierarchies ' check box for object 'XYZ' on 'Sharing Settings' page. We can go to Setup >> Security Controls >> Sharing Settings and click on ' Edit ' button. On the edit page, we can un-check ' Grant Access Using Hierarchies ' for required object.  Major uses of 'Grant Access Using Hierarchies' are:- If you disable the Grant Access Using Hierarchies option, sharing with a role or territory and subordinates only shares with the users directly asso...
1 comment
Read more