The document presents a session on integrating REST APIs with Lightning Components and Salesforce1, detailing components' architecture, usage, and deployment. It highlights the use of Apex classes for making server-side REST callouts and includes several demos showcasing key features and functionalities. Additionally, the presentation addresses risks associated with forward-looking statements and emphasizes the need for up-to-date information on Salesforce's offerings.

1. Easy REST Integrations with Lightning
Components and Salesforce1
​ Luciano Stragà
​ Salesforce Certified DEV
​ lucianostraga@icloud.com
​ @StragaLuciano

2. Luciano Stragà
Salesforce Certified DEV – Altergaia LLC

3. ​ Safe harbor statement under the Private Securities Litigation Reform Act of 1995:
​ This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties
materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed
or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-
looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any
statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new,
planned, or upgraded services or technology developments and customer contracts or use of our services.
​ The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new
functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our
operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any
litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our
relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our
service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger
enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our
annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter.
These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section
of our Web site.
​ Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available
and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features
that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
Safe Harbor

4. Session Agenda
q Topic Presentation - Easy REST Integrations with Lightning Components and Salesforce1
• Concepts and Use Case
q Lightning Components Overview – Basics & Key Features
• Demo: Lightning Component Example
q Lightning Components Logic – Javascript on the Client and Apex on the Server
• Demo: Enabling an Apex class to make a REST callout from a Lightning Component.
• Demo: Javascript controller for interaction with the Apex Class.
q Deploying in Salesforce1
• Demo: How to deploy a Lightning Component in SF1 application.
q Q&A

5. Topic Presentation
Concepts and Use Case Scenario

6. and keep it INTEGRATED!

7. Lightning Components Salesforce1 External REST API
CONSUMINGINSIDE
Use Case Scenario
​ Elements Involved

8. inspirationalapi.herokuapp.co
m

9. Lightning
Components ​ Overview

10. What are Lightning Components?
​ Overview and Key Features
§ Part of the Salesforce Lightning framework
§ Are Self-contained and reusable functional units of an app
§ Reusable section of the UI
§ Rendered as HTML DOM elements in browsers
§ Exposes their Definitions
§ Attributes passing
§ Has a Encapsulated Implementation
§ Component Bundle
§ HTML,CSS & Javascript
§ Communicate with Events

11. Where you can use Lightning Components?
§ Standalone Applications
§ Independent of SF1
§ Lightning Components for Salesforce1
§ Individually
§ In combination with others by Lightning App Builder
§ Customize Salesforce1 with Lightning Extensions (Pilot)
§ Override SF1 tabs and fields with your own component
​ Components Usage

12. ​ APEX
​ On the Server Side
​ JAVASCRIPT
​ On the Client Side
Lightning Components Architecture
​ Component Behavior

13. Use Case Scenario
​ Interaction Diagram
Lightning
Component
JavaScript
Controller
Apex
Controller
External
Rest API

14. Demo: Lightning Component Example

15. § @AuraEnabled Annotation
§ Declares the public method to be call from a Javascript Controller
§ Salesforce REST APIs must be consumed ONLY from an Apex Class, and not from JS the
controller.
§ Making AJAX calls are not possible due Lightning Components and Salesforce REST server are in
different domains.
§ Example:
For REST callouts
Apex On the Server Side

16. § Specifies the URL of a callout endpoint and its required authentication parameters in one
definition.
§ In Setup | Security Controls | Named Credentials.
§ Supports basic password authentication and OAuth 2.0.
§ Apex code usage sample:
Using Named Credentials
Apex On the Server Side

17. Demo: Enabling Apex class for making
REST callouts from Lighting
Components

18. § To make the Apex Class visible, ‘controller’ attribute has to be set with the name of the class.
§ component.get("c.myMethod”); for calling Apex Methods from controllers.
For Apex Interaction
Javascript On the Client Side

19. Demo: Javascript controller for
triggering REST Callouts by an Apex
Class

20. Deploying to Salesforce1
§ Implements=“force:hostabl
e”
§ This attribute has to be set in
the component so as to
enable it in Salesforce1
§ Lightning Components
Tabs
§ Mobile Administration
§ For setting new Lightning
Component tabs
​ How to place Lightning Components in SF1

21. Demo: Deploying a Lightning
Component into Salesforce1 to make
REST callouts

22. Questions &
Answers
​ Q&A

23. Session Resources
​ Inspirational Rest API:
inspirationalapi.herokuapp.com
​ Project on GitHub: github.com/lucianostraga/
dreamforce15
​ Trailhead: developer.salesforce.com/trailhead
​ Twitter: @stragaLuciano
​ LinkedIn: Luciano Straga

24. Thank you