isv lightning webinar series - part 2 (december 8, 2015)

Building & Releasing Lightning Components for ISVsPart 2 of 3 in the ISV Lightning Webinar series

December 8, 2015

Cliff Armstrong & William Yeh, Salesforce Technical Evangelists

Meet your PresentersISV Technical Evangelist Team

Cliff ArmstrongSenior ISV Technical Evangelist

Salesforce

William YehISV Technical Evangelist

Salesforce

Safe HarborSafe 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.

Delivered through the Partner Community

ISV Lightning Webinar Series

We are here

• Recap from Webinar #1 - Defining Your Lighting Strategy

• Demo Component Creation and Usage

• Tips for Building Lightning Components

• Distributing Lightning Components

• Security Considerations

• What’s Next for Lightning Components

• Resources

• Q&A (please post questions via Webinar chat)

What we plan to cover today

A New User Interface: Lightning ExperienceModern, interactive, responsive experience across all devices

A New Approach: ComponentsReusable Building Blocks

Webinar 1 - Defining Your Lightning Strategy

1. Self assessmenta. Tech Leader/Fast Follower/Left Behind? b. Technical Capabilitiesc. Manpower

2. Your App’s Environmenta. What is your use case? b. What do your customers demand?c. Who are your customers (where are they on curve)?d. Competitors?e. Market Segment

3. Your Visiona. If your app could be anything, what would it be? b. Are you gunning for the Dreamforce Keynote?

4. Salesforce Technologya. Are there currently any blockers?b. Are they on our Roadmap?

Slides and Recording of Webinar 1 (requires Partner Community login)

Questions that ISVs need to ask (and answer)

Let’s Recap - Your Custom UX Options

● Proven model

● Easy to implement tags

● Template driven web pages

● Email Templates

● Not going anywhere

● Enables highly interactive UX

● Leverage popular JS Libraries

● Shorter Learning Curve

● Highly interactive UX

● Aligns with SFDC UI strategy

● Tightly integrated into the

container

● Built on metadata

● Highly interactive UX

● Aligns with SFDC UI strategy

● Tightly integrated into the

container

● Built on metadata

Visualforce Visualforce + JS Lightning Components Visualforce + LC

Choose the right tool for the job

Want more, see: User Interface Design Considerations Trailhead

Where can you use them?Lightning Components

* Dependent on Lightning App Builder, GA Mid-2016** In Pilot, GA Mid-2016 (safe harbor)

Salesforce1 Mobile

Lightning Component Tab

Lightning Component

Classic

VisualforcePage

Lightning Component

LightningExperience

VisualforcePage

Lightning Component

LightningExperience

RecordHome*

Lightning Component

External Website

Lightning Component

(Lightning Out**)

Demo 2Integrating Lightning Components Now and in the Future

Demo 1Building and Packaging a Component

Two Demos

Demo

Tips & Best Practices for Building Lightning Components

Comma Delimited Lists are supported for Implements (community builder, app builder, etc…)<aura:component implements="flexipage:availableForAllPageTypes, forceCommunity:availableForAllPageTypes">

Salesforce Lightning Design System SLDS is highly recommended but not a requirement

Build your Component to behave properly without contextRespond gracefully if Component is referenced in unexpected scenario

Nesting components allows you to define different defaults for different usage patternsFor example, if you want Component to behave differently in Community

Best Practices/Tips

Your customers and other partners may want to integrate with your ComponentsMake it easy for them by providing documentation

● lightning.force.com/auradocs/reference.app?sdtd=1● Lets you see all the components you have access to● Source is protected for components in Managed Packages

All Components are Automatically Documented

Your Components are Showing

Set limits on your Int and String Design Attributes if possible<design:attribute name=”limitRows” min=”1” max=”12” label=”Number of Items” />

<design:attribute name="Name" datasource="value1,value2,value3" />

Improves User Experience

Recommended by our Security Team

Leverage Built-in Validation

• Design for access=“GLOBAL”

• Anything meant to be accessed by others should be marked as access=“GLOBAL”

• Components, Apps, Attributes, Interfaces, and Events

• Warnings in 198/Winter ‘16 when debug is enabled (post-Dreamforce patch)

• Components published to the AppExchange for Components (.design files are not enough!)

• Components used within other namespaces

• Components used in Visualforce

Not to be confused with Global Apex classes

Global Access is Good

<aura:component controller="MyController" implements="flexipage:availableForAllPageTypes, force:hasRecordId">

<aura:attribute name="Account" type="Account"/> <ltng:require styles="/resource/bootstrap"/> <div class="bootstrap-sf1"> <div class="container"> <ui:outputText class="form-control" aura:id="recid" value="{!v.recordId}"/> </div> </div></aura:component>

Let your component know which Record page it’s on (if it’s on one)

Lightning Components Built for Record Home

public class AccountsListController

{

@AuraEnabled

@RemoteAction

public static List<Account> GetAccounts()

{

return [SELECT id, Name, Industry, CreatedDate

FROM Account

ORDER BY createdDate DESC];

}

}

Work with both Lightning and Javascript remoting

Reuse your Apex Controllers

My Domain Required for Lightning Components

● In order to run Lightning Components in an org the My Domain feature must be enabled

● Package with components will install in org that doesn’t have My Domain

● May require some work by customers

Distributing Lightning Components

Two Options for Distributing Lightning Components

● Add to your existing application● No different from adding a new custom object or

Visualforce page● Create a new package● You may choose to include a Lightning App that

contains the Component

● Distribute as a Standalone Component

ISVs Distributing using Managed Package

1 2

Use one--time pricing for components that are limited in scope and do not require significant maintenance

over time

Use annual pricing for more complex components that will need to be supported over time

Checkout is required, Simple to Buy is the ThemeCharging for Components

How should you charge for Components?

How should you license your Component?

Does Checkout Support all these variations?

One-Time Charge Annual Charge

Site-wide licensing recommended

Yes!

● Built in credit card processing via Stripe

● Automatically updates licenses in your License

Management Application (LMA) upon purchase

● Pricing flexibility via discount codes

● Available for ISVforce only

Checkout Overview

See the ISVforce Guide for more information on Checkout

Security for Lightning Components

Lightning Components Usher in New Era of EqualityBuild in Security from the Start

Salesforce Developed UI Partner Developed UI

Classic salesforce.com visual.force.com

Lightning Experience lightning.force.com

● With Sharing on all classes that access sObjects

● Rigorous CRUD/FLS enforcement in Apex

○ No automatic enforcement as in VisualForce

○ CRUD/FLS cannot be enforced on the client

● Only invoke DML operations with user interaction

Protect Data Server-Side

● Don’t modify the DOM outside your Controller

● Protect against malicious scripts○ No built-in HTML or JS encode protection...yet

○ v.value = "javascript:alert(1)" Not safe

○ <img src='foo' onerror="{!v.value}"> Not safe

○ <a href="{!v.value}"> Not safe

○ <a href="{!'/' + v.value}"> Safe

See full list of security best pratices here: http://bit.ly/LC-Security

Follow Best Practices Client-Side

A lonely component in a test org isn’t easy to test

Create an app using the Lightning App Builder and provide directions in submission notes

Provide sample data and basic instructions for component

Include Checkmarx report for all submissions

Include ZAP report if your Component interacts with external services - third party end point only

Submission Process for Standalone Components – What do you need to Submit?Security Review

1 2 3

Future of Lightning Components

Developer Productivity – ComponentsLightning Components – The Future

Chevrons

Tabs

Activity Timeline

Related List

Highlights

TreeChatter Feed

Grid

What’s Coming for Lightning ComponentsLightning Components● Support for unauthenticated users ● Lightning Extensions● More Robust Licensing● Lightning Out

Lightning Design System● Lightning Design System is part of Core - Global CSS● Lightning Design System Tokens

Lightning App Builder● GA for Desktop ● Customize Additional Page Types on multiple devices● Custom Page Templates● Integrated Component Exchange● Branding and Visual customization

Wrap-up

NowToday-Spring ‘16

● Leverage Trailhead and Training to become proficient with Lightning Components

● Identify features on your roadmap that can be delivered with a Lightning Component for Visualforce

● Identify new potential products for the Lightning Exchange

Short TermSpring ‘16 - Summer ‘16

● Incorporate Lightning Components into new and existing Visualforce pages

● Build products for the Lightning Exchange

● Start to think Lightning First for your app

Long TermPost Summer ‘16● Deliver Lightning Components

day one of App Builder GA● Align your roadmap with

Lightning● Re-imagine use cases to take

advantage of new user experience

● Don’t miss opportunity to establish your position as an innovator

Lightning Component StrategyGet Ready to Meet Customer Demand for Lightning Components

Resources

• Lightning Component Developer Guide

• Lightning Design System

• Trailhead - Lightning Experience

• Check Out - App Vendors Checkout

• Awesome DF15 Session on Building Lightning Components

• Partner Community groups:

•Lightning Ready Certification for ISVs

•Lightning and Components

Lightning Resources

Thank You