Gear Up for Lightning: Top Six Items To Address
With the upcoming Winter ’20 release in October, Salesforce will start auto-transitioning organizations to the Lightning Experience. Lightning has only gotten better since it first launched in 2014, and Salesforce is doubling down to encourage customers to make the switch from Classic. And this is a good thing! Lightning offers better productivity for end users, and who doesn’t want that?
Below are the six most common action items we see organizations need to address to take full advantage of the Lightning Experience. Many of them are ones that a Salesforce admin can do declaratively, and Salesforce offers a ton of resources to make this transition as easy as possible.
But before you do anything, make sure to run your Lightning Experience Readiness Report! There might be some action items specific to your organization that aren’t addressed here, especially if you have a more customized instance. You can access the report from the Lightning Experience Transition Assistant in the Setup menu.
Documents, Notes & Attachments
Salesforce will no longer support Documents or Notes & Attachments in Lightning. Instead, users will use Salesforce Files and Enhanced Notes. Existing Attachments can still be viewed and downloaded in Lightning, however we recommend converting those Attachments to Files for a long-term solution. Luckily, Salesforce provides an easy-to-use converter tool on the AppExchange, Magic Mover, for Notes and Attachments. For organizations using Documents, admins will need to export all Documents from Salesforce and re-upload them as Files. Once you’ve converted everything to Files, make sure to edit your object page layouts to show the new Files related lists!
Activities are available in Lightning but act a little bit different (read: better!). The separate Activity History and Open Activities related lists no longer exist. Instead, users will manage activities using the activity timeline, a single consolidated list. To make sure users can create tasks, schedule events and log calls/emails, add the appropriate actions to the Mobile and Lightning Experience Actions on your page layouts.
With MyDomain, you can include your organization’s name within your Salesforce URL, for example, “https://myorganization.my.salesforce.com”, and replace the seemingly random number Salesforce provides for you. Not only does this look cool, using MyDomain allows your organization to use single sign-on (SSO) capabilities from external identity providers (like Okta), social sign-on, and Lightning components. Elevate your branding AND your security!
Custom URL Links
With your new Salesforce URL using MyDomain, any hard-coded URLs within your instance will need to be updated to reflect it. Hard-coded URLs are any URLs that reference your specific instance. Your Readiness Report will check for this, but it won’t include everything. Be sure to check if you have any hard-coded URLs at least in your email templates, home page components, web links, workflow, triggers, classes, Visualforce pages, and tabs. If you’d like to do a more comprehensive check, you may need developer support.
The Lightning Readiness Report scans all installed packages in your organization and identifies which ones may not be supported in Lightning. In most cases, organizations may just need to upgrade to the newest version and can work with the third-party publisher. To check if the package works in Lightning, look out for the “Lightning Ready” symbol on its AppExchange listing! If the package isn’t compatible, then a workaround is needed. Be sure to check the new Lightning features and the AppExchange for alternatives. Who knows, maybe that feature you installed an app for was part of a recent Salesforce release!
If you have Visualforce pages in your organization, be sure to run the additional report that Salesforce provides to get more details on which pages may have issues in Lightning and recommended action steps. Unfortunately, if the Visualforce page isn’t compatible in Lightning, it will require developer support to refactor the code.
As with any rollout, be sure to test, test, test before switching it on for all your users. Have your power users from each department do their daily functions in Salesforce to ensure everything is working as expected.
If you really don’t want to switch to Lightning Experience, there is a way to “opt-out” of the rollout. But beware! All of Salesforce’s new feature development will happen in Lightning moving forward. To make sure you can take advantage of Salesforce’s releases, make switching to the Lightning Experience a priority for your organization before October!