Salesforce Release

Summer ’18 Salesforce Lightning Experience and Classic Highlights

Summer18LogoThe list of Summer ’18 features below apply to both Salesforce Lightning Experience and Classic.

There are additional Summer ’18 features available to Salesforce Classic Only, Lightning Experience only, Community Enhancements, Other Enhancements in the Summer ’18 Release Highlights post.

Note: These features are not listed in any specific order.

1. Custom Metadata Type Enhancements:

  • (Generally available) Use custom data metadata types in validation rules. Thank you, Salesforce, for delivering my idea! For an example of how you would use this, read the blog post.

View image full screen

Use the $CustomMetadata global variable in validation rule formulas to dynamically reference custom metadata types using the syntax $CustomMetadata.type.record.field.

  • Retrieve custom metadata type list views via the metadata API so they can be packaged and deployed.

2. Survey enhancements:

  • Make survey questions reflective. Configure follow up questions based on answers to initial questions.
  • Ability to copy a survey.
  • View on the contact record whether the contact has been invited to participate in a survey.
  • Rank questions from a scale of 1 to 10.

3. Marketing can only see campaign member details you want them to via sharing rules inherited from lead and contact rules or from the campaign.

4. If your org has enabled Contacts to Multiple Accounts, when a sales rep converts a lead to an existing contact, s/he can associate the contact with a new or existing account.

5. Use Einstein bots to gather and qualify customers on routine issues or escalate to live agents. Note: Einstein Bots is available to orgs with Service Cloud and Live Agent user licenses, but the Einstein Bot is setup is only available in Lightning Experience.

6 Support reps can view community activity on assets, contracts, custom objects, orders, products, and tasks. Record filtering by object is available in Lightning Experience.

7. Lead Public Read/Write/Transfer OWD setting allows users to merge and delete leads if your org also has the Org-Wide Merge and Delete setting.

LeadOrgWideMergeDelete.GIF

8. “Email Templates” has been renamed to “Classic Email Templates” to distinguish Classic from Lightning email templates.

9. Optimize performance in situations where a large volume of business accounts are associated to a single community user by using a single shared person role. Under Sharing Settings | Other Settings, enable Use person role for first user in community account.

10. Access files quicker via the Recent Files dropdown on the top menu

11. (Pilot) Use the Einstein Next Best Action to have Einstein recommend actions and offers

12. Data Privacy Enhancements:

  • Determine when merging leads and contacts that have data privacy records, if you want to always retain the most recently modified data privacy record.
  • The individual object is now a complete standard object.
  • When users no longer want their personal data in Salesforce, permanently scramble the data with the new System.UserManagement.obfuscateUser Apex method.

13. Lightning Flow Enhancements:

  • Have up to 5 active flows in Essentials and Professional Editions
  • Using lightning components as flow actions. Local Action elements call the client-side controller of a Lightning component, allowing you to integrate with the browser – you can pull data directly into your flow without going through the Salesforce server, open a URL in the browser or redirect a user to the detail page of the newly created record.
  • Display a progress indicator or breadcrumbs of a flow to your users with stages, using new stage resource and new system variables: $Flow.ActiveStages and $Flow.CurrentStage.
  • Count, manipulate active stages as your users navigate through the flow by updating active stages and collections with assignment operators.
  • Use Date/Time variable in your flow to capture times.

DateTimeVariable.gif

View image full screen

  • Use flows to guide console users through processes. Flows associated to a record are launched as a subtab.
  • Use the debug function in Cloud Designer to test and troubleshoot your flows. Anyone who has worked with flows knows how HUGE this feature is to have visibility into what your flow is doing behind the scenes as it executes.  Thank you Arnab and team for this!

FlowDebugger.gif

View image full screen

  • Send flow error emails to the Apex exception email recipients you specify in Setup. It no longer has to go to the Admin or Developer who last modified the flow.

ApexException.gif

View image full screen

  • Tired of getting sandbox flow fault emails and not knowing which of the many sandboxes it came from? Now, flow fault emails will include the org name and ID in the error email! For those like me who have a multiple production orgs with gazillion of sandboxes (you have a sandbox, and you have a sandbox!), this is another HUGE feature and eliminates the guessing as to which sandbox this came from.

FlowEmail.GIF

  • Use debug logs to identify which flow or process actions contribute the most against governor limits.
  • Check whether flow or process bulk operations aren’t executing in bulk by reviewing the new FLOW_BULK_ELEMENT_NOT_SUPPORTED debug log line.
  • Process and flow fault messages shown to end users are friendlier and include the process name and error ID for users to pass along to the administrator.
  • More granular batching of scheduled process actions and waiting flow interviews help avoid runtime errors. Previously, a batch could include different process or flow versions started by different users which could exceed the 100 SOQL query or run DML operators on both standard and setup objects, which fails. To help you avoid limits, scheduled actions or waiting interviews are executed together only if they have the same execution time, the same process or flow version ID and the same user ID who triggered the process or interview.
  • (Critical Update) Enable query bulkification helps your org avoid reaching SOQL limits.
  • (Critical Update) Allow for a partial save for those successful processes rather than roll back all the records (all or nothing) in a given batch if one record in the batch failed to save.
  • A flow interview in Lightning runtime ends when a user is logged out.

14. (Generally Available) Track time with the time field. This can be used in formulas, validation rules, lightning UI components. For more information on the enhancements since beta and what you cannot use it for, read the release notes.

15. Ability to override the default sender of approval email notifications from the user who submitted the approval to an org wide address.

16. Use a formula to set the predefined value in a picklist on a quick action.

17. Standard permission sets now show the object permissions.

18. Files Enhancements:

  • Create and manage library memberships (internal or external users) from Files Home
  • Find files quicker via Recent Files
  • Preview Quip documents and sheets
  • Salesforce Files Sync scheduled for retirement on May 25, 2018
  • Use the ContentDocumentLink object data in the weekly data export file to see how Salesforce files are shared

19. Salesforce Connect Enhancements:

  • Pass more request information to OData and external data sources for processes using up to 10 defined custom HTTP headers.
  • (Beta) Using the Odata 4.0 adapter for Salesforce Connect, track changes to data stored outside of Salesforce, eliminating the need to build your own trigger logic based on changes to the external standard and custom objects.

20. Retrieve custom setting list views via the metadata API so they are deployable and packageable.

21. Track when internal users log into their communities via the new Employee Login to Community login type.

22. Authentication Provider endpoints must start with HTTP or HTTPS.

23. (Beta) Ability to trigger custom application logic when users logout.

24. (Beta) Create contactless external identity users. If your implementation does not require contact information (and the maintenance of this information) for external users, you may want contactless external users. You can upgrade the external identity user at a later point to a community license (at which point, you will need to create a contact for the user). Note: only available to users with the External Identity license, not with any other community license.

25 (Beta) Device Management: View and revoke device access, which logs the device out of Salesforce

26. (Salesforce Shield) Decode from the event log data the pages users were on and what they are doing in Lightning and the Salesforce mobile app with Event Monitoring.

27. (Health Check): Added “Number of expired certificates” and “Enabled HSTS for all Sites and Communicates with the default force.com subdomain that require a secure connection (HTTPS)”

28. Rename your My Domain when you want, without contacting Salesforce Support.

29. (Critical Update) Remove the instance name from My Domain URLs in sandboxes. Note: Activating this CU only in production will apply the change to new and refreshed sandboxes. For the change to take effect in an existing sandbox, you need to activate the CU in that sandbox.

30. Reset password links in forgot password emails stay active until a user confirms the password reset request.

31.Admin-initiated password reset links in emails expire after 24 hours.

32. Authentication provider endpoints must start with HTTP or HTTPS.

33. Use triggers to subscribe to logout events to run custom processes.

34. Enable debug mode for individual users, rather than for the whole org, to improve performance. Note: Users can be enabled via the new User Debug Mode screen in Setup.

Debug.jpg

35. Lightning Component Library is now Generally Available. Find it at salesforce.com/docs/component-library. This is cool. Your org’s Component Library is at https://<myDomain&gt;.lightning.force.com/componentReference/suite.app.

LightningComponentLibrary.JPG

36. Component CSS Class names updated to match the Block-Element-Modifier (BEM) notation SLDS now uses. If you have custom CSS in your Lightning components, you will need to update your selectors to use the single underscore. For example, “class slds-p-around—small” becomes “slds-p-around_small.”

37. New and changed lightning components

38. New and changed lightning interfaces

39. Lightning experience setting (set lightningStylesheets=”true” in the <apex:page> tag) in visualforce pages is now generally available

40. Determine user’s user interface theme in javascript using UITheme.getUITheme()

41. Use the Apex Switch statement to simplify code. Use it to test whether an expression matches one of several values and branch accordingly.

42. Get developer names for record types in Apex more easily, using Schema.DescribeSObjectResult.getRecordTypeInfosByDeveloperName() or Schema.RecordTypeInfo.getDeveloperName()

43. (Generally Available) Compile on Deploy. Apex code is now automatically recompiled before completing a metadata deploy, package install, or package upgrade. This is enabled automatically in Production and cannot be disabled

44. Max amount of Apex code your org can use has been doubled from 3 MB to 6 MB

45. New and changed Apex classes

46. New and changed API

47. Enable the new Modify Metadata permission to give the access the user needs without providing access to org data. Note: Some metadata requires Modify All permission as well. Without it, updates to those metadata types will fail.

48. Force.com IDE 2 Beta discontinued. Note: The classic version of Force.com IDE is still available.

49. Use Salesforce CLI to create environments for development and testing, sync source code, run tests, and support the application life cycle. Note: Installation of Salesforce CLI no longer also installs Git.

50. Search enhancements:

  • Use standard synonym groups to search. Note: This is enabled by default.
  • List email object is now searchable.

51. Debug logs size limits have increased to 5 MB. Orgs can store up to 250 MB of debug logs at a time.

52. Apex Testing Enhancements:

  • Automation testing to ensure flows and processes that are subscribed to a platform event are working as expected.
  • Use Test.getEventBus().deliver() to deliver test events in an Apex test.

53. Get email notification when trigger stops processing event messages. When a trigger subscribed to a platform event exceeds the maximum number of retries, it will stop processing new event messages, move to error state and an email is sent to the developer who last modified the trigger.

54. (Beta) Add flexibility with unlocked packages. Unlocked packages promote iterative and modular development, allowing you to add, update, and remove components in your package.

55. Filter field history reports by old and new values

56. Einstein Analytics Enhancements

57. Lightning for Gmail Enhancements

58. Microsoft Integration Enhancements

59. Salesforce CPQ and Billing Enhancements

60. Einstein Platform Services (Image Recognition and Natural Language Processing) Enhancements:

  • The free tier of service now includes 2,000 free predictions each calendar month, compared to 1,000 previously
  • Ability to reset your Einstein Platform Services private key
  • Use a refresh token instead of your private key to generate an access token.
  • Delete dataset API call returns a 200 status code signifying the dataset deletion response was successfully received, but the deletion has yet to be completed. You must explicitly delete models.
  • Use a new API endpoint to delete a model