The document provides an introduction to Apex triggers in Salesforce, explaining that triggers are custom code that automatically executes in response to create, update, or delete events on objects. It discusses when triggers should be used compared to other options like workflow rules, and gives examples of how triggers could be used to automatically create related records or send emails in response to events. The document also covers best practices for testing and deploying trigger code to production environments.

1. Introduction to Apex Triggers
Arming the Dangerous
Iman Maghroori, Lead Sales Engineer
@IMaghroori
Josh Kaplan, Senior Product Manager
@JoshSFDC

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. Iman Maghroori
Lead Sales Engineer
@IMaghroori

4. Josh Kaplan
Senior Product Manager
@JoshSFDC

5. Here is the Plan
What is a
Trigger?
When / Why
Trigger
Deconstruction
Tools
Resources
Q&A

6. SURVEY: RAISE YOUR HAND IF YOU’VE…
 Created a Custom Field?
 Created a Workflow/Approval rules?
 Written any code before?
 Written Apex code?
 Written a Trigger before?

7. What is a Trigger?

8. What is a Trigger?
“…is procedural code that is
automatically executed in response
to certain events in a database…”
- Wikipedia

9. What is a Trigger?
“ …custom code that fires
when a record is created,
updated or deleted.”
-Iman Maghroori

10. What Happens When You Hit “Save”?

11. 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)

12. Now You’re Dangerous…

13. When Should You Use Triggers?
• When all other options fail
• Don’t write code if you don’t have to
• Easier to maintain
• Easier to change
• Faster to deploy

14. Workflow Can…
• Update Fields
• Assign Tasks
• Send Emails
• Send Outbound Messages (Integrations)

15. Workflow Cannot…
• Create Other Records – Automatically create child records.
• Complex Calculations – Calculate total revenue from child accounts
• Automatically Submit Records for Approval
• Delete Records

16. Apex: The Programming Language of Force.com
Object-oriented language
Java-like syntax
2.5 Billion Lines Of Apex

17. Why Apex?
Runs in the Cloud
Integrated to Your Data
Convenience Features
Testing Framework
Backward Compatibility

18. The Force.com Platform is a Multi-Tenant Environment

19. Use Case: UberJet

21. Create Invoice Trigger

23. Reserve Jet Trigger

25. User Email Trigger

26. Workflow Can…
• Update Fields
• Assign Tasks
• Send Emails
• Send Outbound
Test Your Code!

27. 75% Minimum Code Coverage Before You Deploy
We check for the %, you should check for all the possible use cases.

28. How to Deploy to Production?
• Make sure your code passes the tests & test coverage
• Create an “Outbound Change Set” and add your updates to it
• Push the Outbound Change Set to your Production Environment
• Accept the Inbound Change Set in your Production Environment.
• Setup->Deploy->Inbound Change Sets -> [Change Set] -> Deploy

29. Next Steps to Level Up
• Developer Environment
• Apex Workbook
• To Learn More

30. Where Can I Go for Help?
• Developer.force.com
• Salesforce.com Training / Certifications
• Code Share
• Developer Community
• Apex Guide
• Help & Training
Take it to the Next Level: Professional Services

31. Any Questions?