7 Highlights from the Salesforce Winter’19 Release for Developers

The Salesforce Winter’19 release once again focuses on delivering more connected customer experiences to drive lasting customer relationships.

A lot of the focus in this release is on providing more flexibility to the developers to make your job easier.

The team at Techforce Services has put together a short note on the key updates in this release. Please share what feature you liked or would like to understand better.

  1. Enable CDN to Load Lightning Experience Faster
  2. Test Branding Imagery in Sandboxes
  3. Mark Apex Methods as Cacheable
  4. Custom Metadata Types in Advanced Formula Fields
  5. Salesforce Extensions for VS Code v44
  6. Dev Hub in Developer Edition and Trial Orgs
  7. Scratch Org With More Configuration Settings

LIGHTNING

Enable CDN to Load Lightning Experience Faster

You now have an option to enable Content Delivery Network (CDN) that generally speeds up page load time.

It improves the static content load time by storing cached versions in various geographic locations. CDN can be enabled in the session settings.

Important: CDN is disabled by default for existing orgs and enabled by default for new orgs.

Test Branding Imagery in Sandboxes

Winter’19 release now supports testing of your branding imagery in full sandboxes which were not possible before.

To achieve this you can select the Content Body in the template while creating full copy sandbox.

This is an exciting feature for those who are using communities, as you can test the look and feel and branding images before rolling them out.

APEX

Mark Apex Methods as Cacheable

In order to cache data returned from Apex method, you had to call setStorable() in the JavaScriptcode for every action to Apex method.

After this release by just marking Apex method as ‘cacheable’, it will serve the same purpose of quickly showing cached data from client-side storage instead of waiting for server trip.

As a result it improves the performance of Lightning components.

Sample code:

@AuraEnabled(cacheable=true)
public static Account getAccount(Id accountId) {
// your code here
}

Custom Metadata Types in Advanced Formula Fields

This new feature saves Admins from having to modify multiple formula fields that use certain parameter for calculations.

Now, they can save the parameter in a custom metadata and refer the parameter in the advance formula fields.

VISUAL STUDIO CODE

Salesforce Extensions for VS Code v44

Salesforce extension for VS code which was available only for scratch orgs, is now open for development against any org.

This enables developers to connect, develop and deploy source code from VS Code even if they don’t deal with scratch orgs.

However, this is in Beta phase now.

Thanks to ‘Apex Replay Debugger’ developers do not need to scan through heaps of logs manually. The replay debugger gives live debugging experience using debug log which consists of all the actions for a given transaction. The latest enhancement is to include checkpoints that give additional information when compared to the regular debug logs.

You can now explore all the Apex tests within VS code. The left side bar gives a glimpse of all the methods in each of your test classes without having to open the test class and scroll through entire class. When your test class fails, you can jump right to the line where it failed. And when the test class passes, you can jump to the test methods.

Source

SALESFORCE DX

Dev Hub in Developer Edition and Trial Orgs

Now you can create up to 6 scratch orgs with maximum of 3 active scratch orgs in your Developer edition or trial orgs with Dev Hub.

DevHub wasn’t available in the Developer orgs before and you had to use 30 days trial version to be able to use Dev Hub, which no longer an issue.

It is pretty simple to enable Dev Hub in your Dev Org. All you have to do is:

  1. Log in as System Administrator to org that you want to use as your Dev Hub.
  2. From Setup, enter Dev Hub in the Quick Find box and select Dev Hub.
  3. In the Dev Hub section, click Enable.

You can also enable Dev Hub in your Production Orgs it provides higher daily limits for scratch orgs and package versions, which in turn is useful for continuous integration jobs setup.

Scratch Org With More Configuration Settings

Now it’s possible to spin your scratch orgs with specific org settings.

You can configure your scratch org with any Metadata API. These settings provide you with more granular control over the settings, for example you can provide the values for the fields instead of just enabling and disabling it.

Ex: This scratch org definition is configured using org preferences:

{
“orgName”: “Acme”,
“edition”: “Enterprise”,
“features”: [“Communities”, “ServiceCloud”, “Chatbot”],
“orgPreferences” : {
“enabled”: [“NetworksEnabled”, “S1DesktopEnabled”, “S1EncryptedStoragePref2”]
}
}
Here’s how the same scratch org definition looks after converting to scratch org settings:
{
“orgName”: “Acme”,
“edition”: “Enterprise”,
“features”: [“Communities”, “ServiceCloud”, “Chatbot”],
“settings”: {
“orgPreferenceSettings”: {
“networksEnabled”: true,
“s1DesktopEnabled”: true,
“s1EncryptedStoragePref2”: false
},
“omniChannelSettings”: {
“enableOmniChannel”: true
},
“caseSettings”: {
“systemUserEmail”: “support@acme.com
}
}
}