<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Pavan Chevvuri on Medium]]></title>
        <description><![CDATA[Stories by Pavan Chevvuri on Medium]]></description>
        <link>https://medium.com/@pa1chevvuri?source=rss-e9849bd431ef------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*EX7VMa8UVNo480eLgDHZ9A@2x.jpeg</url>
            <title>Stories by Pavan Chevvuri on Medium</title>
            <link>https://medium.com/@pa1chevvuri?source=rss-e9849bd431ef------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:10:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pa1chevvuri/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[New Minimum Access User Profile]]></title>
            <link>https://pa1chevvuri.medium.com/new-minimum-access-user-profile-f7f5006ab080?source=rss-e9849bd431ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7f5006ab080</guid>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[salesforce-lightning]]></category>
            <category><![CDATA[salesforce-productivity]]></category>
            <category><![CDATA[salesforce-tools]]></category>
            <category><![CDATA[salesforce-development]]></category>
            <dc:creator><![CDATA[Pavan Chevvuri]]></dc:creator>
            <pubDate>Fri, 31 Jul 2020 19:43:45 GMT</pubDate>
            <atom:updated>2020-07-31T19:43:45.067Z</atom:updated>
            <content:encoded><![CDATA[<p>If you have been on the Salesforce platform for sometime, we all have felt the pain of Deploying a new profile across the Environments.</p><p>With Summer’20 Initiated Release, Salesforce introduced a gem called “New Minimum Access Profile” that could save admins and developers a ton of time while they are working through deployments.</p><p>With Minimum Access Profile, now you can assign a least-privilege profile to a user, and then add more permissions via permission sets and permission set groups.</p><p>The Minimum Access — Salesforce profile includes Access Activities, Chatter Internal User, Lightning Console User, and View Help Link permissions.</p><h3>My Personal Experience :</h3><p>Here is what we did to test the new minimum access profile :</p><p>We created a new Profile with a clone of Minimum Access Profile in the Source Org.</p><p>test1 was we deployed source profile after cloning the minimum data profile in target.</p><p>test2 was we deployed source profile file from scratch in target ( meaning no profile exist in target)</p><p>We noticed more permissions test2 has compared to test1.</p><p>So my Recommendation to help you with deployments :</p><p>Always “Clone” New “Minimum-Access-Salesforce” Profile in the Target environment before you deploy, then deploy your Profile from Source to Target location that way you can ensure your Target Profile only has the desired permissions that are needed.</p><p>Reference :</p><p><a href="https://releasenotes.docs.salesforce.com/en-us/summer20/release-notes/rn_forcecom_general_new_profile.htm">https://releasenotes.docs.salesforce.com/en-us/summer20/release-notes/rn_forcecom_general_new_profile.htm</a></p><p>Thanks for reading this small tip!</p><p>Pavan</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7f5006ab080" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to improve Speed and Performance in Lightning Experience ?]]></title>
            <link>https://pa1chevvuri.medium.com/how-to-improve-speed-and-performance-in-lightning-experience-8d33b8373b9c?source=rss-e9849bd431ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d33b8373b9c</guid>
            <category><![CDATA[salesforce-tools]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[salesforce-lightning]]></category>
            <category><![CDATA[salesforce-productivity]]></category>
            <category><![CDATA[salesforce-development]]></category>
            <dc:creator><![CDATA[Pavan Chevvuri]]></dc:creator>
            <pubDate>Thu, 30 Jul 2020 22:55:58 GMT</pubDate>
            <atom:updated>2020-07-30T22:55:58.516Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to improve Speed and Performance in Lightning Experience ?</h3><p>Moving from Classic to Lightning at one point most of us have felt that Classic is faster than Lightning. But are you curious about why we felt that and is that true and what can we really do to actually improve the performance ?</p><p>Then this post is going to help you…</p><p>Lets first start by understanding the architecture of classic and Lightning : In Classic, web pages are generated by the server and then they are rendered on the client ( your desktop or mobile device ) But where as in LEX, pages are loaded on the users device progressively, component by component. Which is why some times we notice it is slower esp if your component contains complex logic to get the data or contain multiple sub components, load times would be even more.</p><p><strong>We can measure the performance in Lightning Pages by Calculating Experienced Page Time (EPT) :</strong></p><p>EPT Time is the time calculated from a Page starts loading to the time when No activity has occurred for at least two frames ( about 33 ms ).</p><p>we can measure EPT in the below ways.</p><p><strong>a. Lightning experience :</strong> Add an EPT counter to Lightning experience</p><ul><li>Enable Debug mode from Setup</li><li>Add “?eptVisible=1” as a parameter to the Lightning URL</li></ul><p>Ex: https://&lt;example&gt;.lightning.force.com/one/one.app?eptVisible=1</p><p>You will see something like this :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/417/1*l9XoEpBVLL_RZviWUyqyaA.png" /></figure><p>Best Practice : Always try to capture the timing when ever you try to make change to the Lightning Record/App Pages before you deploy to PROD.</p><p><strong>b. Using Lightning Usage App to see the EPT:</strong></p><ul><li>We can use the LEX usage app to view aggregated page and browser performance. Check it in your Production instance under the app launcer.</li><li>We could also build custom reports using below report types. (LightningUsageByAppTypeMetrics / LightningUsageByBrowserMetrics / LightningUsageByPageMetrics / LightningUsageByFlexiPageMetrics)</li></ul><p>Note : This is available only in PROD Org</p><p><strong>c. Event Monitoring :</strong></p><p>Event Monitoring is part of Salesforce Shield, and provides access to detailed performance, security, and usage data on all your Salesforce apps.</p><ul><li>Use Event Types : Lighntning Page View, Lighning Interactions, LEX Peformance to get the statistics.</li></ul><p>Now that you know why Experienced Page Time (EPT) is important and how it can be measured, let’s look at some factors that can affect EPT.</p><p>It can help us from identifying the performance Bottlenecks and troubleshoot the issues.</p><p><strong>Factors that affect the over all Page Performance :</strong></p><ol><li>Network: Conditions and “distance” between the device and the host instance.</li><li>Device: Available processing power, memory, and resources of your devices.</li><li>Browser: Specific browser processing capabilities and configuration.</li><li>Salesforce Configuration: Lightning page customization&#39;s, Visual force implementations, or specific org customization.</li></ol><p>In this post lest discuss some of the Salesforce configuration Issues that has impact on your Performance based on my experience:</p><ul><li>Always “Turn Off” Debug mode in Production Org.</li><li>Enable Secure and Persistent Browser Caching. This helps to load your data faster.</li><li>Make sure you design your Record Pages by using Lazy Instantiation of Custom Components by Splitting into Tabs/ Using Quick Actions/ Using the Global Actions.</li><li>Try to Break up the elements on the pages into App Builder Tabs which means present the most useful needed information on the first tab and move the less critical components to other tabs.</li><li>Reduce the number of fields you display on the details tab ( less than 50 recommended ) Check out dynamic forms and split them out to other tabs.</li><li>Try to have the most important Object Related List on the Primary tab and hide remaining related lists behind a secondary tab.</li><li>Build Custom Components using the LWC Frameworks. ( Use Lightning Base Components where ever possible ) <a href="https://developer.salesforce.com/docs/component-library/overview/components">Reference</a></li><li>Use Lightning Data Service instead of using Custom Controller where ever possible ( If you are a developer )</li><li>Measure the Lightning Component Time using the Lightning Inspector Chrome extension and see if there are any bottlenecks.</li></ul><p><strong>Useful References :</strong></p><ul><li>Check this out if you want to learn more : <a href="https://trailhead.salesforce.com/content/learn/modules/lightning-experience-performance-optimization">Trailhead Module</a></li><li><a href="https://developer.salesforce.com/blogs/developer-relations/2017/04/lightning-components-performance-best-practices.html">Developer Tips for Performance</a></li></ul><p>Thanks for reading this Post! Stay Safe!</p><p>-Pavan</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d33b8373b9c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>