Introduction to Apex Triggers
2 likes2,537 views
The document introduces Apex triggers in Salesforce, covering their definition, usage, and operational details. It includes a safe harbor statement regarding forward-looking statements and risks associated with the company. The presentation aims to educate attendees on triggers, including code examples and considerations for real-world applications.
Introduction to Apex Triggers
- 1. Introduction to Apex Triggers Brad Herman Master Solution Engineer [email protected] Dreamforce 2015 Nishant Chandra Solution Engineer [email protected]
- 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. Some interesting things about Brad 8 years at Salesforce Built webapps in ASP Classic Published on AppExchange Some interesting things about Nishant 1.5 years at Salesforce Built multiple Heroku Apps Admin & Developer certs Who are we?
- 4. ▪ Who has written Apex? ▪ Who has coded/scripted in another language? ▪ Who has built a Salesforce workflow rule? ▪ Who has seen the Salesforce setup page at all? Who are you?
- 5. ▪ Introductions ▪ What is an Apex trigger ▪ When to use a trigger ▪ Deconstructing a trigger ▪ Considerations for triggers in the real world ▪ What you can do next ▪ Questions (and, hopefully, answers) What are we going to discuss?
- 6. What is a trigger? “…procedural code that is automatically executed in response to certain events in a database…” - Wikipedia
- 7. What Happens When You Hit “Save”?
- 8. What Happens When You Hit “Save”? 1. Old values are overwritten 2. System Validation Rules 3. Apex (before) triggers 4. Custom Validation Rules 5. Record saved to DB (not committed) 6. Record reloaded from DB 7. Apex (after) triggers 8. Assignment Rules 9. Auto-Response Rules 10. Workflow Rules 11. Escalation Rules 12. Rollup Summary Formulas updated 13. Database Commit 14. Post-commit logic (Sending emails)
- 9. *key takeaway: it’s server-side, multi-tenant, object-oriented How does Apex work?
- 10. Why might I use a trigger?
- 11. before insert before update before delete *key takeaway: any time something changes in the database What events can trigger Apex? after insert after update after delete after undelete
- 12. Show me the code!
- 13. trigger insertContact on Account (after insert) { for(Account acc : trigger.new){ Contact cont = new Contact(); cont.LastName = acc.name; cont.AccountId = acc.ID; insert cont; } } What does a trigger look like?
- 14. That last one was too simple?
- 15. Other cool stuff
- 16. Considerations for the real world
- 17. Is bulkification even a word?
- 18. Do I really have to test my code?
- 19. No, seriously, do I really have to test my code?
- 20. How do I deploy my trigger into production?
- 21. Good declarative tools Triggers: a last resort?
- 22. What can should you do next?
- 24. Share Your Feedback, and Win a GoPro! 3 Earn a GoPro prize entry for each completed survey Tap the bell to take a survey2Enroll in a session1