Vlocity Learning..

 Summer 21 Release Updates. 

Salesforce already published summer 21 Release notes. (Click here )

In this blog, I listed few key details which are important in my view 😁

Key Dates for Summer 21 

By Jun 12 all Orgs are now on Summer 21 

General or Admin Summer 21 Changes 

Download Dashboard as a PNG file. 

Now after the summer 21 release, we will get an option to download the dashboard as a PNG file. Previously there was no provision available for us to download the Dashboard. Only we relied on a snipping tool to capture the dashboard images. 

 Record Access Reason in Lightning  Experience. 

In summer 21 Onwards we can see the Record Access Reason. Prior to Summer 21, we need to switch to classic to know the record access reason. In the below screenshot you can see a button Sharing Hierarchy this facilitates the record access reason view. 

 Track Your Active Licenses

Now we can see a lightning app called Lightning usage App. So once after accessing the app via App Launcher we will get an option to get an overview of Active licenses, assigned and available licenses. 

This overview helps the company to take the decision on whether do they need to buy new licenses or use do they have any unused licenses etc. 

Install More Custom Fields 

The total hard limit for custom fields per object is increased to 900. Each salesforce edition has a limit on the number of custom fields that can be created per object. If it exceeds a certain limit then we need to free up custom fields that are n longer needed. 

The new 900 fields hard limit applies only to these objects.

• Account
• AccountContactRelation
• Asset
• Campaign
• CampaignMember
• Case
• Contact
• Custom Object
• Individual
• KnowledgeArticleVersion
• Lead
• Opportunity
• OpportunityLineItem
• Order
• OrderItems (Order Product)
• Product2 (Products)
• Solution
• Users
• UserRole (Role)

 Inline Editing functionality on Report (Beta) 

This feature helps to do the changes on the Report inline. No need to navigate to the record detail to do changes to the column. This feature is in Beta. We need to contact salesforce to enable it. 

Set Expiration of Assignments on Permissions in Permission set and Permission Set Group (Beta) 

 While assigning the permission set to a user we will get a option to set up the expiration date.

Suppose a sales manager needs consultants to evaluate language used in sales contracts. You give the consultants access to the Contracts object and other permissions via a permission set group so that they can perform their work. The project has an end date, so you don’t want contractors to access sales contracts after that date. Set the expiration date and time zone for the permission set group when you assign it to users.

General Development Changes

Lightning Components

• Aura Components with UI namespaces are deprecated 

Created Quick Action for LWC components. 

We can create the quick action button for the LWC component. Before this release, we were relying on the aura component to expose the LWC component as a quick action. But now we can create a quick action if LWC  implements lightning__RecordAction interfaces. Now we will get an option to configure a quick action as a headless screen.

Here is the code for setting up the headless quick action 

<?xml version="1.0" encoding="UTF-8" ?>
<LightningComponentBundle xmlns="http://soap.sforce.com/2006/04/metadata">
   <apiVersion>52.0</apiVersion>
   <isExposed>true</isExposed>
   <targets>
       <target>lightning__RecordAction</target>
   </targets>
    <targetConfigs>
   <targetConfig targets="lightning__RecordAction">
     <actionType>Action</actionType>
   </targetConfig>
 </targetConfigs>
</LightningComponentBundle>

To use a headless action, add an exposed invoke() method to your component.

import { LightningElement, api } from "lwc";
 
declare default class HeadlessSimple extends LightningElement {
  @api invoke() {
    console.log("Hi, I'm an action.");
  }
}

Monitor Audit Trails for Lightning Components. 

This feature allows the user to track who changed the components when. This is useful whenever multiple users involved in the development activity. 

Flow updates

• Build Multi-Column Screen in Flow builder

We can now configure multi-columns in a flow builder. While defining the columns we will get options to configure the width of each column. And these screens are responsive in nature. 

• Use Is changed in condition logic for start elements and Decision Elements.

Now we have is Changed operator available for record trigger flow. With the help of this operator, we can make sure that certain logic can be executed only during the changes in certain values. Is changed operator available only during the record update. It won't available on record creation and deletion flow.

• Use ISCHANGED,ISNEW and PRIORVALUE in Record Trigger flow. 

Record Trigger flow for a new and updated record now support ISCHANGED,ISNEW and PRIORVALUE formula function.

None of this function available on flow trigger when a record is deleted. When copying formulas containing ISCHANGED and PRIORVALUE into record-triggered flows, use the $Record global variable instead of the object. For example, to use ISCHANGED(account.x) in a record-triggered flow formula, change it to ISCHANGED($Record.x). The ISNEW formula function requires no changes because it has no parameters.

• Control Picklist Requiredness More Accurately

On-Screen component while surfacing the picklist component we can define the picklist is Required or not. 

In previous releases, the picklist always has a value selected. If the default value is not passed then the first item will be set as default value. 

But in the current release --None-- option automatically prepended on the picklist. 

• Set a Default Value for Any Screen Component That Displays Choices

Now you can set a default value using any flow resource. Use a record query, an action, or another component. Or manually select a specific picklist value when you use a picklist choice set. Previously, you could only select a choice resource for the default value.

At a run time whenever we found a match on the default value against the list of picklist values then Default value auto selected.

In the above screenshot, you can see more than one option as default selected. This can be achieved by setting up the default parameter resource with; separated. Forex: Warm; Cold as a value for default parameter resource.

Sort And Limit Data in a Collection

Salesforce has introduced a new item into the Flow Pallet called as Collection Sort.

This collection sort item is helpful when we are handling a large set of records. This collection Sort improves the processing speed. 

When we surface the Collection Sort into the pallet we will get the following options

Debug a Flow to See When Transactions Are Committed

Schedule-triggered flows and auto-launched flows that have no triggers can now show debug details for transactions that are committed or that are rolled back due to an error. If a flow fails, you can debug the flow to see whether record changes were permanently saved to the database via committed transactions before the failure.

Where: This change applies to Lightning Experience and Salesforce Classic in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions.

Why: For example, a flow includes a Create Records element, an Update Records element, and an Action element that makes a call to an external system. The Create Records and Update Records elements modify records, so a transaction is committed before the Action element is executed. The flow fails after the Action element.

Previously, you couldn’t debug the flow to see where transactions were committed during the debug run. Now you can quickly see that after the Update Records element, a transaction was committed that included record changes.

How: Debug a flow in Flow Builder, and then from Debug Details, click Basic Debug Log. Select Show Governor Limit Consumption or Show Transaction Boundaries or both.

We moved the Show query limits in debug details check box from the Debug flow window to the debug details, so you can choose the details as you view them.

When you debug a flow from a flow error email, governor limits don’t appear in debug details.

Finding Failed Flow Easier. 

Before Summer 21 

After Summer 21 

I Listed only a few updates which I felt like good to share :) Please read through the entire release note to understand more. 

Thanks for reading. 

Have a nice day!