skip to Main Content

Lightning is Finally Ready, Time to Get Onboard: Part 1

Roadmap lightningIt’s a wrap! Dreamforce 2016 was an exciting—and exhausting—week of learning, networking and strategizing for the future. Here’s my key takeaway.

Traditionally, one of my favourite sessions is True to the Core. True to the Core started from this idea that Salesforce was turning away from its core mission. Certain feature roll-outs (Chatter in particular) initiated criticism that Salesforce had started to abandon features that are core to a CRM product. Things like multi-select picklist enhancements and state/country picklists—really basic stuff that was not in the platform

Enter True to the Core, led by Parker Harris, co-founder of Salesforce. What’s always interesting about the session is that Parker Harris is very responsive; it’s basically a Q and A. The presentation is stripped of the bells and whistles you see at other SFDC events and really gets down to specifics. And this year, before we even got to any of the questions, Parker Harris made one thing extremely clear: “True to the Core now means Lightning.”

That’s how the session started: “True to the Core now means Lightning.” And this idea resonated throughout the entire conference. Case in point: All the roadmap sessions this year presented Lightning as the driver of all features.

Roadmap sessions explore what’s coming up in the next release, and in the releases afterwards. Roadmaps will tell you when to potentially expect certain enhancements and features. All the roadmap demos were done in Lightning—which is significant since this was obviously planned. At these sessions, it was made clear that, with few exceptions, all new end-user features will be rolled out in Lightning only. The roadmaps also made it clear that the majority of features in Classic will now be supported in Lightning, starting with the Winter ’17 and Spring ’17 releases.

See Part 2 of my post, where I reveal the 3 reasons why your org needs to move to Lighting, stat!

Back To Top