Salesforce Sandbox

Product Education &

Recommendations

John Vogt
Senior Product Manager
Salesforce Platform
Safe Harbor
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
intellectual property and other litigation, risks associated with 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-Q for the most recent fiscal quarter ended July 31, 2012. This
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.
Agenda

• Salesforce Product Line

• Sandbox Value Proposition
• Sandbox Use Cases
• Best Practices for Salesforce Customization
• Team Setup
• Code Management
• Release Planning
• Sandbox Management
Sandbox Products
Sandbox Product Line – Winter ‘14

Partial
Developer Developer Pro Sandbox Full

Refresh Interval 1 Day 1 Day 5 Days 29 Days

Includes Setup
Yes Yes Yes Yes
Configuration
Copies Data
No No Yes Yes
Records
Sandbox Templates/ Yes & Yes (10,000 Yes & No (Full
No & No No & No
Sampling records/object) Data / Object)

Bundled Developer
None 5 10 15
Sandboxes

1GB 5GB Match

Sandbox Size 200MB
(~500K records) (2.5M records) production
Sandbox Templates

Feature Breakdown
• User defined template that specifies the data that will be copied
• Applied to the sandbox during the create/refresh process
• Can be applied to more than one sandbox

Sandbox Copy Details

• Full Sandbox – when applied ALL data for the objects selected will be
copied
• Partial Data Sandbox – when applied, a SAMPLE of data for the
objects selected will be copied
Data Sampling

10K
records

nt ct ity e A B
ou ta n as t t
c n tu C jec jec
Ac Co or b b
pp O O
O t om t om
us us
C C

Sample up to 10k records per object

Random samples reflect true testing needs to find edge case issues
Sandbox Value Prop
The Cloud Computing Value

• Tape Backup
• Hot Backup on Site
• Disaster Recovery located in separate Data Center
• Infrastructure Maintenance
• Hardware repair/replacement
• Dedicated 24/7 Global Support
• Automatic Upgrades
• Same hardware Stack – Sandbox Infrastructure = Production
• Network, Security, App Tier, Data Tier
Sandbox Value

• All features, functionality, user licenses and setup configuration

included in each sandbox product
• Full sandbox additionally includes all of the object data
• Refresh action allows you to create a new sandbox while continuing
your work in the current sandbox.
• Preview of Future Release
• New features and functionality
• Instant provisioning of new features
• No installation required
• Isolated Test Infrastructure
Sandbox Use Cases
Sandbox Use Cases

Use Case Developer Developer Pro Partial Data Full

Development Good Fit Good Fit Okay Not a Good Fit

QA Good Fit Good Fit Good Fit Not a Good Fit

Integration Test Not a Good Fit Not a Good Fit Good Fit Good Fit

Batch Data Test Not a Good Fit Not a Good Fit Good Fit Good Fit

Training Not a Good Fit Not a Good Fit Good Fit Good Fit

UAT Not a Good Fit Not a Good Fit Good Fit Good Fit
Perf/Load Test Not a Good Fit Not a Good Fit Not a Good Fit Good Fit
Staging Not a Good Fit Not a Good Fit Not a Good Fit Good Fit
Use Case Understanding

• Full Sandbox is not Agile

• Development use cases must have agile products
• A sample data set is suitable for the majority of use
cases
• A full data set is only needed for Staging, Performance
and Scalability testing
Best Practices
Team Setup

• Develop in Isolation
• Not in production
• Not in same dev org as their peers
• Teamwork
• Synchronize with peers to leverage each others work
• Stable checkpoints to hand-off between functions (e.g. QA)
• Integrate when complete
• Integrate with peers when development and unit test complete
• Integrate with current production for testing and approvals
Code Management
• Have a Change/Release Management Process!
• No change management process out of the box

• Integrate with Source Control

• Manage multiple code lines
• You can get more out of your agile environments
• Automate your deployments
• Force.com Migration Tool (Ant Tool)
• Consider Continuous Build Systems
Release Planning
• Understand our release schedules
• 3 Major Releases
• Participate in the Preview Window
• Follow Trust

• Are you conservative or aggressive?

• Have a documented Project Plan
• Requirements/User Stories
• Test Plans
• Release Schedule

• A Release Train for each Project

Sandbox Management
• Refresh after Every Release
• Refresh before deploying code line
• Have strict User Governance
• Restrict admin capabilities in the production org to a small group that also
manage the release
• Limit user access in developer sandbox (Developers, Testers Only)
• Create a Post Refresh Run-List
• Include this as part of your change/release management process
• Document the following:
• Data masking needs
• User/Profile Modifications
• Test Data loads
• Turn off scheduled jobs
• Manage Outbound Email