The Summer 19 release is now live on all Salesforce instances and, as usual, we hosted a  release webinar shortly before this to introduce the new features to our customers and prospects, and other members of the Salesforce ecosystem - you can view the on-demand webinar here.

We've combed the 500+ pages of release notes and chosen our top six new features - note that any marked as beta may never be generally available.
 

1. Free (to send) Surveys

In Summer 19 surveys are now charged based on responses, so anyone with the appropriate Survey object permissions can create and send surveys. Each org gets 300 free responses, after which you can purchase an add-on response pack based on the number of responses you expect to receive.
 

2. Additional Skills in Skills-Based Routing

Additional skills are essentially nice-to-haves when routing cases. If no agent with all the defined skills, including additionals, becomes available within the designated time period, the additional skills become optional. The case is routed to the best-matched agent, even if they don't have some (or all) of the additional skills.
 

3. Conditional Instructions in Macros

Macros allow users to complete repetitive tasks with a single click, but up to now have run the same set of instructions regardless of the user executing the macro or the record it is being executed against. Summer 19 allows you to specify instructions that are only executed if the record matches specific criteria. This would allow, for example, a macro to be created to send an email when a case is created that contains different text depending on whether the case is Low, Medium or High priority.
 

4. Row Level Formulas BETA

While this is a beta feature and thus may never go GA, it's too good to leave out. To include a specific calculation on every row of a report, the solution has always been to add a custom formula field to the object being reported on. This has always felt suboptimal as it's polluting the records with data that is only applicable when executing a particular report, and once you have a number of these they start to get in the way of the real data, especially when administering the object. Row level formulas (assuming they go GA) allow you to create the formula to apply to each record where it belongs - on the report itself.
 

5. Max Debug Log Size Increased

A year ago, in the Summer 18 release, the maximum debug log size was increased to 5Mb, but this clearly still left a number of situations where the logs continued to be truncated. The maximum size has now been increased to 20Mb, which according to Salesforce will mean that 99.99% of logs will not be truncated. Hopefully you aren't part of the 0.01%!
 

6. Deploy Source Format Code to Non-Scratch Orgs

One for the developers here, as the force:source:[deploy/retrieve/delete] commands exit beta and become Generally Available. Previously to deploy etc to a non-source tracked org (anything other than a scratch org) you had to first convert to metadata API format and then deploy the converted source. One command instead of two turns into quite a time saver over the average developer's working year!

 

Keir Bowden is CTO of BrightGen, a Certified Technical Architect and multi-time Salesforce MVP - you can find him on twitter @bob_buzzard