Published by: 0

For over 16 years, the look and feel of Salesforce has remained fairly consistent. In 2015, Salesforce began promoting its new platform – Salesforce Lightning. Lightning is the new face of CRM. By switching it on, you could access to the latest innovation. You also get each and every Lightning improvement updates from Salesforce. Modern Lightning UI brings new features, increased productivity, faster deployments, and a seamless transition across desktop and mobile environments.

1) Mobile First – Lightning
Salesforce1 App is built on top of Lightning Platform. Now Lightning Desktop is available and become one platform for both Desktop, Mobile and Other devices. Any and every customization that happens there is immediately accessible on any Desktop, Mobile device via Salesforce1

2) Salesforce Einstein
Salesforce has launched its newest feature called Einstein, an artificial intelligence (AI) tool to help determine companies be more predictive about their customers. Leverage Einstein to predict the quality of a lead, recommend best next steps, and even automate tasks.

3) Lightning Builder
With Lightning Builder anyone can drag and drop Lightning Components to build mobile and desktop apps, and customize pages in Lightning Experience. There are three types of components in Lightning Builder: Pre-built components from Salesforce, components from Lightning Exchange built by partners, and custom components.

4) AppExchange Apps
There are now more lightning ready third-party apps available in AppExchange, all pre-vetted and pre-integrated to work in Salesforce. Lightning ready apps are designed to deliver the most consistent user experience as you move your organization to Lightning. Look for the “Lightning Ready” symbol on AppExchange

5) Lightning Customer Community
The Lightning Customer Community is the most feature-packed release in the history of Community Cloud, enabling companies to quickly and intelligently engage with their customers. The all-new UX offers a new level of personalization, plus engagement opportunities that help your business provide an unparalleled customer experience.

6) Sales Path
Sales Path allows you to define the key stages that a Lead or Opportunity needs to go through, and highlight the important fields per stage that a sales rep needs to complete. Sales reps can now easily enter important information and move the deal through its stages to quickly close deals faster.

7) Kanban View
Easily manage opportunities in the new Kanban view. This view shows up to four key fields on an opportunity and allows you to drag a record to the next stage. Quickly create tasks and events directly related to the opportunity without leaving the view. Stage amounts are recalculated in real time when an opportunity advances, allowing you to see the most up to date pipeline information.

8) Enhanced Reports, Charts, and Dashboards
Reports have a new design that look modern with enhanced functionality. You can even add reports to List Views! Dashboards also got a huge upgrade and are no longer restricted to three columns and will instantly refresh.

Considerations while Moving to Lightning
Although there are many benefits with switching to Lightning, not all functionality is supported and there are some things you will want to consider before making the switch. The below list is not an extensive list of unsupported features, but rather some items that you will want to consider before migrating to Lightning.

a) AppExchange Apps – If you are using any AppExchange apps, ensure that they are Lightning Ready. If the app is supported in the Lightning Experience, a “Lightning Ready” sash appears on its AppExchange listing.

b) Custom JavaScript buttons – These are not supported within Lightning, however quick actions, triggers, or workflow rules can be built as a possible alternative.

c) Visualforce Pages – If your company relies on custom Visualforce pages, you will want to review these and determine which ones are necessary and need to be migrated to a new Salesforce Lightning Component. Deciding which Visualforce pages to migrate first should not be a trivial decision. I suggest you start small and look for pages that simply query data and display the results. Lightning Component development is very different from Visualforce page development. If you are not comfortable working with JavaScript, it will likely take you a while to make the adjustment.

Once you get more comfortable creating components, you can move towards converting larger Visualforce pages. But even then, you should do it in a series of stages. You can break up your page into a set of smaller components and convert them one at a time.

If you have many users on Salesforce classic and you want to slowly get them used to the new look of Lightning Experience, while also getting your feet wet, you should consider first just converting your pages to use the SLDS.

d) Out Of Lightning Components for faster development – When Lightning development was first introduced, it came with a set of built-in user interface (UI) components that would allow you to collect or display input from your users. Even though these components were helpful, they left a lot to be desired. List of what components are available continues to grow with each new release.

For simple components that only need to access a single sObject and use the recordID as the basis for the query, the Lightning Data Service is definitely the way to go. I say this for two big reasons. The first is that components built with the LDS will likely render faster since it is built on a highly efficient local storage that is shared across all components.

e) Check Known Issues – Good to check the known issues in Lightning as you might get more granularity about the issues. For known issues, check Click Here

I hope these tips help you in your migration to Lightning Experience. Interested in learning more? Fingertipplus team is always on top of the latest Lightning/LEX development and are here to help with your migration. Contact us to know more.

Leave a Reply

Your email address will not be published. Required fields are marked *