Lightning Components Developer Guide

What is the Lightning Component Framework?
Quick Start
Before You Begin
Create a Standalone Lightning App
Optional: Install the Expense Tracker App
Create an Expense Object
Step 1: Create A Static Mockup
Step 2: Create A Component for User Input
Step 3: Load the Expense Data
Step 4: Create a Nested Component
Step 5: Enable Input for New Expenses
Step 6: Make the App Interactive With Events
Summary
Create a Component for Salesforce1 and Lightning Experience
Creating Components
Using Components
Communicating with Events
Creating Apps
Debugging
Fixing Performance Warnings
Reference
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Step 6: Make the App Interactive With Events

Events add an interactive layer to your app by enabling you to share data between components. When the checkbox is checked or unchecked in the expense list view, you want to fire an event that updates both the view and records based on the relevant component data.
This flowchart shows the data flow in the app when a data change is captured by the selecting and deselecting of a checkbox on the expenseList component. When the Reimbursed? checkbox is selected or deselected, this browser click event fires the component event you’re creating here. This event communicates the expense object to the handler component, and its controller calls the Apex controller method to update the relevant expense record, after which the response is ignored by the client since we won’t be handling this server response here.Clicking the checkbox on an expense triggers an event that updates the record.

Let’s start by creating the event and its handler before firing it and handling the event in the parent component.

  1. Click File | New | Lightning Event.
  2. Enter updateExpenseItem in the New Event window. This creates a new event, updateExpenseItem.evt.
  3. In updateExpenseItem.evt, enter this code.

    The attribute you’re defining in the event is passed from the firing component to the handlers.

    1<aura:event type="COMPONENT">
2    <!-- If you’re using a namespace, use myNamespace.Expense__c instead. -->
3    <aura:attribute name="expense" type="Expense__c"/>
4</aura:event>
    The framework has two types of events: component events and application events.

    Always try to use a component event instead of an application event, if possible. Component events can only be handled by components above them in the containment hierarchy so their usage is more localized to the components that need to know about them. Application events are best used for something that should be handled at the application level, such as navigating to a specific record. Application events allow communication between components that are in separate parts of the application and have no direct containment relationship.

    Note

    We’ll use a component event. Recall that expenseList.cmp contains the Reimbursed? checkbox.

  4. Update expenseList.cmp to register that it fires the event. Add this tag after the <aura:attribute> tag. 
    1<aura:registerEvent name="updateExpense" type="c:updateExpenseItem"/>

    The Reimbursed? checkbox is wired up to a client-side controller action, denoted by change="{!c.update}". You’ll set up the update action next.

  5. In the expenseList sidebar, click CONTROLLER. This creates a new resource, expenseListController.js. Enter this code. 
    1({
2    update: function(component, evt, helper) {
3      var expense = component.get("v.expense");
4      // Note that updateExpense matches the name attribute in <aura:registerEvent>
5      var updateEvent = component.getEvent("updateExpense");
6      updateEvent.setParams({ "expense": expense }).fire();
7    }
8})

    When the checkbox is checked or unchecked, the update action runs, setting the reimbursed parameter value to true or false. The updateExpenseItem.evt event is fired with the updated expense object .

  6. In the handler component, form.cmp, add this handler code before the <aura:attribute> tags. 
    1<aura:handler name="updateExpense" event="c:updateExpenseItem" action="{!c.updateEvent}" />

    This event handler runs the updateEvent action when the component event you created is fired. The <aura:handler> tag uses the same value of the name attribute, updateExpense, from the <aura:registerEvent> tag in c:expenseList

  7. Wire up the updateEvent action to handle the event. In formController.js, enter this code after the createExpense controller action. 
    1updateEvent : function(component, event, helper) {
2    helper.upsertExpense(component, event.getParam("expense"));
3}

    This action calls a helper function and passes in event.getParam("expense"), which contains the expense object with its parameters and values in this format: { Name : "Lunch" , Client__c : "ABC Co." , Reimbursed__c : true , CreatedDate : "2014-08-12T20:53:09.000Z" , Amount__c : 20}.

  8. Save your changes and reload your browser.
  9. Click the Reimbursed? checkbox for one of the records.
    Note that the background color for the record changes. When you change the reimbursed status on the view, the update event is fired, handled by the parent component, which then updates the expense record by running the server-side controller action saveExpense.
That’s it! You have successfully added a layer of interaction in your expense tracker app using a component event.
The app you just created is currently accessible as a standalone app by accessing https://<myDomain>.lightning.force.com/<namespace>/expenseTracker.app, where <myDomain> is the name of your custom Salesforce domain. To make it accessible in Salesforce1, see Add Lightning Components as Custom Tabs in Salesforce1. To package and distribute your app on AppExchange, see Distributing Applications and Components.