Major Releases, Minor Releases. Developers, Testers. Refreshes and Previews. How do you manage all of these various demands in your Salesforce environments and sandboxes? Join Farhan Tahir, Platform Product Manager, as he shares details on how to tackle these problems around sandbox management through the use of both processes and tools. As well as insight on roadmap features to make development efficient and agile by automating with Salesforce Sandboxes. Watch the video now: https://www.youtube.com/watch?v=FMH77436I2o

1. Sandbox: The Future of App Development
​ Farhan Tahir
​ Director Product Management, App Cloud
​ ftahir@salesforce.com
​ @tahir_farhan
​

2. ​ 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

3. ​ - Introduction to Sandbox
​ - Customer Story by Barnet Associates
​ - Roadmap!
​ Sandstorm
​ Sandbox APIs
​ Increased # of Dev Copies
​ Additional Refreshes
​ Post Copy Scripting
​ Others
Agenda

4. ​ Copy of production on same infrastructure
​ Development tools to build and customize
​ Change Sets and Templates for faster
​ deployment
​ Metadata APIs and IDE for faster development
Sandbox is a key part of building in the cloud

5. Sandbox Product Line
Developer Developer Pro Partial Copy Full
Refresh Interval 1 Day 1 Day 5 Days 29 Days
Includes Setup
Configuration
Yes Yes Yes Yes
Copies Data Records No No Yes Yes
Sandbox Templates/
Sampling
No & No No & No
Yes & Yes (10,000
records/object)
Yes & No (Full Data
Copy)
Sandbox Size
200MB Data
200MB File
1GB (~500K records)
1GB File
5GB (~2.5M records)
File Storage
Dependent on Sample
Match Production for
Data and File

6. Pam Barnet
VP, App Development & Software Adoption, Barnet
Associates
pam@barnetassociates.com
Evan Barnet
President & CEO, Barnet Associates
evan@barnetassociates.com

7. The Barnet’s are loving Salesforce
2002 2005 2014
Customer Partner
Developer
3rd place “Tic Tac Close”
Summer Hack-a-Thon

8. Salesforce app development over the past 6 months
Customer Onboarding Ticket Scan Application Customer Community
Event Planning Opportunity Transfer Tracking Automate Sales

9. Custom app
Odata API
Lightning Connect
APEX Controllers
Visualforce Pages
S1 mobile
Customer Communities is a success!
6 weeks to develop, 1 day to deploy, 2 weeks user adoption
Governance
Change Sets
Unit Testing for APEX Code
Validation
Deployment
Communicate

10. 1. ALWAYS test in Sandbox FIRST!
2. URL for Sandbox login is test.salesforce.com
3. Name Sandboxes to indicate the type: MyCoFULL, MyCoPartial, or MyCoDev01
4. Sandbox user names are appended with the name of the sandbox: PBarnet@MyCo.com.MyCoFULL
5. Change password at the same time as production
6. Keep track of security tokens for production and all sandboxes for ease of data loading
7. Every time a Sandbox is refreshed, user email addresses are appended with @example.com:
PBarnet=MyCo.com@example.com
8. For deploytment, the Platform Version may differ in Sandbox
Sandbox Tips & Tricks

11. Work with the business
Gather Requirements
Dedicated Salesforce.com Owner
Manage change requests
Prevent conflict
Not only are Sandboxes important to deliver apps fast, but
having a strategy is just as important
Process Governance Timing
Communicate with the business

12. Thank you