Classic to Lightning Journey Part-1

If you are a big organization with many custom profiles, thousands of users assigned to them, point and click Configuration and customization as required for the business, you will have to do a peer review before enabling Lightning for any user in your organisation.

Here are some considerations prior to enabling lightning in production org. The first thing you should check is the browser and its. Check if the browser of choice for the organization is capable of rendering Lightning pages. Best to think about long term usability from a browser road map perspective rather than just the status quo. Sometimes it is best to wait until a newer version of the browser is made available.

This should be considered as a priority and should not be left until the end. To know which browsers are supported in Lightning, You can refer:- Supported Browsers for Lightning Experience

I will highlight some of the issues related to this:-

• On behalf of login might not work- Your sales manager might face the issue while trying to log in as any other reps reporting to him.
• IE11 is the default browser on WT8. Javascript engine isn’t good at rendering Lightning pages
• Even if you have opted for extended IE11 support from Salesforce which covers until Dec 2020 for any functionalities that work on modern browsers but not on IE11, but it does not cover you for Performance issues
• Significant performance issues around page load – especially reports/dashboards where large amount of data is to be processed and presented
• Error Message soon after login to Lightning Experience
• If you have any AppExchange package which is built on Lightning component framework, it will have a significant performance issues on Internet Explorer. You may get internal error messages. For an example, standard sharing action is not available in Lightning, so you might have to install the app exchange package provided by Salesforce labs which may not work properly in unsupported browsers.
• If you have a standard news component on the home page in Lightning experience, it may not load properly on unsupported browsers.
• If you have embedded any custom Lightning component, your developer will have to test for browser compatibility.
• If you are using the standard sales path component and embed any link outside of Salesforce as guidance for success, you may get intermittent popup messages something on the lines of:  “Navigate to this page? We’d like to open the Salesforce page https://google.com… in a new tab. Because of your browser settings, we need your permission first.“

Now, we have talked enough about browsers, Once you have finalized on the browser aspect, the next thing to do is to run the Lightning Experience Readiness Check.  Before you run the Lightning Experience readiness reports directly,  I would like you to follow these steps:-

• Preview Your Org in Lightning Experience – Use the preview feature to assess how your Salesforce apps look like in Lightning Experience. You have to do a comparative study in terms of availability of buttons, Vf page embedded in the layout, Third party AppExchange, Sidebar component,  Home page component in Lightning. By doing this, you will get a feel of the gaps you’ll encounter while using Lightning v/s Classic.
• You now have to identify the visualforce pages which have to be fine tuned to correct the look and feel. Visualforce pages need to be restyled in accordance with the Lightning Experience UI. This information will not be provided on the Readiness Check Report. The Readiness Check Report  will only highlight the tags that are not supported in Lightning or if any javascript code is used within the visualforce page.

Once you have done a comparative study using the report to establish the differences between Lightning and Classic, you are good to proceed. As an Admin/Developer, you have to ensure that users don’t lose any existing functionality because not everything gets highlighted on the Readiness Check report.

In summary, remember the following while planning the migration to Lightning:

1. ) Think Browser – think long term
2. ) Preview the org in Lightning Experience
3. ) Run the Readiness Check
4. ) Compare and contrast Lightning v/s Classic to ensure end users do not get     impacted by missing functionality.

To be continued in next blog…