Last Updated on April 15, 2022 by Rakesh Gupta

Currently, Winter’20 release is available under the pre-release program. On the 6th and 7th of September, Sandboxes will be upgraded, as a result, your organization will get the look and feel of Winter’20 release. In this release, you will find lots of new features, as well as, new enhancements related to Lightning Experience, Lightning Flow, Lightning Web Component, Apex, Communities, and APIs.

For example, features like, Automate Survey Invitations with Process Builder, See Who’s Working on a Prospect in a Sales Cadence, Use a Custom Caller ID with Lightning Dialer, Publish Einstein Analytics Dashboards and Lenses to Quip Slides and Einstein Lead Scoring: Control Which Leads to Score features are now available in Lightning Experience.

Also, check out these beta and pilot features:

Count Unique Values in Report Results (Beta): – See how many distinct values your report returns with a unique count. For example, opportunity reports often list multiple opportunities with the same account. Add a unique count to the Account Name column to see how many individual account values appear in the report. Unique counts appear as grand totals at the bottom of the report and as subtotals for each group.
To enable it, navigate to Setup (Gear Icon) | Setup | Feature Settings | Analytics | Report and Dashboard User Interface Settings and select Enable Unique Row Count Aggregate in Reports (Lightning Experience Only).
Give Chat Customers an Estimated Wait Time (Beta): – Your chat customers know their position in the queue but not how soon they’ll get help. The estimated wait time helps set expectations. You can display the Estimated Wait Time using the Chat API and Service SDK. You can display a queue position or an estimated wait time, but not both.
Make Sure Your AppExchange Packages are Ready for Lightning Experience (Beta): – Visit the AppExchange Packages tab in the Lightning Experience Configuration Converter to scan your installed package metadata and prepare your AppExchange packages for Lightning Experience. Find out which packages are ready for Lightning Experience. Get recommendations on updating, replacing, or verifying the rest. The AppExchange Packages tab replaces and enhances the AppExchange section in the Lightning Experience Readiness Check.
Log Hours on the go with Mobile Time Sheets (Beta): – If you are using Field Service Lightning, then you can now allow your mobile workers to log their hours on their mobile devices. They can also view their timesheet history and see the status of timesheets under review. Field service managers can then approve timesheets in Salesforce.
Filter Reports Using Field Comparisons with Field-To-Field Filters (Beta): -Filter a report by comparing the values of two different report fields. For example, see which cases were modified after the closing date by filtering on cases with a last modified date after the closed date.

To enable it, navigate to Setup (Gear Icon) | Setup | Feature Settings | Analytics | Report and Dashboard User Interface Settings and select Enable Field-to-Field Filtering in Reports (Lightning Experience Only).
Connect Your Bots to Third-Party NLPs (Pilot): – Bring your own natural language processor (NLP) such as such as IBM Watson’s Conversation Service (WCS), Microsoft’s Language Understanding Intelligence Service (LUIS), or Google Natural Language (NL) into Einstein Bots to create a multilanguage experience or to tie into your existing systems. Intents and utterance data are passed through Apex to the processor of your choice. A two-way system connects your NLP to Einstein via an Apex template, so customer inputs are sent from your Einstein bot to your provider. The bot can also receive intent and entity information from your third-party provider to use conversation routing.
Connect to Your Customers with WeChat (Pilot) and WhatsApp (Pilot): – Let customers communicate with support agents using WhatsApp and WeChat. Customers use WhatsApp and WeChat to send messages internationally and agents reply from the Service Console.

Be Lightning Ready by the Winter ’20 Release!

Salesforce is turning on Lightning Experience on a rolling basis in Winter ’20. Users still have access to Salesforce Classic after Lightning Experience is turned on. But Lightning Experience is where you want to be for driving business growth and improving productivity. To get ready, verify your org’s existing features and customizations in the new interface, and prepare your users with change management best practices. Salesforce is going to Turn On Lightning Experience (Critical Update, Enforced). This critical update was first made available in Spring ’19.

When it’s turned on, standard profile users and custom profile users with the Lightning Experience User permission enabled will see the Switch to Lightning Experience link in Salesforce Classic and be automatically switched into Lightning Experience on a regular basis.

Starting with Winter ’20, Lightning Experience is permanently enabled when it’s turned on, either by an admin at your company or via the Lightning Experience Critical Update. After Lightning Experience is turned on, you can’t disable it. All users still have access to Salesforce Classic and can switch between the two interfaces as needed.

Supported Browsers for Lightning Experience

Lightning Experience is supported by Apple® Safari® version 12.x+ on macOS. The most recent stable versions of Microsoft® Edge, Mozilla® Firefox®, and Google Chrome™ are also supported. You can continue to use IE11 to access Lightning Experience until December 31, 2020, If you opt into Extended Support for IE11. You can not access Lightning Experience via a mobile browser, but you can access in on iPad mobile browser.

Supported Browsers for Salesforce Classic

Salesforce Classic is supported with Microsoft® Internet Explorer® version 11, Apple® Safari® version 12.x on macOS. The most recent stable versions of Microsoft® Edge, Firefox®, and Google Chrome™ are also supported.

Below is the quick summary of Winter’20 release from user’s /customer’s

Customers/Administrators Point of view

1. Access the Recycle Bin in Lightning Experience: – You no longer have to switch to Salesforce Classic to access the Recycle Bin. You can now view, restore, and permanently delete the items in your Recycle Bin and the org Recycle Bin.

Access the Recycle Bin by selecting it in the App Launcher under All Items or personalizing your navigation bar.

2. Add Tabs and Accordion Components to Your Home Pages: – You can now use the Tabs and Accordion components on Home pages in Lightning Experience. You can create, update, and delete tabs, then change their order. Or, use the Accordion component to organize your components into collapsible sections.

For both Tabs and Accordion, you can configure the tabs or sections that your users see, name them whatever you like, and add components.

3. Change Your Sales Outreach Based on Call Results: – With Sales Cadence Branching, managers can create sales cadences that lead prospects through different outreach steps depending on the results of a call. For example, sales reps can follow one path when they speak to a prospect and another when they leave a voicemail.

To enable branched sales cadences, first turn on Call Results on the Log a Call page in Dialer Setup. Call results are disposition values such as “Left Voicemail” captured when you log a call. Then map your Call Outcome values in High Velocity Sales Setup

When sales managers build a sales cadence, they can add a call step (1) followed by a branch step (2). For each branching step, choose which Call Outcome value to look for, such as Meaningful Connect or Left Voicemail (3).

4. Add Products to Opportunities Faster in Lightning Experience: – Boost sales reps’ productivity when they add products to opportunities. With dependent picklists, sales teams can specify complete product information as they create opportunities. Reps no longer have to open each opportunity product separately to complete fields. If you already use-dependent picklists in the multiline editor for opportunity products, reps can now edit the fields. Previously, dependent picklist fields were read-only.

When you use dependent picklists in the multiline editor for opportunity products, options in the parent picklist (1) determine the available selections in the child picklist (2).

5. Control Whether to Capture Email Data with Einstein Activity Capture: – By default, Einstein Activity Capture adds email from sales reps’ connected accounts to the activity timeline of related Salesforce records. Now you can disable the email capture process to get more control over how Einstein Activity Capture works.

To disable it, navigate to Einstein Activity Capture configuration, then disable emails. Email capture is disabled for all users in the configuration.

6. Customize Opportunity Contact Roles for Better Tracking and Reporting: -Opportunity contact role customization options give you the flexibility to track and attribute revenue to roles, titles, and individuals. With custom fields and page layouts, validation rules, and Apex triggers, you can design an Opportunity Contact Role to match your specific sales and reporting processes. You can capture new data, such as titles and roles, to help your sales reps be more efficient in targeting the right contacts.

For example, a nonprofit organization can create a custom opportunity contact role called personal donor that allows it to track donations directly from individual donors. The organization can then identify its best donors and set up triggers to send thank you emails or other communications based on donation amounts or contact changes.

7. Find a Time That Works for Everyone in Availability View: – The new availability view helps reps easily scan to see who’s free to host a lunch or make a client pitch right in Lightning Experience. They no longer have to switch to Multi-User View in Salesforce Classic. Set up user lists so that reps can add multiple users to their calendar view without the headache of adding them separately.

Availability view doesn’t require any additional setup. To let sales reps see user lists in their calendars, from the Activities Settings setup, choose to Add user lists to calendar views in Lightning Experience.

8. Reuse Content Across Campaign Emails with Snippets (Pardot): – If you are using Pardot editions with the Pardot Lightning app, then you can now use Snippets which give your users the power of content reuse. When your company promotes a series of webinars or other recurring events, your marketers probably have to create many similar promotional emails. With Snippets, they can create a robust block of text, images, and links and pull it into email or email templates. Next time they make changes, they only have to update the snippet, and the email and email templates inherit the changes.

To let users create and manage snippets, add the Snippet tab and related lists to record pages. Add the Assignments related list to snippet records and the Snippet Assignments related list to campaigns.

9. Easily Deliver Knowledge Articles to Your Customers: – Let bots share your library of knowledge articles based on a customer’s search terms. Place this action on dialogs to deliver the top Lightning Knowledge articles to your customers by using clicks, not code.

For example, when a customer enters a search term, the bot delivers one, two, or three articles that solve the request best. You can choose which fields to show customers to deliver a customized experience.

10. Schedule Smarter Service Appointments with Extended Match Work Rules (Field Service Lightning): – If you are using Field Service Lightning, then going forward you can able to Set up extended match work rules to find the perfect service resource for every job.

For example, perhaps your mobile workers support specific ZIP codes. Use an extended match work rule to assign them appointments within their area.

11. More Users Can Remove Sales Cadence Targets: – Now the sales cadence target assignee, the target record owner, and the sales cadence owner can remove targets from a sales cadence. Previously, only users who added a target or users with the Modify All Data permission could remove targets. If you must allow broader access, you can assign groups permission to remove targets.

12. Maintain Access to Attached Files When You Migrate to Lightning Knowledge: – Choose the default visibility for migrated files when you use the Lightning Knowledge Migration Tool. Choose whether all users or only internal users can access files by default. Access to the article record still controls who can see the attachments in the Files related list in Lightning Knowledge. Previously, migrated files were accessible only internally, which meant that partner and customer users in communities could lose access.

During the file migration step, choose which users can access files by default. All users include your internal users and all customer, partner, and unauthenticated users viewing articles in your Communities and Sites. Choose the setting that applies to most of your files, and then adjust access to specific files after migration.

13. Set Targets for Lightning Smart Links: – Keep the right context and give your users the experience that they want with targets for smart links in Lightning Knowledge. Choose the Lightning target in addition to the traditional target. Options include the current app’s default behavior and a new browser tab, subtab, or workspace tab. Salesforce also updated the default behavior for smart links in Lightning Experience when the target isn’t set.

Click the smart link icon to use the Lightning target in your links. You can edit an existing link to set or change targets.

14. Let Your Agents Tackle the Right Cases First:– In a queue, priority is determined by how long the work item has been waiting – first in, first out. However, while a work item is pending in the queue, new work could come in that is more urgent. For example, transferred work, an item that has been waiting on someone’s response, or work that is about to reach a service agreement deadline. You can shift an item to a different queue, but within that queue, it’s behind older items. Also, some queues might have the same priority. Secondary Routing Priority solves this problem by moving a work item forward in a queue over older items and resolving conflicts across queues for items with the same routing configuration priority.

You can enable Secondary Routing Priority in Omni-Channel settings

15. Set File Sharing to Inherit Record Settings: – When attaching files to records, you can have the files inherit the sharing settings of those records. For instance, when a user can edit a record, you want them to be able to edit the files on that record, too. Now you can set the default sharing permissions on files that are attached to records. The preference lets files follow the sharing settings of the record.

For new orgs, this preference is auto-enabled, and files on records are set to Set by Record by default. For existing orgs, navigate to Setup (Gear Icon) | Setup | Feature Settings | Salesforce Files | General Settings and select Set file access to Set by Record for files attached to records.

16. Make Files on Records Visible to Customers in Communities: – Now you can decide which files customers can see on records that you share with customers in your communities. By default, files on records aren’t visible to customers in communities. The new Customer Access switch on a file’s sharing detail page lets you decide when customers can see the file.

To make a file on records visible to customers in communities navigate Files home in Salesforce, from the row-level action list or file preview, click Share. To see where the file is shared, in the sharing detail window, expand the Who Can Access section. The customer access option is visible in the sharing detail of any file shared with a record.

17. Accounts: Customize Account Teams to Better Support Team Selling: – Use customizable account teams to manage complex account relationships better in Salesforce. Collect more information by adding custom fields, buttons, and links to account team layouts. Use validation rules, Apex triggers, Process Builder, and workflow rules with account teams to help keep data clean and minimize manual data entry. You can now report on account teams, too.

18. Get Accurate Daylight Savings Time Values with DATEVALUE(): – The DATEVALUE() formula option provides more accurate daylight savings time values without workarounds. The option avoids an existing one-hour discrepancy when processing times between 11:00 PM and 1:00 AM.

To enable it, navigate to Setup (Gear Icon) | Setup | Company Settings | Company information | Locale Settings and select Improve DATEVALUE() accuracy for DST.

19. Secure Guest Users’ Record Access with a New Setting – Secure the access that unauthenticated guest users have to your org’s data with the Secure guest user record access setting. When enabled, guest users’ org-wide defaults are set to Private for all objects, and you can’t change this access level. You also can’t add guest users to groups or queues or manually share records with them. You can grant record access only with new guest user sharing rules.

To enable it, navigate to Setup (Gear Icon) | Setup | Security| Sharing Settings and select Secure guest user record access.

20. Create Guided Mortgage Application Flows with Mortgage Flow Templates (Financial Service Cloud): – Financial Services Cloud Mortgage comes with standard flows based on the U.S. Uniform Residential Loan Application released in February 2019. These standard flows are also templates that you can clone and customize to create your own guided UI flows for borrowers and loan officers.

To create a custom Mortgage flow, clone an existing standard flow. You can also select the Mortgage flow type and then select a standard flow as the template.

Build, test, and activate your custom Mortgage flow, and then distribute it to loan officers by making it a quick action on residential loan application pages. To make a custom borrower or assets and liabilities flow available to customers, configure it in Community Builder.

Additional enhancements worth noting!

1. Get Flexible with Email TO, CC, and BCC Fields: – You can send email from Salesforce to up to 150 recipients. Previously, you could have 100 email addresses in the TO field, and 25 addresses each in the CC and BCC fields. Now you can send to 150 email addresses across the three fields in any combination, up to 4,000 characters per field.

2. Get Clearer Character Limits on Questions: – Community feeds have had an unspoken limit of 255 characters on a Question field. When a question exceeded that limit, you found out only after you clicked Ask. Now the limit is clearly noted on the Question field, and we’re enforcing it by stopping you when you reach 255 characters.

3. Preview Files in the Chat Window: – Agents can click an attached file, such as an image, video, or PDF, to view it within the chat window. No need to take the time to download files or expose a desktop vulnerability.

4. Remove a File from a Record Without Deleting It Everywhere: – Want to remove a file from a record but not delete it from your Salesforce org? Now you can! Previously, a file owner could delete a file from Files home or a record using row-level actions. But this method also removed the file from all records and posts where it was attached. Now you can easily remove the file from a record without also removing it from other records, posts, or Files home.

On the record’s Files related list, choose Remove from Record from the row-level action menu. Enabled by default in all orgs.

5. Send Customers to a Specific Agent with Omni-Channel: – For faster resolutions, use Omni-Channel to send customers directly to the correct agent. Direct-to-Agent routing respects agent capacity and doesn’t send chat requests to an agent without capacity. The Direct-to-Agent button is available in the routing interface and as a field on the conversation transcript.

6. Know Who Sees What on Account and Opportunity Teams in Lightning Experience: – Teams can collaborate more effectively when they know who can view or edit an account or opportunity and related records. Now teams working in Lightning Experience can see other team members’ access to records.

Previously, team member access was viewable only in Salesforce Classic.

7. View Opportunities Owned by Your Team with One Click in Lightning Experience: – The new My team’s opportunities list view is based on role hierarchy. Sales managers can use it to easily see all the opportunities owned by their direct and indirect reports without creating a list view.

8. Sync Repeating Events Between Salesforce and Microsoft Accounts with Einstein Activity Capture: – You can now let sales reps sync repeating events, known as event series, between Lightning Experience or the Salesforce app and their connected Microsoft accounts. Previously, Einstein Activity Capture didn’t allow any users to sync event series.

9. Accordion and Related Record Components Supported for Case Record Page on Phone: – The Accordion and Related Record components are now available for the Case Record Page on the phone.

10. Layout Changes for Records Are Delayed After Save: – When you make layout changes to record pages on custom objects, the layout changes don’t appear immediately. The record page displays the updated layout about 15 minutes later when you reload the page. This change is a tradeoff to improve performance of record pages. Read more here

Developers Point of view

1. Make Your Lightning Apps Accessible on Phone, Desktop, or Both: – When you create or edit a Lightning app, you can configure which form factors it supports and can be viewed on. Creating an app just for your mobile app users? Designate that Lightning app for a phone.

You can give this feature a try in Lightning App Builder right away, but your changes won’t be visible to users until the new Salesforce mobile app is released the week of October 14, 2019 (if you are not part of Beta/Pilot program).

2. Customize Lightning Record Pages for the Phone Form Factor: – Lightning record pages are no longer limited to Lightning Experience on the desktop! If your org has opted into the new Salesforce mobile app, you can see the same record pages on desktop and the mobile app. Or, go one step further and address the needs of different users by assigning one custom record page for desktop users and another for mobile app users. Not sure which of your pages are assigned to which form factor? You can find that information on the Lightning Record Pages screen in the Object Manager.

Pages that you already have in your org support both form factors by default. With a few exceptions, the custom and standard components on those pages work seamlessly across desktop and mobile.

3. Set Record Page Component Visibility Rules Based on Device: – Give your mobile users exactly what they need on record pages by showing or hiding record page components based on the type of device they’re being viewed on.

For components on record pages, you can now show or hide a standard or custom component on a record page based on the device it’s viewed on.

4. Predict the Future Using Filters in Einstein Prediction Builder: – When you build a prediction, you no longer need a field that answers your prediction question. As long as the records on the object that you base your prediction on have the data, you can use filters instead.

Einstein Prediction Builder’s guided setup has a few new questions. For example, you specify whether you already have a field that can answer your prediction question.

If not, no need to create a custom field. Instead, use filters to set up your prediction. Suppose that you want to predict whether a deal will close. That’s a yes/no question, but the field that contains the data is a picklist. Select No Field, and use filters to provide examples of yes and no values. For example, select Stage Equals Closed Won to filter for examples of Yes.

Select Stage Equals Closed Lost to filter for examples of No.

5. Control Who Gets Read Access to Custom Metadata Types: – Use profiles and permission sets to assign read access to users for custom metadata types. As of Spring ’19, you can block all API read access to custom metadata types for users who don’t have Customize Application permission. Now you can grant API read access to specific metadata types for users and user profiles, even if they don’t have the Customize Application permission.

To grant a specific profile or permission set read access to a custom metadata type, go to the Custom Metadata Types permissions.

6. Lightning Flow and Process Builder Enhancements: – There are several enhancements in Lightning Flow and Lightning Process Builder, as follows:

A) Add Powerful and Performant Lightning Web Components to Your Flow Screens: – The powerful features and performance benefits of Lightning web components have come to flow screens. You can now integrate components that your developers have built or find them on AppExchange for use in your flow screens.

To make a Lightning web component available to a flow screen as a screen component, lightning__FlowScreen must be a target in the component’s targets tag, and the isExposed tag must be set to true. The component can use events in the new lightning/flowSupport module.

B) Start a Flow on a Schedule: – Do you have flows that are launched from Process Builder every time a record is saved, even though you need them to run only once a week? Do you wish you could schedule flows to run with the same ease as setting up a meeting?

Now you can schedule an autolaunched flow to start on a particular date and time and set the frequency to once, daily, or weekly. If you want that scheduled flow to run only for a set of records, you can specify an object and filter.

C) Make Your Flow Screens Dynamic with Conditional Visibility: – Save your users time by showing them only the fields they need when they need them. Add filter conditions and logic to a flow screen component’s properties to show or hide that component based on what a user enters or selects for flow resources like picklists or checkboxes.

For example, display an Address screen component only when your users select “Bill to a Different Address” checkbox screen component.

D) Use Rich Text in Text Templates: – Rich text has come to text templates in Flow Builder. You can always toggle back to plain text when using a text template in a Send Email action or in a custom action that expects plain text.

E) Control Users’ Ability to Run Individual Flows Using Profiles and Permission Sets: – Previously, users with the Run Flows, Manage Flows or Flow User permission could run all flows. Now you can control which flows users can run by restricting access to enabled profiles or permission sets.

F) Alert the Right People When a Flow Error Event Occurs: – To save time troubleshooting processes and flows that fail, subscribe to the new Flow Execution Error Event (FlowExecutionErrorEvent) platform event. Process Builder can subscribe to the event and then perform actions such as posting to Chatter or sending custom notifications. Previously, when a process or flow failed, you received only a flow error email.

From Process Builder, create a process that starts when a platform event message is received. Subscribe to the Flow Execution Error Event platform event.

G) Automate Sending Survey Invitations by Email: – Define the criteria for the Send Survey Invitations action type in Process Builder, and email survey invitations to leads, contacts, and users.

H) Automate Account Team Creation with Process Builder: – Configure a process action to add team members to an account. You can also configure a process to run when an account team member record is created or edited.

I) Help Your Users Search for Records in Flows: – Let users search for a record the same way they do everywhere else in Salesforce by adding a Lookup screen component.

7. Add Lightning Web Components as Custom Tabs: – Make a Lightning web component available as a custom tab in a Lightning Experience app and in the Salesforce app. Perform the following steps to add a custom tab for Lightning Web component:

Add the lightning__Tab target to the component’s configuration file. The .js-meta.xml configuration file defines the metadata values for the component, including the setting to allow usage in a custom tab.
```
< ?xml version="1.0" encoding="UTF-8"?>


lightning__Tab
```
Create a custom tab for this component.
To display the component in a custom tab:
- For a Lightning Experience app, add the component to the App Launcher.
- For the Salesforce mobile app, add the component to the Salesforce app navigation menu.

8. Lightning Components Can Access Apex Methods Only in the Same Package: – A Lightning component installed from a package can’t call an Apex method from an Apex class in another package, even if both packages are in the same namespace. You can’t use the @NamespaceAccessible Apex annotation in an Apex method referenced from a Lightning component.

This table shows the access differences for public @AuraEnabled Apex methods in a Lightning component in second-generation managed packages.

Annotation	Winter ’20 Access	Summer ’19 Access
`public` (no `@NamespaceAccessible`)	Same package only	Same namespace
`public` (with `@NamespaceAccessible`)	Error	Same namespace

9. Enforce Field-Level Security in Apex (Beta): – Apex has a new security feature for field-level data protection, which is accessed through the Security and SObjectAccessDecision classes. To ensure secure processing in Apex in the context of the current user’s read, create, or update operation, use the stripInaccessible method. Based on the field-level security of the current user, this method can be used to strip the fields from query results that the user can’t access. The method can also be used to remove inaccessible fields from sObjects before a DML operation to avoid exceptions and to sanitize sObjects that have been deserialized from an untrusted source.

For example, If the user doesn’t have permission to read the Phone field of a Contacts object, this example code removes the subquery field before reading the records. The DML operation completes without throwing an exception.

List accountsWithContacts =
	[SELECT Id, Name, Phone,
	    (SELECT Id, LastName, Phone FROM Account.Contacts)
	FROM Account];
// Strip fields that are not readable
   SObjectAccessDecision decision = Security.stripInaccessible(

	                                   AccessType.READABLE,
	                                   accountsWithContacts);
// Print stripped records
   for (Integer i = 0; i < accountsWithContacts.size(); i++) 
  {
      System.debug('Insecure record access: '+accountsWithContacts[i]);
      System.debug('Secure record access: '+decision.getRecords()[i]);
   }
// Print modified indexes
   System.debug('Records modified by stripInaccessible: '+decision.getModifiedIndexes());
// Print removed fields
   System.debug('Fields removed by stripInaccessible: '+decision.getRemovedFields());

10. Expand Apex Testing with the ApexSettings Metadata Type: – Use the new ApexSettings metadata type to augment Apex testing with aggregate total tracking, serial execution, and prevention of auto-number gaps. You can also use ApexSettings to suppress debug log details in unhandled exception emails. You can use the ApexSettings metadata type in the following ways.

To enable tracking of aggregate, instead of detailed, totals for Apex test coverage data, use the new enableAggregateCodeCoverageOnly field.
To enable serial execution of Apex tests, use the new enableDisableParallelApexTesting field.
To suppress Apex debug log details in unhandled exception emails, use the new enableDoNotEmailDebugLog field.
To prevent Apex test executions from incrementing auto-number fields for non-test records and creating gaps, use the newenableGaplessTestAutoNum field.

11. Enhanced External Services: Get Better Connections for a Better Tomorrow (Beta): – External Services which was released as a pilot feature in Spring ’19, is now beta. As part of the beta program, this feature is activated in all sandbox orgs. Use External Services to create and use connections to outside services. New registrations can use more-complex swagger2 schema, disregard Apex word, and character limitations, and receive ongoing benefits as they become available. If editing or registering new connections to an outside service, use Enhanced External Services now to get the upgraded benefits and save yourself time later.

12. Turn On Platform Encryption Settings Programmatically Through Metadata API: – When you set up your orgs programmatically, quickly enable Shield Platform Encryption settings with new Metadata API Boolean fields. No more switching between the Advanced Settings page in Setup and your developer environment. Use the new Boolean fields on the new EncryptionKeySettings and PlatformEncryptionSettings to:

Enable the Cache-Only Key Service
Opt out of key derivation processes on customer-supplied keys
Enable replay detection on cache-only key callouts
Enable encryption on custom fields in installed managed packages
Require a second form of authentication for key management tasks
Require the Manage Encryption Keys permission for encryption policy tasks
Enable the deterministic encryption scheme
Enable the background encryption process for field history and feed tracking values
Enable Shield Platform Encryption for Change Data Capture events

For more information about these settings and what happens when they’re set to true, read about the PlatformEncryptionSettings and EncryptionKeySettings metadata types in the Salesforce Metadata API Developer Guide.

13. Compute Code Coverage for Unlocked Packages: – Computing code coverage helps ensure that you’ve tested your Apex code. A code coverage minimum isn’t enforced when you create unlocked packages, but you can use the CalculateCodeCoverage field in the Package2VersionCreateRequest object or the code coverage CLI parameter when you create a package version.

14. Communicate Across Salesforce UI Technologies with Lightning Message Service (Developer Preview): – Use the Lightning Message Service API to communicate across the DOM, between Aura components, Visualforce pages, and Lightning web components. If you’re switching from Salesforce Classic to Lightning Experience, you can now build Lightning web components that can communicate with existing Visualforce pages or Aura components. Read more here

Additional enhancements worth noting!

1. Opt-Out of ISV Hammer Tests: – If you do not wish to participate in ISV Hammer tests, you can ensure that ISV partners respect your decision. Simply opt-out using the ISV Hammer Opt Out page in Setup.

Form the Quick Find menu to select ISV Hammer Opt-Out and turn off the ISV Hammer Tests setting.

2. Callouts Are Excluded from Long-Running Request Limit: – Every org has a limit on the number of concurrent long-running Apex requests. This limit counts all requests that run for more than 5 seconds (total execution time). However, HTTP callout processing time is no longer included when calculating the 5-second limit. Salesforce pause the timer for the callout and resume it when the callout completes.

3. Install Even More Custom Objects in Your Org: – Salesforce did it again: Salesforce raised the total hard limit for custom objects in an org to 3,000 (up from 2,500 in the previous release) so that you can install more custom objects from packages.

Salesforce mobile app Enhancements

The highly anticipated new Salesforce mobile app arrives the week of October 14, 2019. Admins have more power than ever to create mobile experiences that delight users and ease their workload across devices with components optimized for mobile. Salesforce users get a unified experience working across desktop and mobile, no matter how or where they work.

Your users have several options for accessing Salesforce on mobile devices that meet minimum platform requirements.

Users can run Salesforce on mobile devices that meet these mobile platform requirements.

Operating System and Version Requirements	Mobile Browser Requirements*
Android 6.0 or later	Google Chrome on Android
iOS 12.0 or later	Apple Safari on iOS

1. Transition Seamlessly to the New Mobile App with Familiar Navigation Items – When users first log in to the new Salesforce mobile app, they see the same items they used in the previous Salesforce mobile app. Salesforce has moved them to an app called Mobile Only. The Mobile Only app ensures that users’ workflows aren’t disrupted when switching to the new mobile app.

Users can keep using the Mobile Only app, or they can switch to a Lightning app using the App Launcher. If they need access to the previous navigation items again, they can switch back to Mobile Only via the App Launcher.

2. Launch into Lightning Experience Apps with the Mobile App Launcher: – The App Launcher has landed on mobile. You can switch between all your favorite Lightning apps, just like in Lightning Experience desktop.

Previously, to use all the cool features that are available in Lightning apps, you needed to be on a desktop computer. Now you can access Lightning apps from anywhere.

3. Do More on Record Pages with New Styling and Components: – Improvements to record pages in Lightning Experience desktop have made it to mobile. Refreshed styling and improved functionality make it easier to find data and take the needed actions.

The back button easier to see (1). Actions are now at the top of the screen (2), followed by the record details. Tabs are stacked vertically (3), so you can drill down with a quick tap. Navigation items are at the bottom, as they are throughout the app. And the Path component is now supported in mobile for the same objects that support it on desktop. Use it to give reps the guidance they need to close deals on the go.

4. Give Your Users Custom Record Pages on Their Phones: – Custom Lightning record pages are no longer restricted to the desktop. Now you can create record pages tailored to the needs of your mobile users that they see only when viewing the page on a phone.

5. View More Fields in the Record Highlights Panel: – Your reps have access at the top of their record pages to more of the information that they use most. Salesforce has increased the number of compact layout fields that display in the highlights area from 4 to 10.

6. List and Related List Components Are Optimized for the New Salesforce Mobile App: – Salesforce has updated the List View, Related List – Single, Related Lists, and Related List Quick Links components to support mobile navigation and the new Salesforce mobile app. When you place the List View component on a record page, a View More button loads more records in batches, so you can easily get more records or scroll to the information you want.

The Related Lists component groups all your related lists in one section and no longer includes News and Twitter. The Related Lists component also uses a View More button for efficient navigation.

7. Download and Share Salesforce Files for Access on the Go: – Now you can download and share Salesforce files from the Mobile Publisher community, giving users access to files anytime and anywhere

What are your favorite Winter’20 release note gems?

–> You can download release notes in HTML format!, for PDF file.