Lightning Experience Vs Salesforce1 Using Lightning Components

Posted by Sushma Gangavalli | Posted On February 1st, 2017|Lightning Experience

Salesforce1 is a mobile app development platform which has been built to fulfill today’s Mobile and Social Solution needs. Salesforce developers build apps using various user interface and Saleforce1 provides us with a Platform which manages the apps without limiting our business needs. It is designed for scaling with open API’s for being extensible and a powerful developer tool. Salesforce1 allows administrators or developers to create custom apps that are supported by mobile back-end services. It also supports offline data. Infact, all of the recently viewed items can be viewed offline.

Salesforce Lightning Experience

Salesforce Lightning Experience essentially brings out the mobile experience to the desktop view with a modern user interface. It includes entirely redesigned pages and we can build apps visually with Lightning components and Lightning App builder, the former being a framework for developing dynamic web applications for mobile and desktop devices. The Salesforce Lightning Design System helps developers build responsive lightning components.

Salesforce1 and Lightning Experience Actions is the section predefined by Salesforce. We can override the predefined actions to set a customized list of actions on Salesforce1 and Lightning Experience pages in the page layout itself.

Lightning Component Actions invokes a lightning component. These are supported in Lightning Experience and Salesforce1 and in turn the Lightning Component Actions support Apex and Javascript. We can find them in Salesforce1 & Lightning Actions category in the page layout of the editor’s palette.

Configuring Lightning Components for Custom Actions

Lightning Quick Action and/or Lightning Quick Action Without Header interfaces can be used as a custom action in Lightning Experience or Salesforce1. Lightning Components with the above mentioned interfaces can also be used as object-specific actions.

An example lightning component declaration with the above interface is as follows:

<aura:component implements=”force:lightningQuickAction”>

</aura:component>

force:showToast event is used in lightning components to display results at the top of the screen in lightning experience or in salesforce1.

<aura:component implements=”force:showToast”>

</aura:component>

Configure Lightning Components for Record-Specific Actions

Adding force:hasRecordId interface to a Lightning component enables the component to be assigned the ID of the currently displaying record.

The current record Id is useful if the component is rendered as an object-specific custom action in Lightning Experience or Salesforce1.

<aura:component implements=”force:hasRecordId”>

</aura:component>

Lightning App Builder is the key centric element for creating apps or tabs in Salesforce1 and in Lightning experience as well. It is a point-and-click tool that makes it easy to create custom pages. We can add multiple components on a single page according to the requirement of users. It is also possible to use standard, custom and third party components in the Lightning page.

While Standard Components are the components built by Salesforce, Custom Components are the ones that are created in the org. At the same time, Third Party Components are the components installed from a AppExchange package.

Lightning Pages

A Lightning Page is a custom layout that lets you design specific pages in Salesforce1. Lightning Pages that are built using Lightning components are compact, configurable, and reusable elements that can be dragged and dropped into the Lightning App Builder. We can also add global actions to a Lightning page and when a user accesses a Lightning page from Salesforce1 global actions appear in its action bar.

Lightning Page Types

An App Page is to create a home page for a third-party app that can be added directly into the Salesforce1 and Lightning Experience navigation menus. It allows the users to quickly access the objects and items that are of the most importance in that app.

Home pages contain features relevant to specific types of users, and we can assign the customized pages to different user profiles. These are supported only in Lightning Experience.

Record pages are a customized version of an object’s record page. Again, Custom Record pages are supported in Lightning Experience only.

Here is the configuration to add a Lightning component in Lightning App Builder:

SetUp–>Lightning App Builder.

Attached below is the screenshot of Lightning App Builder that contains standard and custom lightning components.

Salesforce 1 vs Lightning Experience

Salesforce1 VS. Lightning Experience

Salesforce 1 Lightning Experience
Apps created with lightning components in Lightning App builder App pages can be directly viewed in the Salesforce1 navigation menu available items. By adding the same to the selected Items, We can directly access the lightning component from salesforce1. There is a possibility of creating tabs or apps with Lightning components in Lightning Experience using the Lightning App Builder.
A Lightning component cannot be added directly in the record related list in salesforce1. You can Add a Lightning component in the record retail list as well.
Provides feasibility to view visualforce pages in salesforce1 by enabling the checkbox available to salesforce mobile app on visualforce page. You have to Configure a visualforce page that has enabled the Availability for Salesforce mobile apps and Lightning Pages in the Lightning experience for a record by creating a custom tab

 

 

Categories: Lightning Experience

Sushma Gangavalli

Sushma had joined AppShark as a fresher and has come a long way since then. She now has 2.4 years of experience and loves watching movies in her leisure!

Leave a Reply