1. Implement Data Governance Around
Packaged Apps in Force.com
Developers
Brian Aggen @bdraggen
Kai Chen @kai_chen

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. Agenda
 The Data Governance Way
 Salesforce: Data Repository or Data Feed?
 Packages: Managed vs Unmanaged
 What’s in the Salesforce data toolbox?
 The Data Governator App
 Q&A

4. Before we begin …
There will be sporadic “Governator” quotes throughout the
presentation.
The first person to raise their hand and correctly identify the movie
will receive a prize!

5. The Data Governance Way
The fundamental discipline surrounding data governance
embodies…
 Data integrity
 Data management
 Data policies
 Process & risk management

6. Where Does Salesforce Fit into Your Organization?
As a Data Repository?
 In other words, Salesforce is the source of truth

7. Where Does Salesforce Fit into Your Organization?
As a Data Feed?
 In other words, Salesforce is NOT the source of truth
Data warehouse
Customer master
ERP system

8. “Who is your daddy, and what does he do?”

9. “Who is your daddy, and what does he do?”
Audience poll:
 Who considers Salesforce their daddy? (data repository)
 Who considers another system as their daddy? (data feed)
 Who considers their Organization as a combination of the two?
Why does this matter?

10. Data Governance Fundamentals
Salesforce provides mechanisms to enable data governance
regardless of where the data ultimately needs to reside.
 Mechanisms can be either
• Declarative
• Programmatic

11. Packaged Applications
Packages allow for distribution of Salesforce components
amongst different Organizations.
 Unmanaged Package
• Open source
 Managed Package
• Built-in versioning and patching capabilities
• Unique naming of components to prevent conflicts
• IP protection for Apex

12. “My CPU is intact, but I cannot control my other functions.”

13. Packaged Applications
How can we “control” the functions of a Managed package?
 Prevent data from entering the system
 Manipulate data after the fact
 Reevaluate the application value

14. Salesforce Toolbox
Preventing data from entering the system
 Declaratively
• Validation rules
• Field dependencies
• Page Layouts
 Programmatically
• Apex triggers / classes

15. Salesforce Toolbox
Manipulating the data after the fact
 Declaratively
• Workflow rules
• Approval process
• Reports
• Custom objects / fields
 Programmatically
• Apex triggers / classes / scheduled jobs
• Data Loader
• Visualforce Pages

16. Order of Execution
1. Layout, System Field, and user defined validation rules (*UI)
2. Execute before triggers
3. System Field rules and user defined validation rules (*System)
4. Saves the record but no commit
5. Execute after triggers
6. Execute workflows rules
7. Execute workflow updates
8. If the record was updated with workflow field updates, fires before and after triggers
only one more time, in addition to standard validations. Custom validation rules are
not run again.
9. Commits records

17. Data Governator App
Salesforce for Twitter and Facebook
@data_governator I’ll be back! #terminator2
Create new Contact

18. Data Governator App Gaps
Salesforce for Twitter and Facebook
•Merges Facebook and Twitter Contacts into a single a Record
Type
•Creates generic “Social Account”
•No mechanism to highlight trending hashtags

19. Data Governator App Solutions
Merges Facebook and Twitter Contacts into a single a Record Type
•Created a Workflow rule to update the Record Type

20. Data Governator App Solutions
Creates generic “Social Account”
•Trigger that fires after insert to create a new Account

21. Data Governator App Solutions
No mechanism to highlight trending hashtags
•Created a Custom Object to house hashtag data

22. Demo Time

23. “Get to the choppa!”

24. Brian Aggen Kai Chen
@bdraggen @kai_chen