Home > Uncategorized > daily 02/15/2018

daily 02/15/2018

    • Many of the Salesforce Clouds, such as Sales Cloud, Service Cloud, and Pardot, have already received design overhauls if they were born in Classic. 
    • for example, Kanban View and Report Builder (beta) etc., but, it is also putting effort to migrate features from the Classic interface to Lightning Experience (For example, Collaborative ForecastsEnterprise Territory Management, and, Add a Case Comment from a Related List, etc).
    • Territory Management, Collaborative Forecasts, Report folder sharing, Sharing your calendar with co-workers, Case Milestones, Service Contracts, Lightning Report Builder (beta), etc


    • can get an idea about all out-of-the box functionalities they are currently using; and, also about the customizations within the customer’s organization. Lightning Experience is undergoing rapid development. As a result, many of the current limitations will be addressed and covered in the next few releases.
    • When you add a product to an opportunity in Lightning Experience or Salesforce1, and the product has default schedules,Salesforce doesn’t create the schedules.
    • Salesforce ‘Classic’ and ‘Lightning’ can be used in unison, and users can switch between the two. Whether your company would become more productive depends on how it uses salesforce.
    • For this reason your company should ensure that all (or at the very least most!) day-to-day features required by your users are available in Lightning before migrating.
    • The downside is that whilst switching to Lightning offers greater flexibility in both Dashboard design and appearance, unfortunately not all of the Classic features can be configured in Lightning.
    • Users can’t create additional Reports & Dashboard folders
    • If your team relies on List Views to work sets of records, be it Opportunities or otherwise, then you’ll need to consider the implication of Lightning’s new List View visibility before switching.
    • This removes the ability to grant visibility to users based on their Role or membership of a group. An added complication is that ‘All’ users includes internal and partner users.
    • At GSP, we advocate the use of Products to almost all of our customers.


    • Product Schedules aren’t available in Lightning.


    • From what I’ve read, it seems that it’s currently more for companies that are looking to develop custom apps via the salesforce lightning platform and have those work more seamlessly on the Salesforce1 app since that runs on lightning. But I also know there’s a huge learning curve due to the huge re-organization for the UX.
    • Now some of what you develop might be compatible with Lightning and some of it might not be (like URL hacks, VF pages etc.) and the incompatible features will need revamping to be supported by Lightning.
    • Also, I would do a thorough gap analysis using the checklist provided by Salesforce and ssee where you stand and then build a transition plan from that point.
      • Lightning App Builder: visual user interface designer

      • Lightning Components and Design System: reusable user interface building blocks

      • Lightning Process Builder: visual business process designer

        • Lightning Connect: real-time integration with external data source systems

    • many solutions and applications have yet to convert to Lightning as well
    • your Salesforce instance won’t implode, but it also won’t be perfect

Posted from Diigo. The rest of my favorite links are here.

Categories: Uncategorized
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: