Salesforce Winter ’18 Top Features For Platform

Salesforce Winter ’18 Top Features For Platform

Salesforce presents 54th release this year; we feel enchanted to try-out our hands upon incredible new features from winter ’18 version. Subsequently, playing with the latest version directly on the platform brings out our favorite top 6 highlights from the winter ’18 release. Let’s check them out here!!

Salesforce Service Salesforce DX: Salesforce DX is a whole new and innovative way to regulate and flourish Salesforce applications. Whether you’re an individual developer or functioning as part of an organization, Salesforce DX contributes an integrated end-to-end lifecycle design for high-performance agile development, and above all, Salesforce creates it the approachable and flexible for you to develop with coexisting tools.

Salesforce DX is a compilation of products and services that transport source drive development. Now you can get gain from modern collaboration technologies such as:

  • Get to version control everything across your team
  • Your code
  • Your org configuration
  • Metadata

It provides more excellent ability to test out features with determination. Also, Salesforce DX CLI’s is a powerful command-line interface that facilitates development and builds automation while working with your Salesforce org and much more.

Salesforce IoT Explorer: Salesforce IOT Explorer is inherent to the core Salesforce platform; you can launch precisely from the setup. Salesforce is accessing device data in real time and monitoring the energy output of a connected product. The orchestrations interface allows you to see various states with associated declarative rules that automatically generates a service case when IOT Explorer detects a fault. Here the case details are directly set up within service console that has been notifying by reading the device data. A service technician can now escalate and route that case accordingly based on the device data. With Salesforce IOT Explorer the user experience and processing engine are all built into the core Salesforce platform and is fully integrated across all your business processes. All this benefits you to connect with customers across any connected device and revolutionize the way you service to sell and market.

Einstein Analytics New Story Recommendations and Visualizations: The latest Einstein analytics enhancement included exciting new features for Einstein discovery drive, smarter insights and impressed with new story visualizations. Salesforce has taken care of all the work while it recommends improvement to your data. It will automatically detect any duplicates and outliers so that you can create the best version of your analytical report. With the addition of story timelines, you can tap back and forth between your story and what’s going to change over time is the ability to discover these consistent patterns in your data without the use of any data scientist, it allows your team to work smarter and faster.

Einstein Analytics SDK with Encryption at Rest: In winter 18, there’s an opening up the foundation of our analytics platform to everyone with the Einstein analytics SDK. Whether your app is built in lightning visualforce or even outside of Salesforce, you can now have your apps interact with any analytics dashboard.  Salesforce has now introduced both the analytics web SDK which allows you to quickly connect with custom applications as well as the analytics effects SDK where you can put up queries of your analytics data from any apex class encryption at rest. It might built-in natively, you’ll never have to worry about the security and protection of your analytics data.

Lightening Experience Enhancements: In the winter release, you’ll undoubtedly notice a drastically changed Lightning experience. These enhancements are results of incredible research feedback from Salesforce community and a strong desire to see customers succeed.

First comes first, This feature has an all-new option which is Scanning information.  You’ll soon notice the more compelling contrast between the content and the background. Salesforce has improvised legibility with enhanced font sizes and with explicit hierarchies between the textbox, headers, body content, and buttons. You will also observe more compact design with increased content density and less white space on the page. Now you can view more data in the same area and spend less time scrolling, but that’s not all. We’ve infused the lightning experience with some Salesforce fun. Trailhead branding built right in; these new enhancements help make every user attain the most out of their lightning experience and be more productively efficient.

New Lightning Components: It is the moment of joy to share that; Salesforce has added even more based lightning components for Salesforce developer community. Based lightning components are the building blocks that make up the modern lightning experience, Lightning apps, and lightning communities user interfaces.

New and Changed Lightning Components are as follows:

  • Added information about new components, lightning:outputField and lightning:recordViewForm, and changes to lightning:datatable and lightning:verticalNavigation
  • New and Changed Lightning Components
  • Added information about changes to lightning:button and lightning:buttonStateful.
  • New and Changed Lightning Interfaces
  • Added support for the force:hasRecordId interface for Lightning components used in the Utility Bar.

Hope this has helped you with the all new winter 18 release, for more information you can check us out at

How We Can Use Third Party JavaScript Libraries With Lightning Components?

How We Can Use Third Party JavaScript Libraries With Lightning Components?

Third-party Libraries are used by most of the developers nowadays because Third-party libraries provide quick and easy work around that can save you a lot of time and help you avoid some lines and efforts while writing codes.

Third-party libraries usually fall in one of the following categories:

  1. DOM manipulation libraries ( ex. jQuery, etc.)
  2. Specialized Utility Libraries (ex. moment.js, numeral.js, etc)
  3. UI Libraries (ex. Bootstrap, jQuery UI, etc.)
  4. Data Visualization Libraries (ex. D3, Chart.js, Leaflet, etc.)
  5. MVC Frameworks (ex. React, Angular, etc.)

How to use third party libraries in lighting components-

There is a whole lot of powerful features which are provided by the Lightning Framework. In lighting components, Functionalities by your library might not always work.
In lightning component, we need to add these libraries to a static resource, and then we can include the library by using tag <ltng:require>
Upload everything in zip format under static resources. And use them in <ltng:require> tag.


&amp;lt;ltng:require styles="{!$Resource.YourCSSResource}" scripts="{!$Resource.YourJSResource}" afterScriptsLoaded="{!c.afterScriptsLoaded}"/&amp;gt;

afterScriptsLoaded attribute is used to execute some javascript method after the script is loaded.

To include a JavaScript library that you’ve uploaded as a static resource, use a <ltng:require> tag in your .cmp or .app markup.
Using styles attributes, you can include the .css resources into the component or app and be using scripts attribute you can include the javascript resources into the component or page.

Here is an Example of aura component:

&amp;lt;ltng:require styles="{!$Resource.YourCSSResource}" scripts="{!$Resource.YourJSResource}" afterScriptsLoaded="{!c.libLoaded}" /&amp;gt;
&amp;lt;div class='mynamespace'&amp;gt;
&amp;lt;div class="dropdown"&amp;gt;
&amp;lt;ul class="dropdown-menu" role="menu" aria-labelledby="mLabel"&amp;gt;
&amp;lt;li role="presentation"&amp;gt;&amp;lt;a role="menuitem" href=""&amp;gt;Action&amp;lt;/a&amp;gt;&amp;lt;/li&amp;gt;
&amp;lt;li role="presentation"&amp;gt;&amp;lt;a role="menuitem" href=""&amp;gt;Another action&amp;lt;/a&amp;gt;&amp;lt;/li&amp;gt;

Class mynamespace, dropdown, dropdown-menu would be defined into the libraries.This is the method of how one can use JS Function which will always execute after loading of the script.

libLoaded: function(component, event, helper) {
alert('ready to go');

Here is the example of JQuery sortable. We have to add the JQuery resource in the page and use functions to perform the functionality.


You can use bootstrap classes for CSS. After adding the Bootstrap resource, you need to add the class on the element.

Steps to include bootstrap in your lightning:

  • Download the optimized Bootstrap package.
  • Unzip that package and go to Setup > Build > Develop > Static Resources and click New.
  • Specify bootstrap as the Name, then click the Choose File button, and select the bootstrap.css in the dist/CSS directory of the unzipped bootstrap folder.

After adding bootstrap in static resources, you can use the classes of bootstrap to your component elements.

&amp;lt;div class="navbar-header"&amp;gt;
&amp;lt;a href="#" class="navbar-brand"&amp;gt;Accounts Details&amp;lt;/a&amp;gt;

So, this is how you can implements the standard UI by third-party libraries with your lightning components.

Aura Basics

Aura Basics

I have been working a lot on Salesforce Lightning framework recently and completed more than 5 big small projects in converting Salesforce classic apps into making them lightning ready. Let me summarize what I have learned recently.

What is Aura?

Aura is a UI framework for developing dynamic web apps for mobile and desktop devices.Aura supports partitioned multi-tier component development that bridges the client and server. It uses JavaScript on the client side and Java on the server side.

The screenshot below merely give you a hint of the look and feel of an Aura App:

 What is an APP?
The line just above the screenshot “look and feel of an Aura APP”. The word APP(bold) is like container in Aura i.e. it holds the component which is having the fields and button in it. Let’s get into little bit technical explanation of the above screenshot. The component file will have the .cmp extension whereas App will have the .app extension.

Component aura_basic (aura_basic.cmp)

<aura:component >

<!-- Below div is used for header designing -->

<div class="slds-page-header" role="banner">

     <div class="slds-grid">

       <div class="slds-col">

         <p class="slds-text-heading--label">Aura</p>

         <h1 class="slds-text-heading--medium">Component</h1>




<!-- this form is being design so as to create complete  input form -->

    <form class="slds-form--stacked">     

<div class="slds-form-element slds-is-required">

         <div class="slds-form-element__control">

             <ui:inputText aura:id="expname" label="Input Text Field"  class="slds-input" labelClass="slds-form-element__label"/>


    <div class="slds-form-element slds-is-required">

         <div class="slds-form-element__control">

             <ui:inputNumber aura:id="amount" label="Number Field"  class="slds-input" labelClass="slds-form-element__label"/>

     <div class="slds-form-element">

         <div class="slds-form-element__control">

             <ui:inputDate aura:id="expdate" label="Date Field" class="slds-input" labelClass="slds-form-element__label" displayDatePicker="true"/>


     <div class="slds-form-element">

         <ui:inputCheckbox aura:id="reimbursed" label="Checkbox" class="slds-checkbox" labelClass="slds-form-element__label"/>

     <div class="slds-form-element">

         <ui:button label="Submit" class="slds-button slds-button--brand" />





<!– “force: slds”  attribute is used to give the page as lightning effect–>

<aura:application extends=”force:slds”>

<c:aura_basic />



Lightning Bundle:

Now let me introduce you all to the term Lightning Bundle. Lightning Bundle basically, a collaborative name of the following files:

  • Component
  • Controller JS File (Client-Side JavaScript file)
  • Helper JS File (Server-Side JavaScript file)
  • Style File (CSS file)
  • Renderer
  • Documentation
  • SVG (Depreciated)

We basically work on the first four files (Bold). SVG is used for icons but it is outdated and salesforce now is introducing lightning icons instead.

Let’s talk about Component, Controller JS, Helper JS and Style file individually.

Component: Components are the self-contained and reusable units of an app. They represent a reusable section of the UI and can range in granularity from a single line of text to an entire app.

A component can contain other components, as well as HTML, CSS, JavaScript, or any other Web-enabled code. This enables you to build apps with sophisticated UIs.

Controller JS: A client-side controller handles events within a component. It’s a JavaScript resource that defines the functions for all of the component’s actions. Client-side controllers are surrounded by brackets and curly braces to denote a JSON object containing a map of name-value pairs.


myAction : function(component, event, helper){

// add code for the action




Each action function takes three parameters:

  • component—The component to which the controller belongs.
  • event—The event that the action is handling.
  • helper—The component’s helper, which is optional. A helper contains functions that can be reused by any JavaScript code in the component bundle.    

Helper JS: A helper resource is part of the component bundle and is auto-wired via the naming convention, <componentName>Helper.js. To create a helper using the Developer Console, click HELPER in the sidebar of the component. This helper file is valid within the scope of the component to which it’s auto-wired.

The following code shows you how to call the updateItem helper function in a controller, which can be used with a custom event handler.

Controller JS File :


newItemEvent : function(component, event, helper){

helper.updateItem(component, item, callback);




Helper JS FIle :


updateItem : function(component, item, callback){

//Update the items via a server-side action

var action = component.get(“c.saveItem”);

action.setParams({“item” : item});

//Set any optional callback and enqueue the action

if (callback){

action.setCallback(this, callback);






CSS File : Style your components with CSS. Let’s look at a sample helloHTML.cmp component. The CSS is in helloHTML.css.


Component Source:


<div class=”white”>

Hello, HTML!


<h2>Check out the style in this list.</h2>


<li class=”red”>I’m red.</li>

<li class=”blue”>I’m blue.</li>

<li class=”green”>I’m green.</li>


CSS Source:


background-color: grey;


.THIS.white {

background-color: white;


.THIS .red {

background-color: red;


.THIS .blue {

background-color: blue;


.THIS .green {

background-color: green;



Complete Example:
Let’s have a glimpse of Aura where on submitting the Account Name you will get all the contacts related to that Account.


<aura:application extends=”force:slds”>

<c:GetContactList />




<aura:component Controller=”ContactListAura”>

  <aura:attribute name=”contList” type=”Object[]” />

<div class=”slds-page-header” role=”banner”>

<div class=”slds-grid”>

<div class=”slds-col”>

<p class=”slds-text-heading–label”>Aura</p>

<h1 class=”slds-text-heading–medium”>Component</h1>




<form class=”slds-form–stacked”>

<div class=”slds-form-element slds-is-required”>

<div class=”slds-form-element__control”>

<ui:inputText aura:id=”accName” label=”Input Text Field”  class=”slds-input” labelClass=”slds-form-element__label” placeholder=”Enter Account Name”/>



<div class=”slds-form-element”>

<ui:button label=”Submit”  class=”slds-button slds-button–brand” press=”{!c.getSubmit}” />


<table class=”slds-table slds-table_bordered slds-table_cell-buffer”>


<tr class=”slds-text-title_caps”>

<th scope=”col”>

<div class=”slds-truncate” title=”Name”>Name</div>





<aura:iteration items=”{!v.contList}” var=”item”>












getSubmit : function(component, event, helper){

helper.getContactListHelper(component, event, helper);






getContactListHelper : function(component, event, helper) {

var action = component.get(“c.getContactLists“);


“nm” : component.find(“accName“).get(“v.value”)


action.setCallback(this, function(a){

component.set(“v.contList“, a.getReturnValue());

console.log(‘v.contList ‘+component.get(“v.contList”));







public class ContactListAura {


public static List<Contact>getContactLists(String nm){

system.debug(‘nm–> ‘+nm);


return [SELECT ID,Name FROM CONTACT WHERE Account.Name=:nm];


return null;




Flow of Page :

<aura:attribute name=”contList” type=”Object[]” />

The very first line after <aura:component> will be use to display the data on the Component. When I have entered the Account Name to the Input Text and click “Submit”. It has evoked getSubmit method of Client-Side JS i.e. Controller JS method.

In Controller JS.

helper.getContactListHelper(component, event, helper);

will call the HELPER JS method i.e. Server-Side JS. In Helper JS the line

var action = component.get(“c.getContactLists”);

Give the reference of the AuraEnabled method in the Apex class (We have set the Controller attribute of aura:component tag with the name of ApexClass Name.)


           “nm” : component.find(“accName”).get(“v.value”)



Will set the set the Parameter of Apex Method with the Value which we have inserted in the input text having aura Id as accName.

action.setCallback(this, function(a){

           component.set(“v.contList”, a.getReturnValue());

           console.log(‘v.contList ‘+component.get(“v.contList”));



This line will set the variable which we will be using on the component to display the data.

In the above snippet, “this” keyword is used to refer the current component which has invoked the complete execution.


This line is most important as it is responsible for getting the returning result from apex class and set it to the attribute/variable which we are going to use the component.

Note: Alphabet v is used to access variables whereas c is used to access controllers.

Difference Between SLDS & Aura Components

Difference Between SLDS & Aura Components

As we all know Lightning has been added to Salesforce very recently and it is the future of Salesforce. So a lot of people who are new to Lightning but have the curiosity to learn it sometimes find it difficult to understand.I realized that the best way to start would be by describing what are the differences between Salesforce Lightning Design System and Salesforce Lightning Components Framework. So in this blog, I will try to explain what are the major differences between Salesforce Lightning Design System and Salesforce Lightning Components Framework and hopefully, it will clear out most of the doubts that a new developer is having regarding The Lightning Framework.

Introduction to Salesforce Lightning Design System

It is a CSS framework which is used for creating dynamic web apps.   By Using SLDS  We can make our apps responsive and can also provide  Look and feel similar to the Lightning Experience.

Steps to install the SLDS Unmanaged Packaged: For using SLDS in our Salesforce org. First We need to install the Latest Salesforce Lightning Design System unmanaged packaged as a static resource zip file.

  • Log into your Developer Org.
  • Open the Salesforce Lightning Design System in a Separate Window.
  • Go to the Download Section.
  • Click on the latest unmanaged package
  • Now click on Install it.

After Completing the above steps the package will get installed into your org.

Benefits of using Salesforce Lightning Design System:

  • By using SLDS it’s easier to build apps which are responsive and also have the look and feel similar to 260662Lightning Experience.
  • It is compatible with multiple browsers like  Google Chrome, Latest Mozilla Firefox,   Latest  Safari Latest Internet Explorer 11 and above.
  • It provides a robust grid system because of which It is easier to build responsive layouts that work elegantly across different screen sizes.
  • The CSS is fully namespaced with the slds- prefix to avoid CSS conflicts.

Introduction To Lightning Components Framework 

It is built using Open Source Aura Framework. By Using Aura Framework We can build apps completely independent of the Data present in our Salesforce org.

Benefits Of Lightning Components Framework:
  • It provides an out-of-the-box set of components for building apps
  • When we use Lightning Components  Framework We do not need to worry about the optimization of our apps for different devices as  Components take care of that by themselves.
  • It uses the stateful client and stateless server architecture which uses  Javascript on the client side for managing UI component metadata and Application data.
  • It uses an Event Driven architecture which enhances the decoupling  Between components.
  • It supports the latest browser technology such as HTML5, CSS3.
 Use Of Developer Console:

The Developer Console provides us the tools which are Used for developing Components and applications. By Using Developer Console We can perform the following functions

  • We need to use File option for either creating or opening the following Lightning Resources:
    • Application
    • ComponentInterface
    • Event
  •  We need to use the sidebar to create or open client-side resource.
  • Component
  • Controller
  • Helper
  • Style
  • Documentation
  • Render
Differences Between SLDS and Aura

free-Vector-File-EPS-87250 FRAMEWORK:

  • First of all Salesforce Lightning Design System is a CSS-based framework.
  • Used for creating dynamic apps while on the other hand Lightning Components Framework uses aura components for creating the dynamic apps.


  • In the case of Lightning Components Framework, We need to write two Controllers one for client side and the other one for server side. while in the case of Salesforce Lightning Design System we need to write only one controller which will be a server side controller.

Note: Java scriptThe client side Controller that we will write for Lightning Components Framework would be written using javascript while the server side controller will be written using apex.


  • By using Lightning Components Framework we can build an app which will be completely independent of Salesforce data while in the case of Salesforce Lightning Design System(SLDS) do need some Salesforce data which can be accessed using Javascript Remote Objects.


  • Lightning Components Framework is client-side centric while Salesforce Lightning Design System are server-side centric.


  • Because Lightning Components are client side centric therefore they are better.
  • Equipped for creating dynamic web apps then Salesforce Lightning Design    System.


  • As mentioned above  Lightning Components are client side centric therefore they are more mobile friendly as compared to the Salesforce Lightning Design  System(SLDS).


  • In Lightning Component Framework Event Driven programming such as Javascript and Java swing is used for writing helpers which respond to Interface events as they occur but in Salesforce Designing System there is no such concept of Event Driven Programming.


  • Because In the Lightning Component Framework we need to create two controllers and also it uses  event-driven programming language such as  Javascript, therefore, it is much for complex as compared to the Salesforce Lightning Design System(SLDS)