Apex · Lightning · Salesforce

Highlights of Winter’19 Release Notes: Part II

“Aloha Trailblazers Ohana” We bring you back the Part II highlights of Winter’19 Release!! Let’s learn new and blaze our trail!!

Don’t miss out to read the part I highlights to stay updated about the new features!! Part I Highlights

Lightning Communities: Content Management, Flows for Guest Users, and Filtered Search Results

1. Upgrade to Latest Community Theme:

With every release, salesforce adds enhanced and improvised features. Likewise, they have updated the features of lightning communities. With winter’19 release a new layout template is made available for the communities.

Theme Communities

2. Inbuilt Content Management(beta):

A new tile is added in the community workspaces, which allows you to create content within the community and also lets you integrate your Salesforce CRM data, which can be displayed as information. All the data is managed in one place and you can also adjust the layout according to your needs.

ContentManagement Communities

Content Management Communities

3. Export themes from the community builder:

Now, you can export themes which you have created from the developer page on the community builder settings. You can put your theme on APP Exchange or share it with your community via a file. This feature is available to all Communities admins.

export theme

Lightning Components in Community Builder:

1. Help Guest Users with Flows:

Guest users can now access flows through your public community pages. With flows, you can guide your users through the registration process while learning more about them, allowing you to provide the best community experience possible.

2. Block Deletion of Threads in Communities:

With Winter’19 release the orgs created after the release, deletion of feed’s which are nested is blocked.

For e.g: If a question on your community feed has an answer and related replies, that feed cannot be deleted. This is recommended to avoid deletion of the main feed and (solutions) replies to the feed.

3. List view of topics in community content: 

You can now view your community’s topics in one place, and sort them by name, description, or type. You can now enable up to 10 topics and filter the list according to your need. You can also modify/delete/edit the list.

Content topics list view

4. Display Related Lists with more precision:

You can use the Related Records List component, which displays all related lists of all kinds, the new components provide a more targeted experience. For instance, you can show just the related open cases for a particular account. In addition, both components have a new layout option for narrower displays, such as sidebars and mobile, for better usability.

5. Show Your Salesforce IoT Data Anywhere in Salesforce with IoT Insights:

Add the Salesforce IoT Insights Community Builder component to show Salesforce IoT data to your Lightning community members.

This makes your Salesforce IoT data available to your users throughout Salesforce, giving them more information to serve customers. The IoT Insights Lightning standard component enhances your CRM data by showing Salesforce IoT information alongside it. You can include the component on Salesforce Lightning record pages, such as cases, work orders, and assets.


6. Allow Field Service Dispatching from Lightning Communities:

The new FSL Community Dispatcher permission set provides all the permissions a community dispatcher needs to use the dispatcher console, view global actions and their related objects, and schedule, optimize, and dispatch service appointments.

To use the dispatcher console in a community, users need:

  • Customer Community Plus or Partner Community license
  • FSL Dispatcher permission set license
7. New Global Actions for Communities:

Salesforce has added two new case global actions for specific user type.  When you configure your Contact Support Form component, you now see separate case global actions: one for authenticated users and one for guest users.

8. See Field Dependencies While Editing a Record Details Page:

You can now view and update all dependent and controlling fields when editing a picklist or checkbox on a Record Details page.

For that, you should have a dependent picklist field in your object.

Field Dependencies

Community Engagement: Recognition Badges

1. Display Recognition Badges on User Profiles:

These badges are available on the profile component of your community. This displays the last three badges earned by the user and a button to award a new badge.

You can include this badge component in a user’s profile page, to show the badges earned.

2. Award Recognition Badges with the New Give Badge Button:  

Giving your fellow users the recognition badges they deserve is easy with the Give Badge action. Add Give Badge as a button, and give any user a badge directly from a user profile.

From a user profile, select Give Badge and that user’s name is automatically included in the To field. You can also give badges with the Give button on the Recognition Badges card. Add the card to your user profiles with the User Profile component or the Recognition Badges component.


Give badge

Files in Lightning Communities: Editable File Detail Pages, and Custom Fields on File Uploads

1. Make Changes to Fields whenever necessary:

You can now edit file details in Communities for all fields, including file name, description, and custom fields so you can keep your file information accurate and up to date.


2. Populate Custom Fields When Uploading Files:  

Users can populate required custom fields and see validation rule error messages when files are uploaded to the community. This feature is available on files uploaded from Files home, from the Files or Notes and Attachments related lists, and the Lightning file upload component.

When uploading a file, users are alerted to required fields or validation errors that must be fixed before the file can be saved.


Salesforce Surveys: More Control to Gather the Data You Need

1. Gather Specialized data with new question types:

To gather data in an effective way, with the Winter’19 release three new question types are being introduced in salesforce surveys – CSAT, Sliders, and Picklists.

CSAT lets you collect Customer Satisfaction data from a list of options. Sliders, on the other hand, let’s your participants select a value on a sliding measure scale. Picklists are nothing but a pre-defined list of options for participants.

2. Add Multiple Questions to your surveys:

Users with Survey creator license can now add multiple questions to the surveys, to help the participants navigate and move through survey easily.

View Status and Responses on Survey Invitations:


3. No Authentication Required for contacts to take surveys:

In order for a participant to take a survey, they no longer need to log in from their salesforce account, if they are associated with contact records in your Org.

4. Gather financial data from financial services cloud:

With winter’19 release surveys are made available to the Financial Service cloud. A user can create surveys in the financial service cloud, in order to gather insights from banking and financial service customers.

5. Pause and Resume a survey:

Participants can now pause a survey and come back to finish it later without losing their progress. Surveys which require authentication can only be paused. Users are required to log-in with salesforce authentication credentials in order to pause a survey.

APEX: What’s new in Winter’19!!

1. Fire platform events from Batch Apex:

With Winter’19 release Batch classes can fire platform Events. Event records provide more granular tracking of errors than the Apex Jobs UI because they include the record IDs being processed, exception type, exception message, and stack trace. You can also incorporate custom handling and retry logic for failures. Clients listening on an event can tell how often it failed, which records were in scope at the time of failure, and other exception details. Events are also fired for Salesforce Platform internal errors and other “uncatchable” Apex exceptions like LimitExceptions that are caused by reaching governor limits.

To fire a platform event, a batch Apex class declaration must implement the Database.RaisesPlatformEvents interface.




2. Use Inherited Sharing keyword to secure your Apex Code:

You can now specify the inherited sharing keyword on an Apex class, which allows the class to run in the sharing mode of the class that called it. Using inherited sharing enables you to pass security review and ensure that your privileged Apex code is not used in unexpected or insecure ways. An Apex class with inherited sharing runs as with sharing when used as a Visualforce page controller, Apex REST service, or an entry point to an Apex transaction.

This example declares an Apex class with inherited sharing and a Visualforce invocation of that Apex code. Because of the inherited sharing declaration, only contacts for which the running user has shared access are displayed. If the declaration is omitted, even contacts that the user has no rights to view are displayed due to the insecure default behavior of omitting the declaration.



Output with Inherited sharing Keyword:

sharing output

Without Inherited sharing keyword this displays the list of all contacts.

3. Streamline API Calls to Your Org:

You can now access API features without configuring remote site settings by using the System.Url.getOrgDomainUrl() method.You can now interact with those objects using Apex code, building endpoints with the System.Url.getOrgDomainUrl() method.

You can also use the updated System.UserInfo.getSessionId() method to retrieve session IDs, even when your code runs asynchronously.

Share Extensible Functionality with the Callable Interface:

Instead of implementing the Process.Plugin interface for use cases it wasn’t designed to support, you can now implement System.Callable. Simply invoke Callable to make a common point of agreement between pieces of code from different parties. This helps developers to build upon one another’s solutions.

To implement the Callable interface, you need to write only one method: call(String action, Map<String, Object> args).

The Callable interface allows integrations in which code from different classes or packages can use common base types.

4. Changed Apex Classes:

With winter’19 release the apex classes have changed and now has new constants.

Schema.DescribeFieldResult Class

New method: isAiPredictionField() 

Returns a Boolean indicating whether the field is enabled to display Einstein prediction data.

Schema.DescribeSObjectResult Class

New Method : getRecordTypeInfosByDeveloperName()

Returns a map that matches developer names to their associated record type.

System.Crypto Class
New Methods: 
verify(String algorithmName, Blob data, Blob signature, Blob publicKey)

Returns a Boolean verifying the digital signature for encrypted data, using the specified algorithm and the supplied public key.

verify(String algorithmName, Blob data, Blob signature, String certDevName)

Returns Boolean verifying digital signatures for data, using the specified algorithm and the public key associated with the certDevName.


Returns a Boolean verifying the HMAC signature for data using the specified algorithm, input data, privateKey, and the mac.

Changed Apex Enum

These enumerations were updated in this release.

Auth.Auth.VerificationMethodEnum Enum

Contains the different ways users can identify themselves when logging in. Can be used to implement mobile-friendly passwordless login pages, and to self-register (and deregister) verification methods.

This enum has a new value, Password. Identity can be verified by password.

Metadata.PlatformActionListContextEnum Enum

Describes the different contexts of action lists.This enum has a new value, ActionDefinition. This value is reserved for future use.

New Apex Interfaces:

Auth.ConfigurableSelfRegHandler Interface

Create a class that implements Auth.ConfigurableSelfRegHandler to register users with their email address or phone number instead of a username and password. When you set up your community’s self-registration with the Configurable Self-Reg Page, Salesforce generates a default AutocreatedConfigSelfReg Apex class. Modify the class to extend the functionality, for example, to change how users are created.

createUser(accountId, profileId, registrationAttributes, password)

Create a community member from the information that the visitor provided on your community’s self-registration page.

Auth.LoginDiscoveryHandler Interface

Create a class that implements Auth.LoginDiscoveryHandler to log in users based on other verification methods than username and password. Users can identify themselves with their email, phone number, or another identifier like a Federation ID or device identifier. When you set up your community’s login page with Login Discovery Page, Salesforce generates a defaultAutocreatedDiscLoginHandler. You can modify the class, for example, to support single sign-on (SSO).

login(identifier, startUrl, requestAttributes)

Log in the external user given the specified identifier, such as email or phone number. If successful, redirect the user to the community page specified by the start URL.

System.Callable Interface

Enables developers to use a common interface to build loosely coupled integrations between Apex classes or triggers, even for code in separate packages. Agreeing upon a common interface enables developers from different companies or different departments to build upon one another’s solutions. Implement this interface to enable the broader community, which might have different solutions than the ones you had in mind, to extend your code’s functionality.

call(action, args)

Provides functionality that other classes or packages can utilize and build upon.

Visualforce: Field Sets in Lighting Experience and New Access Metrics

1. Create and Edit fieldsets(Lightning):

Now you can create and edit fieldsets in lightning experience.

When a fieldset is added to a Visualforce page, developers can loop over its fields and render them. If the page is added to a managed package, administrators can add, remove, or reorder fields in a field set to modify the fields presented on the Visualforce page without modifying any code. The same Visualforce page can present different sets of information.

field sets

2. New Access Metrics Fields:

Use the new ProfileId and LogDate access metrics fields to prioritize which Visualforce pages to migrate to Lightning Experience.

The ProfileId field shows the Salesforce profile ID of the user who viewed the Visualforce page. The LogDate field shows the date that the user accessed the page. This field provides more insight into page usage than the MetricsDate field, which represents the date the metrics are collected.

3. Use Image Proxy URL to display third party images securely:

You can now protect your users from unauthorized requests by using the IMAGEPROXYURL function to securely fetch images outside your org’s server.

To securely retrieve an external image, include the IMAGEPROXYURL function on the src attribute of a tag or the valueattribute of an object.

<img src={!IMAGEPROXYURL(“https://domain&#8221;)}/>

<apex:image value=”{!IMAGEPROXYURL(“domain”)}”/>

4. Improve Security with Iframes:

You can now isolate HTML static resources on a separate domain using iframes. Using a separate domain to embed information from untrusted sources protects your Visualforce content.

To reference a static HTML file on a separate domain, use $IFrameResource.<resource_name> as a merge field, where resource_name is the name you specified when you uploaded the static resource.

5. URL parameters are no more case sensitive:

The protected URL parameters used in Visualforce pages—retURL, startURL, cancelURL, and saveURL—are no longer case-sensitive. For e.g: If you change the parameter value from retURL to returl, the system now recognizes it as a protected parameter.

Search: Relevant Results in Real Time and More Ways to Filter Results and Search

1. Get More Relevant Search Results Without the Wait: 

Search results now instantly prioritize the objects you interact with. That means new users, or users changing roles, don’t have to build up interaction history to see what’s most important when they search. Previously, it took some time to accrue interactions with objects and prioritize those objects in search results. Now any object your users open, create, or update gets an instant boost when using global search.

   2. Filter Search Results by Number Range:
  1. When the numbers matter, use filters to frame your search results. Zero in on opportunities that fall within a certain amount or probability range.
  2. For example, use number range filters to create a list of hot opportunities to follow up on. On the search results page, click Opportunities in the sidebar to see the available filters. Enter your target range, and click the magnifying glass.

From Setup, in the Object Manager, go to Search Layouts for each object. Add the fields that users want to filter to the Search Results layout. You can’t filter encrypted fields. 

Screenshot (144)

3. Recover Your Unsaved Text After Getting Timed Out: 

Sometimes your Lightning Experience session is interrupted, whether you’ve been inactive too long or you lost your connection. You used to see the same timeout message, regardless of how your session ended. Now the message that pops up is specific to your scenario and tells you how to recover the unsaved text.

If your session is interrupted, return to the page to copy unsaved text, like a Chatter post, so you don’t lose it during a new session.

Screenshot (145)

4. Field History Tracking Data Deleted After 18 Months: 
  1. Salesforce guarantees to retain your field history data for up to 18 months.
  2. Starting with the Winter ’19 release, we no longer retain field history beyond 18 months. To retain field history longer, you can purchase the Field Audit Trail add-on.
  3. This policy applies to all orgs created after June 2011 who have not purchased the Field Audit Trail add-on.
  4. To guarantee that you have access to your field history data, purchase the Field Audit Trail add-on. Field Audit Trail lets you define a policy to retain archived field history data up to 10 years from the time the data was archived.
  5. Use the queryAll() API to retrieve deleted field history during the grace period and create your own backup. You can’t use the getDelete() API to retrieve data that Salesforce deletes following the 18-month limit.

Productivity Features:

1. Email Experience: Attachments in List Emails and Actions, Bounce Notifications, Email Tracking, and Quick Text.
a. Bounce Back from Email Bounces:
  1. Sales reps need to know when their emails to contacts, leads, and person accounts don’t go through. Without a warning, they’re waiting for a response that’ll never come. Now reps know which lead, contact, or person account has a bad email address, and they know which specific email wasn’t delivered.
  2. Any user can see a bounce warning. If the user has update rights to the record, the user can update the contact’s email address to remove the bounce warning.
  3. A bounce warning appears next to the email address in the lead, contact, and person account record.
  4. To activate Bounce Management, from Setup, click Email, then click Deliverability. Select Activate bounce management. To display bounce information, from Setup, enter Enhanced Email in the Quick Find box, and then select Enhanced Email. Click Enable.

Screenshot (146)

   b. Quickly See Whether Customers Open Email from Your Company: 
      1. Now we can glance at the activity timeline to see if and when customers open the email that reps send through Salesforce.
      2. Previously, to see if and when customers opened an email from your company, reps ran the HTML Email Status report. But now, tracking information is visible in the activity timeline.
    1. Screenshot (147)
    2. 3.  If you want, add the First Opened and Last Opened fields to your email page layouts to see the information there, too.

Screenshot (148)

  c. Use Attachments After Inserting Salesforce Classic Email Templates:

Your sales reps know that they can insert a Salesforce Classic email template into a Lightning Experience email. Now they can use existing content and add attachments to the email too. For text, custom HTML, and letterhead email templates, reps can add attachments from Files.Screenshot (149)

Screenshot (150)

      1. When a Salesforce Classic Visualforce email template is inserted into a Lightning Experience email, you can’t add an attachment.
      2. To change the attachments that are part of a Salesforce Classic email template, go to Classic Email Templates in Setup.
    1.  Screenshot (151)
  1. Kanban: Recently Viewed Availability, Search Kanban View

Explore the power of the Kanban View from Recently Viewed lists. No need to switch to another view to find records. Search is now available on the Kanban View.

a. Get the Kanban View for Recently Viewed Lists Users can switch to the Kanban view from the Recently Viewed list view of almost any object.
    1. Select the Recently Viewed list view (1), then select Kanban from the Display As menu (2).                Screenshot (152)
b.  Search for Records in the Kanban View
    1. Users can hone in on the records they need faster by searching the selected list view from within the Kanban view.
    2. Enter a search term in the search box to see matching records.Screenshot (153)

Analytics: Reports and Dashboards

Reports: Enhanced Run Page Improvements (Beta), Drill into Your Data, Edit Joined Reports with the Lightning Experience Report Builder (Beta)

The second beta release of the enhanced run page report is available to all users. It brings many powerful features to report readers, such as grouping report data and toggling the visibility of detail rows. Drill into your data to get more information. As part of the Lightning joined reports beta, edit joined reports with the Lightning Experience report builder.

  1. Edit Joined Reports with Lightning Report Builder (Beta)
  • Enhance your joined report workflow by editing joined reports with the Lightning report builder and with more run page functionality including filtering and sorting.
  • This release contains a beta version of Lightning joined reports, which means it’s a high-quality feature with known limitations. Lightning joined reports isn’t generally available unless or until Salesforce announces its general availability in documentation or in press releases or public statements
  • To view joined reports in Lightning Experience, you need the Run Reports user permission.
  • To create or edit joined reports, you need one of these permissions: Create and Customize Reports, Report Builder, or Report Builder (Lightning Experience).
  • Work with joined reports in Lightning Experience’s modern interface and take advantage of Lightning Experience’s productivity-improving features like report run page filtering. Edit joined filters, groups (including cross-block groups), and columns with the Lightning report builder.
  • If necessary, turn on the Lightning joined reports beta. From Setup, enter Reports in the Quick Find box, then select Reports and Dashboards Settings. Select Enable Lightning Joined Reports (Beta), and then click Save. To edit a joined report with the Lightning report builder, click Edit (Beta).

Screenshot (155) - Copy

    2. Features Not Available

These features aren’t available in the Lightning Experience report builder, but they are available in the embedded Salesforce Classic report builder. To open the Salesforce Classic report builder in Lightning Experience, click either New Report (Salesforce Classic) or Edit (Salesforce Classic).

Editing and building feature gaps and limitations include:

  • Creating joined reports
  • Adding or removing blocks and report types
  • Adding and editing custom summary formulas and cross-block custom summary formulas

Running and reading feature gaps and limitations include:

  • Subscriptions
  • Export
  • Chatter feeds
   3. Choose the Currency for a Report
  • If your org has an international clientele, chances are some of your users want the option to review the financial data in other currencies. Lightning report builder lets users set the currency on a report.
  • In an org that has multiple currencies enabled and currencies activated, select the report. Click Edit. In the currency picklist, set the currency. To preserve your choice for this report, click Save.

Screenshot (156)

Dashboards: More Filter Values, Joined Reports as Source Reports, Custom Axis Ranges, and Decimal Precision

  1. Add Up to 50 Values to Each Dashboard Filter

Dashboards illuminate your business data, and dashboard filters let you shine a light on specific parts of your business. Previously, you could add up to 10 distinct values (like State equals California) to a dashboard filter. Now you can add up to 50 distinct values to each dashboard filter.

  • To view, refresh, and apply filters to dashboards, you need the Run Reports user permission.
  • To add filters to dashboards, you need one of these permissions: Create and Customize Dashboards, Edit My Dashboards, or Manage Dashboards in Public Folders.
  • To add or edit filters to dynamic dashboards, you need the Manage Dynamic Dashboards user permission.
  • With up to 50 values per filter, you can filter by all 50 states.
  • Add or edit a filter, choose a field, and then click Add Filter Value to add up to 50 filter values.

Screenshot (157)

    2. Set Decimal Precision in Dashboard Charts and Tables
  • Choose how many decimal places charts, tables, and metrics show in dashboards, from 0 to 5.
  • To set decimal places for a dashboard component, you need one of these permissions: Create and Customize Dashboards, Edit My Dashboards, or Manage Dashboards in Public Folders
  • To set decimal places for a dashboard component on a dynamic dashboard, you need the Manage Dynamic Dashboards user permission.
  • Because 14.11B is more than 14B and the difference between 90%, 90.1%, and 90.10001% matters.

Edit or add a dashboard component, then specify decimal precision with Decimal Places.

Screenshot (158).png

3. Use Joined Reports as Source Reports for Dashboard Components

With a joined report as its source report, a dashboard component can contain data from multiple standard or custom report types. Or, you can provide multiple views of the same object.

  • To use a joined report as a source report for a dashboard component, you need one of these permissions: Create and Customize Dashboards, Edit My Dashboards, or Manage Dashboards in Public Folders.
  • To use a joined report as a source report for a dashboard component on a dynamic dashboard, you need the Manage Dynamic Dashboards user permission.
  • See accounts with open cases by joining the cases report type to the accounts report type, filtering for open cases, and grouping by account. Or see cases by status by joining the cases report type together on three joined report blocks and filtering each block by status: open, in progress, and closed.
  • To use a joined report as a source report, it must have a chart. To add a chart to your joined report, edit it with the Lightning Experience report builder or edit it in Salesforce Classic. (You can’t add charts to joined reports using the Salesforce Classic report builder embedded in Lightning Experience.) Then, click Add Chart.

Screenshot (159).png

Usability and Performance Improvements

  1. Dependent Picklists No Longer Have a Default Value Selected: 

Dependent picklists in communities no longer have a default value when loaded, so they now work the same in communities as they do in your internal org. We made this change because picklists did not consistently assign default values in all environments. If your site design or code assumes a default picklist selection, you need to adjust it.

2. Guest Users Are Redirected to a Login Page When Visiting Record Pages

Salesforce has standardized the guest user experience for all Record pages. Now guest users are redirected to a login page when attempting to visit Record Detail, Record List, or Record Related List pages. Previously, guest users were redirected to a login only when trying to access the Record Detail page.

  • This feature is available in Lightning and Salesforce Tabs + Visualforce communities accessed through Lightning Experience and Salesforce Classic. Communities are available in Enterprise, Performance, Unlimited, and Developer editions.
  • For the redirect to work, the guest user must be able to access to the correct object. For the Record List page, the guest user must have access to the appropriate entity. For the Record Related List page, the guest user must have access to the entity of the related list and the parent record to which the related list is attached.
    3. Get Faster Page Response with Support for Optional URL Query Parameters

To improve performance and flexibility, we added support for query parameters to navigateToURL. {!EL} expressions are automatically replaced with a dynamic Aura expression. The Aura expression updates at runtime to parameters provided by the current page, such as parameters from the route or URL query parameters. This change improves performance because only components that are necessary during navigation events are loaded rather than reloading the entire page. However, this change can mean that custom components may not work as expected.

  • This change affects Lightning and Salesforce Tabs + Visualforce communities accessed through Lightning Experience and Salesforce Classic. Communities are available in Essentials, Enterprise, Performance, Unlimited, and Developer editions.
  • This change affects Lightning components at runtime that have the following characteristics.
    • The component has a required String attribute, which doesn’t have a default value
    • The component has a corresponding design attribute
    • The value of the design attribute is an “{!EL}” expression. The expression can be set either as a default value on the design attribute or by changing the value in the Community Builder component properties.
    • The component lives on a page that has no parameter from the route or from the URL query strings for the {!EL} value
  • Previously, the component didn’t load if it met all these characteristics, and so users didn’t see it. Starting with Winter ‘19, Aura tries to load the component regardless, which means that some components might now show on a page with errors in them.
  • If you’ve written custom components that meet the above characteristics, check your code to make sure that you’re not performing unsafe operations on component attributes that might now be undefined.
   4. Decrease Page Load Times with Community Content Delivery Network (Generally Available)

Introduced as a pilot feature in Winter ‘18, the Community Content Delivery Network (CDN) is now available to everyone for free. Use the CDN to decrease your community’s page load time and improve your member’s experience.

  • Provision and activate the CDN by editing your custom domain. Select Salesforce serves the domain over HTTPS, using a Salesforce content delivery network (CDN) partner and a shared HTTPS certificate and click Save.
  • Provisioning takes 2–6 hours but requires no downtime and you are emailed when it’s finished. When it’s complete, activate your domain. Activation takes 10–15 minutes and does temporarily make your community unavailable, so we recommend doing this step at a time when traffic is light.


  1. Save Your Chatter Posts as Drafts: 

Have you ever lost your work in the middle of writing an important Chatter post? We know how frustrating that is. Introducing Draft Posts, a new option to automatically save all your unpublished feed items.

As you type a new post, Chatter saves your work to the My Drafts tab. Add files, links, images, mentions, hashtags, and any other rich text, because we save it all.



  • You can access your drafts in My Drafts to publish, edit, or delete them.

Screenshot (160)

  • When you save a post with a hashtag, the corresponding topic is not created until the post is published.
  • To turn on Draft Posts in your org, navigate to the Chatter setup menu. Under the Draft Posts section, select Allow draft posts.
  2. It’s About Time—Date Format Fixed for Spanish Locales

The date and time information that appears with feed items and comments is fixed. The rule is that the locale setting determines the date-time format, and the language setting determines the language. For Spanish locales, when the language setting was English, a mix of Spanish and English for the date and time was shown. Now it’s all fixed.


  1. New and Changed API: 

There are many new standard objects added. Few changed objects are:


These fields are new

  • FirstOpenedDate
  • IsBounced
  • IsOpened
  • IsTracked
  • LastOpenedDate


These values are new to the Type field

  • Quick Text
  • Macro

Note: There are a few other fields which are changed. For the complete reference please visit Salesforce Winter 19 release notes.

2. SOSL: Changed Clauses


USING ListView = is an optional returning clause used to search within a single given object’s list view. You can now use USING ListView = Recent to search for the most recently accessed items that were viewed or referenced by the current user.

3. REST API: New and Changed Calls
  • New Calls

/v44.0/consent/action/  – Determine the actions to which your customer has (or hasn’t) consented, regardless of which objects in Salesforce recorded the consent.

  • Changed Calls

/vXX.X/limits/ – For the data storage and file storage reports, /vXX.X/limits/ performs calculations the same way as the Salesforce user interface. The API now uses these definitions:

1 KB = 1,024 bytes

Previously, it used these definitions:

1 KB = 1,000 bytes.

Hope, this helped you learn new and blaze your trail!!

Check out Highlights of Winter’19 Release PartI: Part I Highlights

Source:  Salesforce Winter’19 Release Notes

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s