Wondering how to manage multiple Salesforce environments for managing your release? Join us as our Architects show how large enterprises manage Sandbox environments. Learn some of the key considerations in picking sandbox types and migration tools to lay out a process to manage an effective Release Management.
From Sandbox To Production: An Introduction to Salesforce Release Management
1. From Sandbox To Production
An Introduction To Salesforce Release Management
Seth Tager, Salesforce, Lead Member of Technical Staff
John Vogt, Salesforce, Senior Product Manager
2. 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 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.
8. A little bit of info about our fake company…
Acme Company
▪ Purchased CRM Enterprise Edition from Salesforce – No Add-on Products
▪ Small IT department, 2 Developers, admins wear many hats
Use Cases
▪ Typical - need to track contacts, accounts, orders
Requirements
▪ Create custom order forms to track orders, update accounts, and contacts
• Visualforce Pages for form
• Apex Controller to manage work flow
• Customer Schema objects and fields for further customization
9. Org Customization for Acme
If Possible, Stay in the Browser
▪ With a small or no IT shop and limited admin or developers, its best to avoid desktop tools
that you would have to install, upgrade, etc.
▪ Staying in the browser, you still have the ability to customize through several tools
▪ If you are using Apex or Visualforce, we recommend the Developer Console. This tool is
getting the most attention in our dev teams and has a solid roadmap.
Stick with Point and Click
▪ Point and click features were created because anyone can jump right in and customize – this
can empower some business users that don’t have a traditional IT/software development
background
Sandbox First!
11. Demonstration
▪ Created Some Objects and Fields
▪ Use Developer Console to quickly create a Visualforce or Apex class
▪ Set up deployment connections
▪ Create an outbound change set and upload
▪ Deploy the changes and validate the deploy
12. Quick Recap
Stay in the Browser
▪ Stick with Point and Click
▪ Use Developer Console for Development
▪ Use Change Sets for Deployment
Test & Validate before you Upload & Deploy
▪ Understand the criteria for code coverage on Apex
Develop & Test in the Sandbox
14. Demonstration
▪ Play the role of another unchecked user
▪ Modify the custom schema in the production org
▪ As the original sys admin make an addition change to the schema in
the sandbox
▪ Create the outbound change set, upload, and deploy
15. Best Practices for Force.com Development
Have a Change/Release Management Process!
▪ No change management process out of the box
Have a documented Project Plan
▪ Requirements/User Stories
▪ Test Plans
▪ Release Schedule
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)
17. Demonstration
▪ Create a new Permission Set on AcmeOrder
▪ Create the outbound change set, including the Permission Set
▪ Save, Upload, and Deploy the change set
▪ Deploy and Validate in the production org.
18. What just happened to my Profile/Permission Set?
Profiles and Permissions Sets are not standalone
Profiles and Permission Sets must be assigned in the production org
Good use cases for deploying profiles:
▪ Object CRUD
▪ Field Permissions
Bad use cases for deploying profiles:
▪ Layouts
▪ Record Types
Dude, Where's my permission?
19. I can’t add my component to a Change Set
Manual Deployments can be necessary
▪ Not all components are exposed through the Metadata API
▪ Unsupported Metadata Types
Best Practice:
▪ Deploy as much as possible with Change Sets
▪ Then go to the production org and manually create the components you have
already created and tested in the Sandbox
20. Best Practices for Release Scheduling
Understand our release schedules
▪ 3 Major Releases
▪ Participate in the Preview Window
▪ Follow Trust
When to deploy
▪ Conservative:
• Do not release during the preview window
• Let the major release simmer for a few weeks
▪ Aggressive:
• Release early and often
21. Best Practices for managing your Sandbox
Refresh after Every Release
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
23. Recap
Stay in the Browser
Test & Validate before Upload & Deploy
Have a Release/Change Management process
Maintain Strict User Governance
Have a Post Refresh Run List
25. New Sandbox Lineup & Bundles
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 /
Object)
None
5
10
15
200MB
1GB
(~500K records)
5GB
(2.5M records)
Match production
Bundled Developer
Sandboxes
Sandbox Size
27. Speaker Name
Speaker Name
Speaker Name
Speaker Name
Speaker Title,
@twittername
Speaker Title,
@twittername
Speaker Title,
@twittername
Speaker Title,
@twittername
28. We want to hear
from YOU!
Please take a moment to complete our
session survey
Surveys can be found in the “My Agenda”
portion of the Dreamforce app