The list of Summer ’19 features below apply to both Salesforce Lightning Experience and Classic.
There are additional Summer ’19 features available to Salesforce Classic Only, Lightning Experience only, Lightning Community Enhancements, Other Enhancements in the Summer ’19 Release Highlights post.
Note: These features are not listed in any specific order.
1.Lightning Flow Enhancements:
A. (Beta) Automated Home: This home page captures the last 30 day usage of peak paused flow interviews, total flow interviews without UI and total flow interviews with UI, gives you access to automation templates, information on automation app development, trailhead and the community and lastly, view graphs of total completed screen flows by name in the last 30 days, yesterday’s average completion time by flow name, total errors by flow name in the last 30 days and total started automations by process type in the last 30 days.
B. Processes cannot be saved if there are any warnings. You will be shown the error so you know what to fix.
C. You can now reference custom metadata types in a process formula! #CMDTAllTheThings! Watch the video
D. Use Apex-Defined Data Types to Manipulate Complex Internet Data in Flows Declaratively. There may be situations where you need a flow to manipulate complex data objects typically returned from calls to web services. The developer defines an Apex class to use as the pattern for conversion from web to flow and using the Apex-defined variables in flows, it will directly process JSON returned from web calls declaratively. Note: As of Summer ‘19, if a flow invokes Apex, the running user must have that Apex class assigned via to them via their profile or perm set.
E. New flow type selection screen allows you to specify up front what type of flow you are creating and based on the type, will only show you the flow components that are allowed for that selected flow type. You also have an easier way to access flow templates on the AppExchange.
F. Gap features from the old flow UI, Cloud Flow Designer, were addressed in the new flow Builder. We can now copy, paste, undo and also in Manager, see where a flow resource is used within the flow. Watch the video.
G. You can now use rich text in Flow Builder, including (beta) the ability to attach an image. Watch the video.
H. Search standard flow actions by category, type or search by keyword.
I. Increased Flow Usage-Based Enrollment for Standard Cloud User license or Salesforce CRM Contact User license to 50 additional flow interviews in Enterprise and 100 additional flow interviews in the Unlimited Edition.
J. (Lightning Scheduler) Use $Client.FormFactor global variable in your Decision flow element to enhance the user experience for each form factor.
K. When you do not set a default for the dependent picklist screen component, the field’s label shows by default, allowing you to use your existing customized picklists.
L. If you have any misconfigured values in your flow assignments, it will throw and error and Salesforce will not allow you to save and run the flow until you have resolved the flow issues.
M. (Critical Update) Evaluate the Criteria Based on the Original Record Values in a Process. This critical update will ensure that a process that has multiple criteria nodes and a record update will evaluate the original value of the field that was blank when it started the process. Note: If your process has the “Do you want to execute the actions only when specified changes are made to the record?” option selected or uses theISCHANGED(), enabling this critical update could possibly cause your process to behave differently.
N. Send Custom Notifications to the desktop or mobile device from a process. Watch the video. Watch the video.
O. (Critical Update) BR() will be used correctly in flows and processes. When you use BR() in flow or process, it will be translated into a line break, not _BR_ENCODED_.
P. (Critical Update) When enabled, this will require that the running flow user have access to Apex classes that are invoked by the flow via their profile or perm set.
Q. Cloud Flow Designer will be retired in Winter ’20.
R. Process Visualizer will be retired around June 2019.
2. Custom Metadata Type Enhancements:
A. You can now create up to 200 custom metadata types per org. This includes CMDTs created in your org and installed from managed and unmanaged packages.
B. Monitor the number of custom metadata type usage in your org on the System Overview page.
3. (Critical Update) Require TLS 1.2 for HTTPS Connections: Starting in October 25, 2019, all inbound or outbound connections to/from Salesforce must use TLS 1.2. Orgs created after this date will require TLS 1.2by default.
4. Manage access with session security-level-policies to manage certificates, manage connected apps, manage 2FA in API, manage 2FA authentication in UI and view event log files.
5. When switching between Classic and Lightning Experience, keep the record context. If the page does not exist, Salesforce will redirect you to the default landing page.
6. Use a Flow to Route Work Items Based on Skills, rather apex to create PendingServiceRouting and related SkillRequirement records.
7. (Beta) Live Controller <apex:liveController /> is a standard Visualforce controller that listens for updates to a single record using a standard controller or multiple records with a standard list controller and will re-render the page to display those updates in real time. This will be available on June 17, 2019. Review the release notes for more information.
8. When predefining email addresses, you can now make email address fields (To, Cc, or Bcc fields) read only so the email sender cannot make any changes.
9. Bounced emails now come from the header From address “Mail Delivery System” mailer-daemon@salesforce.comand the envelope address as empty.
10. Files can now be shared a maximum of 2,000 times with records, people or groups, an increase from 100.
11. Salesforce Connect Enhancements:
A. (Generally Available in Salesforce Connect using OData 4.0 Adapter) Track data changes to external objects using External Change Data Capture.
B. Picklists are now available for Salesforce Connect external objects created from Odata 2.0 and 4.0 adapters.
C. Reports that include a Salesforce Connect external object can evaluate up to 20K external records instead of 2K.
D. You can now use JWT or JWT Token Exchange as authentication protocols to build named credentials.
12. Data Protection and Privacy Enhancements:
A. Track customer’s consent with Authorization Form Objects
B. (Generally Available) Classify your data to support your data management policies by specifying the data owner (by user or public group), field usage (Active, DeprecateCandidate and Hidden) and sensitivity (Public, Internal, Confidential, Restricted and MissionCritical) of the data in any field.
C. Customize the data sensitivity values by adding a description to each data sensitivity level or manage the values. Go to Data Classification Settings in setup.
D. Salesforce is enabling Data Protection and Privacy in all orgs. You can disable the tracking preference.
13. (Admins with EinsteinBuilderFree license) Reference Einstein Predictions in formula fields by selecting AI Prediction and the field.
14. Total hard limit of custom objects in the org has been raised to 2,500 to allow you to install more custom objects from packages.
15. Delete Custom Fields Faster from Your Org. When you click on the Erase link for a custom field, it will mark the field for hard-delete and waits for Salesforce to move it into the hard delete processing. When there are 75% of the custom fields in a current object marked for deletion, a Purge button will appear that allows you to bypass the hard deletion queue and initiate the hard deletion process.
16. (Pilot) Add Flexibility to Your Permission Set Group with Muted Permissions. This allows you to disable specific permissions as needed.
17. Total number of character allowed in all index fields is now 100 from 50.
18. Email, phone and URL are now available for Big Objects.
19. Grant a connected app access to external (protected) resources with custom scopes.
20. If an org has My Domain and use the Login Discovery page, users can verify themselves with their SSO information, password or Lightning Login. With Lightning Login, users can use Salesforce Authenticator in place of a password.
21. Salesforce now offers password complexity option that requires that the password include at minimum 3 of the following: one number, one uppercase letter, one lowercase letter, and one special character (! ” # $ % & ‘ ( ) * + , – . / : ; < = > ? @ [ \ ] ^ _ ` { | } ~).
22. Customizable Forecasting will be retired as of Summer ’20. Users will not be able to access the Customizable Forecasting feature and its underlying data. Salesforce recommends migrating to Collaborative Forecasts.
23. The original territory management feature will be retired as of Summer ’20. Users will not be able to access the original territory management feature and its underlying data. Salesforce recommends migrating to Enterprise Territory Management.
24. Shield Platform Encryption Enhancements:
A. View statistics about your encrypted history and feed tracking data values by turning on Encrypt Field History and Feed Tracking Values.
B. Encryption is now available for Chat Body and Chat Supervisor Transcript Body fields using Platform Encryption.
C. You can now enable Shield Platform Encryption in scratch orgs.
D. (Generally Available) You can now perform exact, case- insensitive matching on deterministic encrypted fields.
E. Platform encrypt the activity subject field.
F. (Generally Available) Platform encrypt your email messages
25. Event Monitoring Enhancements:
A. (Beta) Real-Time Event Monitoring is the newest event monitoring feature. When you enable Real-Time Event Monitoring, you get (Beta) Enhanced Transaction Security to create transaction policies against the new Event objects. You can subscribe to several streaming events and store these events to up to 7 days.
B. Event Manager is your new place to view/manage your streaming and stored event monitoring events.
26. Aura component and Lightning web component (LWC) enhancements:
A. Use the Continuation class in Apex for a long running request to an external web services from an Aura component or Lightning web component. The asynch callout made with a continuation will not count towards the 10 synchronous Apex limit request lasting longer than 5 seconds. Note: A single Continuation object can contain a max of 3 callouts.
B. You can now add a LWC to a standalone Aura app using the naming convention: <namespace:camelCaseComponentName>.
C. You can add a LWC to a Visualforce page with 3 steps: (1) add LWC for Visualforce JavaScript library to your VF page using the <apex:includeLightning/> component, (2) create and reference a standalone Aura app that declares your component dependencies and (3) writing a JavaScript function that creates the component on the page.
D. (Beta) Add LWC to App using Lightning Out for use outside of Salesforce servers.
E. Save-time validations for Aura components have been improved and are surfaced during save time and not at runtime.
F. (Critical Update) Prevent creation of function expressions when using $A.createComponent() or $A.createComponents()in Aura components.
G. (Critical Update Postponed) The critical update to use without sharing for @AuraEnabled Apex Controllers with Implicit Sharinghas been postponed to Winter ’20.
H. Specify the form factor (Desktop, Phone or both) your Aura component or a LWC supports on a Lightning page by using the design:suppportedFormFactors tag set the component’s design file.
27. (Pilot) Enforce FLS in Apex: To ensure Apex proper security processing of field visibility to the current user based on their FLS access level, use the stripInaccesible method via the Security and SobjectAccessDecision classes. This will remove fields that are not accessible to the user.
28. Use Platform Cache with your scratch orgs by adding PLATFORMCACHE to your scratch org’s JSON configuration file.
29. Salesforce will stop supporting or providing updates to Force.com IDE after October 12, 2019 when it retires.
30. Salesforce has raised the maximum size of the debug log from 5MB to 20MB.
31. You can use Apex change event triggers to process change event messages. These triggers run asynchronously after the database transaction is completed. A change event trigger is an “after-insert” trigger. The change event name is StandardObjectNameChangeEvent, for standard supported objects and CustomObjectName__ChangeEvent, for custom objects.
32. Compose streams of change data capture notifications with custom channels. You can subscribe to the custom channel to receive notifications on the objects your app consumes.
33. Receive change event notifications on CampaignMember, CampaignMemberStatus and Contract objects.
34. Platform Event Enhancements:
A. You can now choose whether to publish an event message immediately or after the transaction is committed.
B. Process smaller event batches in Platform Event triggers and recover from exceptions. You can now set checkpoints for where the platform event trigger can resume execution.
C. (Beta) Subscribe to the /event/AsyncOperationEvent channel to be notified of any asynchronous platform event publish errors.
D. Use lightning/empApi module in Lightning web components as like Aura components for subscribing to event streaming channels.
35. New or Changed Lightning components
38. New or Changed Salesforce CLI
Jenwlee's Salesforce Blog 