Take control of your Salesforce application with a governance process! Establishing a governance process helps us sort change requests and work with all of our stakeholders, from end users to developers. Join us as we teach you how to manage your entire application lifecycle process by instituting a governance process for your business.
3. 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.
4. Get Social with Us!
@salesforceadmns
#awesomeadmin
Salesforce Admins
Salesforce Admins
The video will be posted to YouTube
& the webinar recap page
(same URL as registration).
This webinar is being recorded!
5. Join the Admin Webinar Group for Q&A!
Don’t wait until the end to ask your
question!
• We have team members on hand to answer
questions in the webinar group.
Stick around for live Q&A at the end!
• Speakers will tackle more questions at the end,
time-allowing
bit.ly/AdminWebinarGroup
9. Set up a Center of Excellence
Transparency is key
Identify
Stakeholders
Define Roles &
Responsibilities
Set Structure Set Scope
10. • Learn about Salesforce Identity features
• Utilize single sign-on (SSO)
• Know all data integration endpoints and data flows
• Be ready to identify possible data impacts when outside systems change
• Maintain your own list of integrated fields with all attributes
Coordinate across platforms
Know Your Ecosystem
12. Principles of Change Management
Collect ideas and
requests from users
Analyze & Prioritize
Requests
Configure, develop &
deploy using Sandbox
Train end-users on new
or changed functionality
Collect
Configure,
Develop & Deploy
Analyze &
Prioritize
Train
End-Users
13. LevelofEffort
Process/Security Impact
Release Management
Define a release strategy
Immediate Releases
• Implement immediate changes
• Owned by individual sub-group
• Minimal impact to the production flow
Monthly Releases
• Minor changes impacting two or more groups
• Thrice as often as a Major Release
• Minor impact to training and production
Major Releases
• Major impact on production and integration
• Significant changes e.g. AppExchange app customization
• Impact across more than one business unit
• Staggered with platform releases
Also Major Release
• Requires changing user permissions
• New declarative app
• Staggered with platform releases
15. Sandbox is a Key Part of Cloud Building
• Copy of production on similar infrastructure
• Templates for faster creation
• Change sets for easier deployment
• IDEs for faster development
SANDBOX
PRODUCTION
16. Bundled Sandboxes by Edition
Developer Developer Pro Partial Copy Full
Professional Edition
10
(no change sets)
Enterprise Edition 25 $ 1 $
Unlimited Edition 100 5 1 1
17. Salesforce Sandboxes
Developer Developer Pro Partial Copy Full
Refresh Interval 1 Day 1 Day 5 Days 30 Days
Includes Setup &
Configuration
Yes Yes Yes Yes
Copies Data Records No No Yes (partial) Yes
Sandbox Templates/
Sampling
No & No No & No
Templates: Yes
Sampling: Yes (to 10k
records per object)
Templates: Yes
Sampling: No (full data
copy possible)
Sandbox Size
200MB data
200MB files
1GB data
1GB files
5GB (~2.5M records)
File Storage Dependent on
Sample
Match Production for Data
and File
18. Sandbox Access Considerations
Post-refresh scripts and tasks
• To write Apex, users need FULL org access
• This gives full (confidential) data access to non-approved developers
Clean data Edit users Load sample data
19. Sandbox Deployment Methodology Example
Expedited
Dev
Dev
Dev
Dev
Edition
Dev
Edition
Dev Pro
Full
Copy A
Full
Copy B
Prod
Standard
Try premium
features!
Developer Admin
21. Key Takeaways
You can do it!
1. Secure management/executive support
2. Familiarize yourself with your IT ecosystem
3. Identify workstreams/projects and draw planned flow to
present to stakeholders
4. Scale down appropriately