This document contains a forward-looking statement regarding potential risks and uncertainties in salesforce.com's financial results. It notes that actual results may differ from projections due to various risks including issues with new products, services, business models, mergers and acquisitions. The statement also notes that unreleased features mentioned may not be delivered on time or at all, and customers should only make purchase decisions based on currently available features. The document encourages reviewing salesforce.com's SEC filings for more details on potential risk factors.

1. August 10, 2017
Get Started with Salesforce DX

2. Forward-Looking Statement
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.

3. Go Social!
Salesforce Developers
Salesforce Developers
Salesforce Developers
The video will be posted to YouTube & the
webinar recap page (same URL as registration).This webinar is being recorded!
@salesforcedevs / #SalesforceDX

4. ▪ Don’t wait until the end to ask your question!
– Technical support will answer questions starting now.
▪ Respect Q&A etiquette
– Please don’t repeat questions. The support team is working
their way down the queue.
▪ Stick around for live Q&A at the end
– Speakers will tackle more questions at the end, time-
allowing.
▪ Head to Developer Forums
– More questions? Visit developer.salesforce.com/forums
Have Questions?

5. Agenda
1. Salesforce DX Overview
2. Demos
3. Adopting Salesforce DX
4. Q & A

6. Environments
are easily
created and
disposable
Metadata
and code is
modular
Development is
based on open
standards and
extensibility
Everything is
driven from
source code
Development is
organized
around team
collaboration
Processes and
tools facilitate
continuous
delivery
Flexible
packaging
supports agile
distribution
model
Building a world-class software factory
Principles of Modern Software Delivery

7. Source-driven development
Greater agility to test out features with confidence
Team collaboration
Increased dev productivity, faster time to market
Continuous integration and delivery
Higher quality code, more automation
Open and prescriptive
Build with the tools and processes you know and love;
bring together Lightning, Force.com, and Heroku
Team collaboration
Introducing Salesforce DX

8. Source-driven
Development
Ephemeral
Scratch Orgs
Enhanced
Salesforce CLI
IDEs, Text Editors,
Language Services
Continuous
Integration
Packaging 2
(Pilot)
Continuous
Delivery
Partial/Full
Sandboxes
Empowering developers
Transforming Salesforce Development

9. Plan
Code
BuildTest
Release
CLI for integration
with 3rd party editors
Scratch orgs for devs,
built off of source
Continuous Delivery/
build automation
Continuous integration
with test automation
Sandboxes for
performance testing,
UAT, staging
Packaging to streamline
delivery to prod
VCS as the
source of truth
IDEs, Text Editors,
Language Services
Across Application Lifecycle Management
Improve the Developer Experience

10. DEMOS

11. ▪ CLI
Perform common Force.com development tasks
▪ Continuous integration and delivery
Team development with scratch orgs built from source empower more automation, higher
quality code
▪ Source driven development
Scratch orgs and source change tracking provide greater agility to test out features with
confidence
▪ The Whole Enchilada
Leverage throughout entire application lifecycle
Not just “all or nothing”
Adopting Salesforce DX

12. Organizing the “happy soup” into projects
Modularizing your code

13. Organizing the “happy soup” into projects
Project Development
A group of related code and customizations
Can be tested independently from other components in your org
Able to be released independently
Source components can only live in one project at a time

14. Don’t export entire org as a single project
Modularize
Be careful with schema
Put shared schema in it’s own project
Watch for shared objects
Add to a common project
Running without CI
At a minimum include CI runs for each commit
Don’t export live data from production org
Create targeted data for functional testing
No integration testing
Plan for integration and UAT testing after deployment to sandboxes or production
Things we’ve learned don’t work
Anti-Patterns

15. Become a Salesforce DX Trailblazer
Four new badges for the Getting Started with Salesforce DX trail
Salesforce DX
Development Model
Git and Github Basics
*New Partner Module!
Continuous
Integration using
Salesforce DX
App Development
with Salesforce DX

16. Salesforce DX → Major Releases
Summer ’17
TrailheaDX
Winter ’18
Dreamforce
Spring ’18
Salesforce CLI Open Beta GA GA+1
Source Sync &
Change Tracking
Open Beta GA GA+1
Scratch Orgs Open Beta GA GA+1
IDEs, Text Editors, &
Language Services
Open Beta GA GA+1
Packaging 2 Closed Pilot Open Beta GA

17. Join the Salesforce DX Open Beta
Two easy ways to get started
Enable Dev Hub
in a Production or
Business Org
From Setup, search on
“Dev Hub” and then click
Enabled.
Get a Trial Org
with Dev Hub Enabled
30 day Free Trial
Sign Up at:
https://sfdc.co/DX-Trial-Org

18. August 17, 2017 | 10:00 a.m. PDT
Join us for next week’s webinar:
Adopting Salesforce DX
Register here: bit.ly/adoptingSFDXwebinar

19. Survey
Your feedback is crucial to the success
of our webinar programs. Please fill out the survey at the
end of the webinar. Thank you!

20. Q & A
Try Trailhead: trailhead.salesforce.com
Join the conversation: @salesforcedevs

21. Thank You