Your SlideShare is downloading. ×
0
Five Admin Tips Every Developer Should Know
Five Admin Tips Every Developer Should Know
Five Admin Tips Every Developer Should Know
Five Admin Tips Every Developer Should Know
Five Admin Tips Every Developer Should Know
Five Admin Tips Every Developer Should Know
Five Admin Tips Every Developer Should Know
Five Admin Tips Every Developer Should Know
Five Admin Tips Every Developer Should Know
Five Admin Tips Every Developer Should Know
Five Admin Tips Every Developer Should Know
Five Admin Tips Every Developer Should Know
Five Admin Tips Every Developer Should Know
Five Admin Tips Every Developer Should Know
Five Admin Tips Every Developer Should Know
Five Admin Tips Every Developer Should Know
Five Admin Tips Every Developer Should Know
Five Admin Tips Every Developer Should Know
Five Admin Tips Every Developer Should Know
Five Admin Tips Every Developer Should Know
Five Admin Tips Every Developer Should Know
Five Admin Tips Every Developer Should Know
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Five Admin Tips Every Developer Should Know

442

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
442
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
24
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Five Admin Tips Every DeveloperShould KnowRebecca Dente, AchieversNick Hamm, Appirio
  • 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 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.
  • 3. Nick HammCloud Solutions Architect,Salesforce MVP
  • 4. Rebecca DenteDirector of Cloud TechnologySalesforce MVP
  • 5. Youre a DeveloperYou guys are all devs. You spend your time in code. You live Apexand breathe visualforce.
  • 6. You are not an AdminAdmins are those people in the business suits on theother side of the office.You know the ones that get all the credit for yourwork?
  • 7. Why do I care about how Admins work?We want to share with you some tips that will make your life easier,but also make more people release the kickass stuff you do.Working together means you can get more code, and more appsthrough testing and into the hands of users to let you start writingthe next cool app.
  • 8. AgendaCommon Clicks vs Code scenariosVisibility of work between a team of Admins and DevsImportance of Change ManagementTakeawaysQ&A
  • 9. Problem:  I need to enforce data qualityCommon developer solutions:  Write a trigger to validate data inputs
  • 10. Admin Solution!Validation RulesFormula Fields/Cross-object Formula Fields
  • 11. Problem:  I need to update or summarize data when a user makes changesCommon developer solutions:  Write a trigger to update field values  Write a trigger to summarize child object data
  • 12. Admin Solution!Workflow RulesRoll up summary fields
  • 13. Problem:  I have to make Visualforce changes when new fields are added or moved on the page layoutDeveloper solutions:  Edit the Visualforce page and reposition the fields  Add new Visualforce code to display new fields
  • 14. Admin Solution!Fieldsets!These will help you to leverage even your entry-level Admins
  • 15. Problem:  Deployment/promotion of changes between environmentsCommon developer solutions:  Eclipse IDE  Fire up some ANT scripts!
  • 16. Admin SolutionLeverage change sets. Shared insight Allows admins to help with the deployment processEXTRA CREDIT – create a release schedule that all admins & developers stick to
  • 17. Problem:  My users want a 7 step wizard for data entry  I dont have the bandwidthCommon developer solutions:  300+ lines of code that will require heavy editing every time the business changes their minds  Ill get that to you next month
  • 18. Admin SolutionVisual Workflow
  • 19. Developer AND Admin Problems Development Amnesia No one is using my stuff!
  • 20. Working Together Implement a change management process that everyone adheres too Communication is key Knowledge-sharing
  • 21. Take AwaysClicks before Code Validation Rules and Formula Fields Workflows/Approvals Field SetsChange SetsVisual Workflow
  • 22. Rebecca Dente Nick Hamm Director, Cloud Cloud Solutions Technology Architect

×