Salesforce DX Update for ISVs - What ISV Partners should know about Salesforce DX right now. Vivek M. Chawla, Senior ISV Technical Evangelist at Salesforce, answers the most common questions from ISV Partners about Salesforce DX, including... - What is going GA / BETA / PILOT in Winter ‘18 - What ISVs should know about Salesforce DX - What ISVs can do to learn more about Salesforce DX For more information about Salesforce DX, check out the following Chatter groups in the Salesforce Success Community. Salesforce DX - http://bit.ly/sfdx-group Packaging 2 Beta - http://bit.ly/pkg2-beta-group

1. Salesforce DX Update for ISVs
What ISV partners should know about Salesforce DX right now
What is going GA / BETA / PILOT in Winter ‘18
What ISVs should know about Salesforce DX
What ISVs can do to learn more about Salesforce DX
Vivek M. Chawla
Senior ISV Technical Evangelist
October 15, 2017

2. Forward-Looking Statements
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. Salesforce DX Release Plan for Winter ‘18
What’s going GA, entering BETA, or beginning a PILOT?

4. Salesforce DX in Winter ’18
● Developer Hub (GA)
● Scratch Orgs (GA)
● Salesforce CLI (GA)
● VS Code Plugins (GA)
● Feature Management (GA)
● Packaging 2 (Beta)
● Dev Controlled Pkgs (Pilot)

5. Common questions that ISV Partners have
about Salesforce DX
What every ISV should know about Salesforce DX

6. Will it cost anything for ISV Partners to use
Salesforce DX?
No, there is no initial cost to ISV Partners for using Salesforce DX.
All ISV Partners will get a baseline entitlement of Active Scratch Orgs and daily
activations, based on program tier.
Registered/Silver 40/80 (Active/Daily)
Gold/Platinum/Strategic 150/300 (Active/Daily)
If an ISV Partner requires more scratch orgs they will be available for purchase.

7. How will ISV Partner developers get access to
Scratch Orgs?
To create Scratch Orgs, developers must have access to a “Developer
Hub” org, a feature that will only be available in EE and UE orgs.
The Developer Hub feature will be made available inside all ISV Partner
Business Orgs. ISV developers will need user accounts in the PBO in order to
create and manage Scratch Orgs. (see the next slide for more details)
All ISV Partners will have access to exactly one Developer Hub in their PBO.
Developer Hub will not be available in DE orgs or any trial orgs that are spun up
from Environment Hub.

8. How will ISV Partners add developer users to
their PBO so they can access the Dev Hub?
To support the creation of developer users in a Partner Business Org, each
PBO will be provisioned with 100 free, limited-access licenses.
Since many ISVs only have two user licenses in their PBO, we’ve created a new
limited-access, no-cost license type called “Salesforce Limited Access - Free”.
ISVs can create logins for their developers using this new license type.
This license will allow developer users to create and manage scratch orgs via the
Salesforce CLI. Users with this license will not be able to access any CRM
objects (like Leads and Opportunities).

9. Does an ISV Partner need to do anything (like
open a case) to make the Dev Hub available
for activation in their PBO?
No. ISV Partners won’t need to do anything to make the Dev Hub available
in their PBO.
The Dev Hub feature, baseline Scratch Org entitlements, and the 100 “Salesforce
Limited Access - Free” licenses will be automatically added to all Partner
Business Orgs (PBOs) during the week of October 16th.
Once provisioning to PBOs is complete, we will release a Partner Alert with
instructions on how to activate the Dev Hub and share best practices for creating
developer users with the “Salesforce Limited Access - Free” license type.

10. Why should ISV Partners with well established,
non-Salesforce DX developer workflows care
about using Scratch Orgs?
One of the best features of Salesforce DX for ISVs is the ability to assign an
existing package’s global namespace to a Scratch Org.
With Scratch Orgs, multiple developers can work on individual branches of a
package as if they were building directly in the packaging org.
The disposable nature of Scratch Orgs also makes them ideal for development
workflows that utilize Continuous Integration/Delivery. Instead of spending time
“cleaning” an org before deployment, just spin up a fresh Scratch Org when you
need it.

11. How can ISV Partners get started with
Packaging 2?
The Packaging 2 (Beta) can be activated in any Winter ‘18 Developer Hub.
In Setup, go to the Dev Hub activation page to enable the Packaging 2 (Beta).
Please note that this feature can not be disabled once it has been enabled.
Join the “Packaging 2 (Beta)” Chatter group- http://bit.ly/pkg2-beta-group
During the open beta, the “Packaging 2 (Beta)” Chatter group in the Success
Community will be the best resource for anyone test driving Packaging 2. In
particular, look for several “assignments” that help Partners work through the
most common use cases for Packaging 2.

12. When should ISV Partners invest serious time
and effort with Packaging 2?
ISV Partners should begin learning about Packaging 2 as soon as possible.
Packaging 2 is closely aligned with the DX framework and will allow greater
control over how the package is constructed and how to handle extensions and
upgrade paths.
Being hands-on with Packaging 2 during the beta period gives ISV Partners the
chance to understand new functionality and design patterns while providing
feedback that may shape the final GA product.
Having said that, Packaging 2 is not a GA feature. Partners should hold off
converting existing packages over to Packaging 2 until it reaches GA status.

13. What is the ideal strategy for adopting
Salesforce DX?
Adopting SFDX isn’t an all-or-nothing proposition. Here are some options.
Salesforce 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

14. Salesforce DX Learning Path for ISVs

15. How can ISV Partners learn more
about Salesforce DX?
Trailhead
bit.ly/sfdx-trail
DX for ISVs Playlist
bit.ly/sfdx-for-isvs
Packaging 2 Beta
bit.ly/pkg2-beta-group
WATCH these videos... DO this Trail... TRY Packaging 2...
YouTube videos that show how to get started
with Salesforce DX, the Salesforce CLI and
how to adopt key features.
Take the Salesforce DX Trail - four modules
that dive into working with Version Control,
CI/CD, the CLI and tips for getting started.
✮ Extra credit ✮
Get an early start with Packaging 2 and you’ll
be in a great place to adopt once it goes GA!