Monday, 24 April 2017

Summer'17 : Top New Features

Top New Feature Coming in Summer 17 Release

1.  Get Expanded Analysis When You Check Your Lightning Experience Readiness  


The Readiness Check is chock full of more actionable advice, including specifics on resolving your JavaScript buttons and links, who’s ready to migrate, and how to use your report to inform your migration plan. And since it only takes one click to get a personalized report sent straight to your email inbox, there’s no reason to wait to kick off the Readiness Check. This change applies to both Lightning Experience and Salesforce Classic.

2. Lightning Sync for Google: Two-Way Sync, General Availability

#Events #Sales

Make your teams more productive by setting up contacts and events to sync between your G Suite account and Salesforce. These changes apply to Lightning Experience, Salesforce Classic, and all versions of the Salesforce1 mobile app.

Now contacts sync in both directions between Google Contacts and Salesforce. Set up reps to sync both ways so that they can create and edit contacts from the application that’s most convenient to them: Gmail or Salesforce. This change applies to Lightning Experience, Salesforce Classic, and all versions of the Salesforce1 mobile app.
No need to hold off any longer! Lightning Sync for Google is generally available and open for business! When you set up your reps to sync contacts and events between their G Suite account and Salesforce, you give them an opportunity to be more productive. Save your reps time and eliminate unnecessary data entry while also doing your part to promote Salesforce adoption across your team. This change applies to Lightning Experience, Salesforce Classic, and all versions of the Salesforce1 mobile app.
Reps have tons of appointments on their calendars, but only a subset of those events contains valuable data that reps want to track in Salesforce. Now setting up reps for both Lightning for Gmail and Lightning Sync lets them choose which Google Calendar™ events sync to Salesforce. This change applies to Lightning Experience, Salesforce Classic, and all versions of the Salesforce1 mobile app.
When Salesforce moves faster, you and your reps can move faster, too. We’ve tinkered under the hood so that contacts and events sync more frequently between your reps’ G Suite account and Salesforce. No setup necessary—you can kick back while your reps enjoy an improved sync experience. This change applies to Lightning Experience, Salesforce Classic, and all versions of the Salesforce1 mobile app.
3.  Kanban: More Objects, More Settings
#Sales #Kanban
Several enhancements make the Kanban View easier to use. These changes apply to Lightning Experience only.
Display Knowledge and Social Persona records in an entirely new way by switching to Kanban view. This change applies to Lightning Experience only.
Money isn’t everything. In the Kanban view, reps can summarize by numeric fields, not just currency fields. This change applies to Lightning Experience only.
Your reps can configure the Kanban view to group cards by the record’s owner. This change applies to Lightning Experience only.
Reps can see in a glance which Kanban cards they don’t have permission to drag.

4. Service Console: Increased Efficiency for All (Generally Available)
The Service Console in Lightning Experience is now generally available and includes a bunch of enhancements. Features like split view, keyboard shortcuts, case hovers, and more are aimed at keeping your support agents productive. With Community 360, agents can see which articles a customer has looked at. But we didn’t forget about our awesome admins. Now you can set up service-related features like Lightning Communities and Lightning Knowledge in a jiffy.
To keep your support agents happy and efficient, we’re giving them some awesome new features. Keyboard shortcuts and split view let agents manage cases faster and with fewer clicks. Combine all that goodness with the new Omni-Channel utility, and your agents have even more power at their fingertips. These changes apply to Lightning Experience only.
Our setup flows take the guesswork out of enabling core service features. Great for newbies or seasoned admins, setup flows walk you through the setup process without having to consult a help topic. Lightning Service now offers setup flows for Lightning Knowledge and Lightning Communities. In the Recommended Setup window, we've also added an easy way to customize your case statuses. This change applies to Lightning Experience only.
Help support agents decrease customer frustration, and improve support. Community 360 shows support agents working in the console whether customers have already looked at pertinent documentation, and if they’ve already filed any cases before calling support. Agents don’t suggest articles customers have already accessed, or open duplicate cases. This feature is new in Lightning Experience.
5. Move Communities Between Orgs with Change Sets
Change sets are now available for Lightning communities and Salesforce Tabs + Visualforce communities, making it easy to move your community between orgs that have a deployment connection. Create, customize, and test your community in your sandbox environment and then migrate the community to production when testing is complete.
Community migration is also supported via the Metadata API.
6. Announcing Partner Central—The New Partner Community Solution
Recruit, onboard, and manage your partner relationships from a central location built on the new, native Lightning solution: Partner Central. Extend your CRM tools and data to channel partners in a responsive, flexible community that is powered by Lightning and the Salesforce platform. Welcome to the new way to drive channel sales!

7. Stay on Top of What Happens in Your Communities with Global Notifications

With Global Notifications, your members receive messages wherever they are working, whether in their communities or in their apps. Members receive notifications on any screen—mobile, tablet, and desktop. This functionality is available in communities based on Customer Service (Napili), Partner Central, and any Lightning Bolt solutions.
Notifications in communities
All events that trigger notifications (@mentions and group posts) are supported. Members can even trigger notifications on record feeds. For example, an internal member can trigger a notification from the Salesforce org by @mentioning an external member on a lead or opportunity. When a member clicks a notification, the originating detail page or other appropriate location is displayed for seamless collaboration across communities and apps.
By default, the Notifications icon is hidden in existing communities and displayed in new communities. For the default Customer Service theme layout, show or hide Notifications for your members by selecting Hide Notifications icon in community header in Settings | Theme in Community Builder.

8.  Promote Your Picklist Fields to Global Value Sets
Global Picklists became generally available Winter ’17. Since then, we’ve been busy adding features, and now you can migrate existing picklist fields into global value sets.
Promote a single picklist field into a global value set by editing your picklist field and clicking Promote to Global Value Set.
Field edit dialog showing the Promote to Global Value Set button.
A new global value set is created, and the promoted field now references it. You can also use the new global value set for other fields.
There are a few limitations to be aware of:
  • You can only promote fields that have fewer than 1,000 values (both active and inactive).
  • You can only promote restricted picklists. If you want to promote an unrestricted picklist, first convert it to a restricted picklist.
  • You cannot promote a field to an existing global value set. But check out this Salesforce Lab App for some help.
  • After a field is promoted, you can’t demote it back.

9. Retrieve and Deploy Metadata Using Apex
Salesforce uses metadata types and components to represent org configuration and customization. Metadata is used for org settings that admins control, or configuration information applied by installed apps and packages.
Previously, accessing metadata required using the Metadata API, but you can now use classes in the Metadata namespace to access metadata components from Apex code.
Access metadata from your Apex code to handle tasks such as:
  • Customizing app installs or upgrades—During or after an install (or upgrade), your app can create or update metadata to let users configure your app.
  • Customizing apps after installation—After your app is installed, you can use metadata in Apex to let admins configure your app using the UI that your app provides rather than having admins manually use the standard Salesforce setup UI.
  • Securely accessing protected metadata—Update metadata that your app uses internally without exposing these types and components to your users.
  • Creating custom configuration tools—Use metadata in Apex to provide custom tools for admins to customize apps and packages.
Metadata access in Apex is currently limited to custom metadata records and page layouts. You can retrieve, create, or update custom metadata, but you cannot delete metadata through Apex.

10.  New Option for Parallel Testing on the isTest() Annotation

Use the @isTest(isParallel=true) annotation to indicate test classes that can be run in parallel and aren’t restricted by the default limits on the number of concurrent tests. This makes the execution of test classes more efficient, because more tests can be run in parallel.
This annotation overrides settings that disable parallel testing by default. A test class that doesn’t have this annotation is restricted by the default limits on the number of concurrent tests.

11. Lightning Data Service (Beta)
Lightning Data Service is now in beta. Use Lightning Data Service to load, create, edit, or delete a record in your component, without using Apex code. Lightning Data Service handles sharing rules and field-level security for you. Lightning Data Service also improves performance and user-interface consistency.
With the move to beta, force:recordPreview has been deprecated and replaced with force:recordData. If you’re using force:recordPreview, you must refactor your components to use force:recordData.
With force:recordData, the targetRecord attribute has been updated to return records in a new shape using the UI API.

12. Override Standard Actions with Lightning Components
At long last, you can override four of the standard actions on objects—View, New, Edit, and Tab—using Lightning components. You can override these actions on standard and custom objects. Overriding standard actions allows you to customize your org using Lightning components, including completely customizing the way you view, create, and edit records.
The ability to override standard actions has long been possible using Visualforce pages. It’s also long been a top request for Lightning components. We’re thrilled to be adding this feature, and we hope you find it just as exciting. (This isn’t just a feature, it’s an adventure.)
All of that said, there’s a lot you need to know to successfully use action overrides with Lightning components. On the surface, adding an action override that uses a Lightning component is almost exactly the same as using a Visualforce page. You simply choose a different item, and away you go.

There a lot many other feature as well, Offical release notes  is available HTML format as well as PDF file.


Post a Comment