Sandboxes are non-production environments that duplicate a production org's metadata and can be used for app development, testing, training, and user acceptance. There are different types of sandboxes that vary in refresh frequency and amount of production data included. Managing sandboxes strategically is important for efficiently building apps. Change sets allow migrating changes between sandboxes and production. Best practices include always testing in sandboxes first, keeping security settings and data consistent, and communicating with business stakeholders.

1. Sandboxes:
The Future of App Development
Managing Sandboxes to Build Apps Fast!
VP, App Development & Software Adoption, Barnet Associates
pam@barnetassociates.com
@pambarnet
President & CEO, Barnet Associates
evan@barnetassociates.com
@ideacrowd

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. 20142002 2005
Barnet Associates - Systems Improvement Solutions
The Barnet’s are loving Salesforce
Customer Partner Developer
3rd Place “Tic Tac Close”
Summer Hack-a-thon

4. Agenda
• Sandboxes Overview
• Strategies
• Demo!
• Sandbox Secrets & Best
Practices
• Key Resources
• Q & A
Professional
Edition
Enterprise
Edition
Performance
Edition
Unlimited
Edition
Developer
Sandbox
10 (change
sets not
available)
25 100 100
Developer
Pro Sandbox
5 5
Partial Copy
Sandbox
1 1 1
Full Sandbox 1 1

5. Salesforce app development projects
Customer Onboarding Ticket Scan Application Customer Community
Event Planning Opportunity Transfer Tracking Automate Sales

6. Fun Metrics & Timelines of some apps we’ve built
Automated Sales Rep Transition:
• APEX Trigger, APEX Test Class, Custom Object, Custom Fields, Workflow Rules with Field
Updates and Email Alerts
• 10 hours to develop, 30 minute demo, 2 weeks for business acceptance
Customer Community with Real Time Charts & Reports
• JSON APIs, APEX Controllers, APEX Test Classes, Visualforce Pages
• 2 weeks to develop, 1 day to deploy, 2 weeks for user adoption
Change Control Tracking
• Customization of AppExchange Change Control App, Workflow Rules, Custom Fields, Field
Updates and Email Alerts
• 5 hours to develop, 1 day to test and gain user acceptance, 3 days for user adoption

7. Custom Dashboard
JSON API from external
data source
Brought in via Jitterbit
Custom APIs
Charts built using
Visualforce Charting
Real-Time External Data

8. What is a Sandbox?
• Non-Production Environment
• Duplicates Production Metadata
• Used for developing and testing
• Used for training and user acceptance
• Linked to Production Environment
• Various methods of migrating changes to Production
• Large orgs will have multiple Sandbox Environments
• Admin Playground!

9. Sandbox Overview
Purpose of Sandboxes:
• Development
• Testing
• Reduce the time it takes to
convert your ideas into apps
• Reduce operational risk
• Increase Efficiency
• Training
• User adoption
• Raise User Satisfaction
Professional
Edition
Enterprise
Edition
Performance
Edition
Unlimited
Edition
Developer
Sandbox
10 (change
sets not
available)
25 100 100
Developer Pro
Sandbox
5 5
Partial Copy
Sandbox
1 1 1
Full Sandbox 1 1
Sandboxes by Edition

10. Sandbox Types Overview
Developer
1-Day Refresh
No Production Data
200 MB Data Limit
Developer Pro
1-Day Refresh
No Production Data
1GB Data Limit
Partial Copy
5-Day Refresh
Sample Production Data
5GB Data Limit
Sandbox Template
Full Copy
29-Day Refresh
Copies Production Data
Production Data Limit
Sandbox Template

11. Process to Implement New Functionality
Build and Test in Sandbox
Demonstrate to User Audience and Gain Acceptance
Build Change Set in Sandbox
Upload to Production
Validate in Production and Deploy!
1
2
3
4
5

12. Sandbox Strategies
How Sandboxes can be designated and utilized for maximum efficiency and governance
Production
Instance
Staging
Dev
Integration
Admin PlaygroundTraining
Dev
Dev
Rollup /
Integration/UAT
Release #1
Production Org
Full copy
Developer pro, test data
Partial Data
Developer
Dev
Dev
Release #2
Dev

13. Items to deploy
Create Changeset and
Upload to Production
Validate and Deploy
Change Set Name with
version #
Description
Add Items
Dependent items
Open Change Set in
Production
Validate and monitor
Progress for errors
Deploy
Test in Production
Training Custom Object
Contact Custom Fields
Contact Page Layout
Production OrgSandbox Org Sandbox Org
Demo - Sandbox Deployment using Change Sets
Custom Object to track Training Modules Completed by a Contact

14. Sandbox Secrets, Tips & Tricks
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. Refresh often and early!
8. Create a post refresh task list
9. Every time a Sandbox is refreshed, user email addresses are appended with @example.com:
PBarnet=MyCo.com@example.com
10. For deployment, the Platform Version may differ in Sandbox

15. Communicate with the business
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

16. Learn with Trailhead
The fun way to learn Salesforce
Learn More Learn More

17. Sandbox Overview:
https://help.salesforce.com/HTViewHelpDoc?id=create_test_instance.htm&language=en_US
Understanding Sandbox Environment Types:
https://help.salesforce.com/HTViewHelpDoc?id=data_sandbox_environments.htm
Developing Cloud Apps – Coding Optional:
https://developer.salesforce.com/page/Developing_Cloud_Apps_%E2%80%94_Coding_Optional
Quick Tutorial – Build a Cloud App in 5 Minutes:
https://developer.salesforce.com/page/Quick_Tutorial_1:_Build_a_Cloud_App_in_5_Minutes
Development Lifecycle Guide:
https://resources.docs.salesforce.com/sfdc/pdf/salesforce_development_lifecycle.pdf
Resources and Links

18. Thank Y u

19. Q&A