Salesforce Lightning Tutorial: Lightning Component basics<\/h1>\n

Chapter 1: Prerequisite for Lightning Component Development<\/u><\/span><\/h2>\n

My Domain<\/h2>\n

Before we begin to deep dive into the development of Lightning Component we need few things to be enabled in our Developer Edition Org. First thing is to enable My Domain in the DE org. Enabling My Domain and activating it can take up to half an hour, therefore we need to have My Domain as early as possible for any development.<\/p>\n

Adding a Custom Domain, serves many other purposes as well, which are mentioned below:-<\/p>\n

\n
• Highlight business identity and unique domain URL.<\/li>\n
• Login screen can be branded and customized.<\/li>\n
• Work in multiple Salesforce Org at the same time.<\/li>\n
• Set up custom login policies.<\/li>\n
• It is a required feature for Single-sign On facility and Lightning Components. <\/strong><\/li>\n<\/ul>\n

  My Domain is also available for sandboxes and more info about My Domain can be found in the Below mentioned document.<\/p>\n

  https:\/\/help.salesforce.com\/articleView?id=domain_name_overview.htm&type=5<\/p>\n

  Before we begin the development lets create the custom object that we require for this tutorial.<\/p>\n

  To create a new object in the Lightning Experience(LEX), follow the below instruction these instruction are given assuming the you have enabled the Lightning experience in your org or you already have it enabled.<\/p>\n

  \n
  1. Go to Object Manager, by clicking on the gear icon on the top-right of your org, then click on the Setup.Fig 1.1: Setup link<\/li>\n
  2. A new window will open, click on the object manager tab, this will open the list view of the objects presently deployed in you Org, now click on the create button and then click on custom object.\n

     Fig 1.2: Object Manager Tab<\/p>\n

     Fig 1.3: Create button<\/p>\n<\/li>\n

  3. Now fill up all the required fields i.e. Label, Plural Label, Object Name Record Name and its Data type, and other features which are mentioned below, accept all the default values other than the one mentioned below.\n

     Fig 1.4: Object Definition Page<\/p>\n\n\n\n\n\n\n\n

     Field<\/strong><\/td>\n	Value<\/strong><\/td>\n<\/tr>\n
     Label<\/td>\n	Expense<\/td>\n<\/tr>\n
     Plural Label<\/td>\n	Expenses<\/td>\n<\/tr>\n
     Starts With vowel sound<\/td>\n	checked<\/td>\n<\/tr>\n
     Object Name<\/td>\n	\n Expense__c<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/li>\n Once the object\u2019s definition is saved, then on the object definition page, click on the link Fields & Relationships link and create custom fields on this object. Click on the new button, it will take you to the Data type selection screen.\n Fig 1.5: Object definition page<\/p>\n Fig 1.6: Field Data type Selection page<\/li>\n Create the below mentioned fields \n\n\n\n\n\n\n\n Field Label <\/strong><\/td>\n API Name<\/strong><\/td>\n Field Type<\/strong><\/td>\n<\/tr>\n Amount<\/td>\n Amount__c<\/td>\n Number(16,2)<\/td>\n<\/tr>\n Client<\/td>\n Client__c<\/td>\n Text(50)<\/td>\n<\/tr>\n Date<\/td>\n Date__c<\/td>\n Date<\/td>\n<\/tr>\n Reimbursed<\/td>\n Reimbursed__c<\/td>\n Checkbox<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Make sure that before we begin, you must have some knowledge of Apex Basics and Database, otherwise it would very difficult to understand some concept mentioned here.<\/li>\n<\/ol>\n \u00a0Chapter 2: Getting Started with Lightning Components<\/span><\/h2>\n Before we dive into the abyss of Lightning, first we need to know that why we should use lightning and what are the benefits of using the Lightning Component.\u00a0 Its benefit includes the following features.<\/p>\n \n Out of the box Component set to kick start our app building experience, these components are smart and do not require optimization for different devices as they take care of it themselves.<\/li>\n Performance, as we use stateful Client and stateless server architecture and rely on JavaScript on the client site to deal with all the UI component meta data and app data. Server calls are reduced as they are called only when they are necessary.<\/li>\n Event Driven architecture, for better performance of components.<\/li>\n Faster development device-aware and cross browser compatibility and component rich ecosystem.<\/li>\n<\/ul>\n Let\u2019s know Lightning Components framework a bit more.<\/p>\n What Is the Lightning Components Framework?<\/h2>\n It is a UI framework used for developing apps which run both on mobile devices and desktop, it makes use of single page application architecture using dynamic, responsive components for the interface. It implements JavaScript on the client side and Apex on the server side.<\/p>\n Fig 2.1 Lightning Framework<\/p>\n It is a framework with a collection of code and services to help developers create unique and modern Apps, it was born to build salesforce for mobile devices but later on it was decided to use this framework for both desktop and mobile devices. This framework is for building Single Page application.<\/p>\n Where You Can Use Lightning Components<\/h2>\n Lightning components can be used in many different ways, like customizing the org, standalone app and even apps that can be hosted on other platforms (using Lightning out).<\/p>\n Lightning components can be embedded in LEX app launcher, as a tab in Salesforce App Navigation. They can be used in Lightning App Builder and Community builder.<\/p>\n Lightning components can be added to a custom lightning page, record page as a quick action or a standalone app.<\/p>\n Creating and Editing Lightning Components<\/h2>\n Let\u2019s begin writing some code and create awesome components for our org.<\/p>\n To write the code we need to open the IDE, which can be accessed by either clicking your name (in Classic) or the gear icon in the LEX.<\/p>\n Fig 2.2: Developer Console link<\/p>\n Fig 2.3: Developer Console Interface<\/p>\n Create Lightning Components in the Developer Console<\/h2>\n To create a Lightning Component in the developer console follow the below instruction:-<\/p>\n \n Click on file and then hover over the new menu and then click on Lightning Components, this will open another dialogue box as shown below.<\/li>\n<\/ol>\n Fig 2.4: Lightning Bundle<\/p>\n \n Give it the name helloWorld and click on submit button.<\/li>\n This will open helloWorld component bundle and helloWorld.cmp as tabs. By default it provides us with opening and closing tag of aura:component, for this section just type <p> Hello Salesforce Lightning <\/p><\/li>\n<\/ol>\n Fig 2.5: HelloWorld Component<\/p>\n We have created our first component, now how to view this component, it is not as simple as Visualforce Page. To view Lightning component we first need to put in a container app. Let us make a simple container app for our helloWorld Component.<\/p>\n For creating the App follow the below instruction:<\/p>\n \n Click on file and then hover over the new menu and then click on Lightning Application, this will open another dialogue box which is the\u00a0New Lightning Bundlepanel, enter the name of our container app \u201charnessApp\u201d for the app name, and click\u00a0Submit you will have something as shown<\/li>\n<\/ol>\n Fig 2.6: The container App<\/p>\n \n This app will have <aura:application> tag written by default, just type <C:helloWorld\/> inside these tags and click on save. The difference between a Lightning App and component is visible on the right side panel. In App there is a preview button and in the component there is no preview button.<\/li>\n<\/ol>\n So here you see how we created a component and then hosted it inside a Standalone Lightning App. So you must be wondering that, what a component is. So without a further adieu let\u2019s dive deep into the component.<\/p>\n What Is a Component?<\/h2>\n A Component is a bundle which contains set files, written and wired in such a way that they accomplish a common business goal .They are coherent yet loosely coupled set of code and form the basic building block of Lightning Component Framework. It encapsulates a modular and reusable piece of UI and can range from single line of text to entire application. Let\u2019s discuss about the component\u2019s mark up next. Component resource has a .cmp suffix. Below is an example of the component mark up.<\/p>\n <aura:component><\/p>\n Hello, world!<\/p>\n <\/aura:component><\/p>\n This is as simple as a component can be in our helloWorld.cmp<\/p>\n Component Naming Rules<\/h2>\n A component name must follow these naming rules:<\/p>\n \n Must begin with a letter, contain only alphanumeric or underscore characters, it must be unique in the namespace<\/li>\n Can\u2019t include whitespace, end with an underscore or contain two consecutive underscores.<\/li>\n<\/ul>\n Component Bundles<\/strong><\/h2>\n A component bundle consists of files and resources grouped together to achieve a common goal, it contains the following resources:-<\/p>\n \n Component<\/strong>: resource name has suffix of .cmp and it contains all the mark up of the component. Each bundle can have only one component.<\/li>\n CSS<\/strong>: resource name has suffix of .css and it contains all the styling of the component<\/li>\n Controller<\/strong>: resource name has suffix of .js and it consists of client-side controller methods to handle the events.<\/li>\n Design<\/strong>: resource name has .design as the suffix and it is required for a component to be used in lightning app builder, lightning pages or community builder<\/li>\n Documentation<\/strong>: resource has .auradoc as suffix and is a description of the component, sample code and one or more component reference.<\/li>\n Renderer<\/strong>: resource name has .js as a suffix and is used to override client-side renderer for a component.<\/li>\n Helper<\/strong>: resource has .js as its suffix and it contains JavaScript Functions that can be called from any JavaScript code in the components bundle.<\/li>\n SVG<\/strong> File: resource has .svg as the file extension and it contains custom icon resource for the components used in lightning App Builder or community builder.<\/li>\n<\/ul>\n Next we will start making our component a little bit more complex by using attribute and expressions.<\/p>\n Also Have a look at the below resources:<\/p>\n \n Best Salesforce Interview Questions book with Apex and Visualforce concept explained<\/a><\/li>\n<\/ol>\n Also Have a look at the below learning resources:<\/p>\n \n SOQL (Salesforce Object Query Language)<\/a><\/li>\n \n Apex Trigger Best Practices and the Trigger Framework<\/a><\/p>\n<\/li>\n \n Salesforce Interview Question and Answers Part 2<\/a><\/p>\n<\/li>\n \n Salesforce Interview Questions on Test Class<\/a><\/p>\n<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":" Salesforce Lightning Tutorial: Lightning Component basics Chapter 1: Prerequisite for Lightning Component Development My Domain Before we begin to deep dive into the development of Lightning Component we need few things to be enabled in our Developer Edition Org. First thing is to enable My Domain in the DE org. Enabling My Domain and activating … Continue reading Salesforce Lightning Tutorial: Lightning Component basics<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":1169,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[107],"tags":[40,79,110,61,74,45,75,38,83,42,82,55,109,108,51,111,52],"_links":{"self":[{"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/posts\/1159"}],"collection":[{"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/comments?post=1159"}],"version-history":[{"count":3,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/posts\/1159\/revisions"}],"predecessor-version":[{"id":2193,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/posts\/1159\/revisions\/2193"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/media\/1169"}],"wp:attachment":[{"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/media?parent=1159"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/categories?post=1159"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/salesforcenextgen.com\/wp-json\/wp\/v2\/tags?post=1159"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}