Aura Elements in Salesforce – This is All You Must Know! |

What’s Aura Part?

A UI framework for creating net purposes for desktop and cellular platforms is named the Aura Lightning Part Framework. This modern framework can be utilized to create dynamic single-page purposes. On the consumer and server sides, it employs JavaScript because the controller of the part class. Quite a few consumer interface (UI) components provided by the lightning namespace come pre-configured to make use of the Salesforce Lightning Design System (SLDS). Salesforce directors use these components to construct single-page net purposes that supply a seamless platform expertise for a spread of duties.

The place we Can Use Lightning Elements?

Your Salesforce org could be customised in a wide range of methods utilizing Aura Lightning parts. Moreover, you should utilize Lightning parts to construct apps which can be already accessible on the Salesforce Org. Moreover, it’s potential to develop apps that run on a number of platforms. The required information are saved in “Bundles” by Lightning Elements and Functions:

1. Part – The structure of the part is configured utilizing a markup language.

2. Controller – For client-side processing, a JavaScript Controller is required, however an apex controller is used for server-side processing.

3. Design File – When a part is utilized in Lightning pages or Lightning App Builder, its design-time behaviour is described in a design file.

4. Documentation File – Customers who’ve obtained your part can discover pattern code or reference supplies in a documentation file.

5. Helper – A helper’s objective is to retailer reusable JavaScript operations that the controller manages.

6. SVG File –Customized icons that can be utilized as additional references could be included in an SVG file.

Remember to take a look at: Javascript for Lightning Web Component | Salesforce Lightning

We’ll focus on the Aura Lightning Part

1: First we’ll create Lightning Part.

For this Open Developer Console -> New -> Lightning Part.

Identify the Lightning Part and Test all Part Configuration and we are able to add our parts to the Salesforce.

Code:-

<aura:part implements=”drive:appHostable,flexipage:availableForAll  
PageTypes,flexipage:availableForRecordHome,drive:hasRecordId, 
forceCommunity:availableForAllPageTypes,drive:lightningQuickAction”          entry=”world” > 
<h1>Hey Lightning!</h1> 
</aura:part>

2: To preview that Aura Part, We’ve to make use of the Lightning Software wherein we name that Aura Part as proven under:

<aura:software extends="drive:slds"> 
<c:ComponentName/> 
</aura:software>

3. Attributes – Attributes have two necessary parameters i.e. Identify and Kind.

4. Worth Suppliers – The worth supplier permits us to entry the worth of a part attribute in part markup and Javascript controller.

Instance:- {!v.AccountData}

5. Motion Suppliers – The motion supplier permits us to deal with actions, occasions, handlers for the part.

Instance:- <lightning:button label=”Save” onclick=”{!c.onSave}” />

Take a look at one other superb weblog by Harsh right here: Using Batch Apex in Salesforce | The How-to Guide

Occasions in Salesforce Lightning Part

The Lightning Framework’s event-driven structure permits the communication between varied occasions. When a consumer interacts with the consumer interface, JavaScript controller actions which can be triggered by that interplay hearth lightning occasions. Occasions can deal with the communication between Elements.

There are two varieties of customized occasions in Lightning: