Spring 16 Release – Sales Cloud Highlights
A new year, and three new Salesforce releases to look forward to! As predicted, the Spring 16 release looks set to focus mostly on Lightning enhancements – and there are a lot of them! Here are my favourite features, both Lightning and Classic, for the Sales Cloud:
Person Accounts: Supported in Lightning Experience (Beta)
An anticipated feature for lots of Salesforce users considering switching over to the Lightning Experience, Person Accounts is now compatible with both Salesforce Lightning and Salesforce Classic. Previously, users couldn’t set up Lightning in Production if Person Accounts was enabled (and Person Accounts cannot currently be deactivated), but the wait is over! Do be aware though, this feature is in Beta, which means there are some known limitations (see page 76 of the release notes here for details on these).
Campaigns: Supported in Lightning Experience (Beta)
A good addition for a more complete Sales Cloud solution, Campaigns are now supported in Lightning. Users can create Campaigns and view Campaign list views easily from Lightning.
In addition, Lightning also supports adding Campaign Members via import wizard insert. Users will also be able to see the Campaign History against associated Leads, Contacts and Person Account records. Unfortunately, the functionality to add Members from records already in Salesforce is not yet available in Lightning – but hopefully will be coming soon in a future release. Again, another feature in Beta – you can read the limitations on page 77 here.
Inline Editing on Records: Lightning Experience
Users can now edit individual fields on a record detail page and easily edit multiple fields at one time. Also, if a user tries to navigate away from the page, they receive a warning message to let them know the edit has not been saved – no more lost edits! Note: Inline editing for list views is still only available in Salesforce Classic.
List View Enhancements: Lightning Experience
You can now create custom list views and edit the columns displayed whilst still in the Lightning interface. Filters can also be added to list views like they can in Salesforce Classic, as well as being able to resize columns.
Additional extras you get with Lightning on list views is the ability to add charts and also search for a list view by name – nice little additions to make list views even more useful in future!
Email Enhancements: Lightning Experience
There are a few different email enhancements in this release, and I really like them all! Firstly, you can now pop out the email composer, allowing you to have split screen whilst drafting an email. It also gives users flexibility to navigate to different related records, for example, whilst keeping the email editor open.
You can also create email templates and search for merge fields much more easily. Once you have drafted an email, there will be an option to save as a new template to allow you to reuse in future. Merge fields can now be searched for, which means we no longer have to spend time scrolling down lists of fields to find the right one!
Email Enhancement: Lightning Experience and Salesforce Classic
Email preferences are now also being utilised when composing an email, so you are warned if a Lead or Contact has opted out of email communications. This is a great addition, which makes the most of the email opt out functionality.
Collaborative Forecasting with Custom Fiscal Years: Salesforce Classic
Users who have Custom Fiscal Years can now use Collaborative Forecasting. This feature will be really useful for those of you who want to use Forecasting on a custom currency field or with Opportunity Splits functionality.
URL Custom Button and Link Support: Lightning Experience and Salesforce1
URL custom buttons and links will now be supported in Lightning and Salesforce1! This is big news for many users, who were previously blocked from even considering Lightning because their sales processes were relying heavily on custom buttons. Approach with caution though – I tested this in my pre-release sandbox and although the custom button brought up the correct page, none of the information was pre-populated.