Every release comes with plethora of features and innovations that empowers you to connect your customers. Today in this blog we will cover some interesting features that comes under the winter release.
So, here are list of features :-
1. Lightning Components Can Access Public Apex Methods Only in the Same Package :
An Apex class method of an lightning component can't call other apex class method of other package, even if they belongs to same namespace. Which was possible in earlier release. You can’t use the @NamespaceAccessible Apex annotation in an Apex method referenced from a Lightning component.
2. Aura Components in the ui Namespace Are Being Retired :
The ui components are scheduled for retirement in all Salesforce orgs in Summer ’21. Use similar components in the lightning namespace instead. Retiring the legacy components enables us to focus on components that match the latest web standards in performance, accessibility, user experience, and internationalization.
Where: This change applies to orgs with Lightning components in Lightning Experience, Salesforce Classic, and all versions of the Salesforce app.
When: Salesforce plans to end support for Aura components in the ui namespace in Summer ’21. You can continue to use these components beyond Summer ’21, but we won’t accept support cases after that release. For instance
Replace with lightning:menuItem and lightning:buttonMenu.
Replace with lightning:button, lightning:buttonIcon, or lightning:buttonIconStateful. For button groups, use lightning:buttonGroup.
3. Navigate Users Directly to an App
Now you can create Lightning web components and Aura components that navigate users to a specific page in an app.
Where: This change applies to Lightning Experience in all editions. This change doesn’t apply to Lightning Out, Lightning communities, or the Salesforce mobile app.
How: Now you can create components that link directly to your app and to a specific page in your app.
Use the lightning-navigation Lightning web component or the lightning:navigation Aura component with the new standard__app page reference type.
To navigate users to an app, pass either the appId or appDeveloperName URL parameters to the appTarget.
To navigate users to a specific page in an app, include the pageRef attribute.
4. Enforce Field-Level Security in Apex (Beta)
The stripInaccessible() security feature for field-level data protection has moved from pilot to beta and is available in production orgs.
Where: This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions.
Why: You can use the stripInaccessible method to strip the fields that the current user can’t access from query and subquery results. You can use it to remove inaccessible fields from sObjects before a DML operation to avoid exceptions.
How : If the user doesn’t have permission to read the Phone field of a Contacts object, this example code removes the subquery field before reading the records. The DML operation completes without throwing an exception.
5. Add List and Related List Components to the New Salesforce Mobile App :
List View, Related List - Single, Related Lists, and Related List Quick Links components are updated to support mobile navigation and the new Salesforce mobile app. When you place the List View component on a record page, a View More button loads more records in batches, so you can easily get more records or scroll to the information you want.
Where: This change applies to the new Salesforce mobile app in all editions, except Essentials and Database.com.
When: You can give this feature a try in Lightning App Builder right away.
Who: Available to users with the New Salesforce Mobile App user permission.
How: To add the Related List - Single and Related List Quick Links components to the new Salesforce mobile app, add the components to a Lightning page in the Lightning App Builder while in the mobile view.