Making your Application Social with the Chatter API

Transcription

1 Making your Application Social with the Chatter API Logan Henriquez Product Quinton Wall Developer

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 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, 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 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, 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 filed on April 30, 2008 and in other filings with the Securities and Exchange Commission. These documents 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 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 @forcedotcom / #forcewebinar Developer Force Group facebook.com/forcedotcom

4 Agenda Why Social Enable Your App? Use Cases Eloqua: Demo and Sample Code Tips Summer 12 Preview Q&A

5 Make any app social with the Chatter API REST API

6 IT: Why Social Enable Your Custom Apps? Collab between dept. & teams Partners, customers, suppliers Make existing apps social

7 IT: Why Social Enable Your Packaged Apps? Connect to enterprisewide news feed (eg: Chatter) Easily add social functionality (feeds, likes, comments etc) Distribute app virally via feed

8

9 Chatter API Use Cases

10 Next Generation Intranets for the Social Enterprise Burberry World Company-wide and team based collaboration Dynamic, real-time information Integration of multiple data sources Sharepoint webpart reference implementation

11 Use Case Custom Mobile, Desktop, Tablet Apps Build custom mobile applications, e.g. Product information apps Q&A Note taking and case discussion for medical providers

12 Use Case - Internet of Things Share service data from Cars, Generators, Computers using custom object records / feeds Foster conversation centered on products and services. Scenarios: - Service - Technical presales - Technical support - Project Management

13 Build Highly Branded Customer Communities Enable partners or customers to collaborate with your employees or each other Share business process data Customize the UX to meet your exact brand requirements Extend to mobile and tablet apps

14 Drive Collaboration Around Business Process and Data Chatter feed inside external applications Supplement data, process, and analytics with rich conversations Analytics, Finance, Supply Chain Management, HR

15 Drive Collaboration Around Business Process and Data

16 Eloqua Use Case 105, Billion 8.2 Billion

17 Why Collaboration with Chatter? Buyers need information Marketers create info assets Sales has relationships Collaboration is key: Sales intuition + Marketing resources = Buyer engagement

18 What scenario are we solving Sales Marketer

19 Eloqua Demo

20 REST API Resources

21 Chatter API Resources Latest version "/services/data/v24.0/chatter All requests to API made using OAuth2 Start here

22 How We re Using the Chatter API Feed Users Groups Messages Records Topics Recommendations Files Organization Today Future

23 /chatter/users/me TBD styling changes

24 Feed Item Resources

25 Comments Resources

26 Users Resources

27 Comments Resource ( POST )

28 Chatter API Tips

29 Chatter API or SObject REST API? Chatter API: Semantically rich resources Localized presentation-ready data in JSON or XML form Comprehensive feed data in a single request Matches the web UI SObject REST API: Data directly from the database Arbitrary SOQL queries The same Oauth tokens can be used for both

30 Tips - General Group feeds are just record feeds /chatter/feeds/record/<group id> Security model of UI is observed News feed can only be retrieved for the logged-in user Following an object is described by a subscription. DELETE the subscription to stop following Use 'Accept-Encoding: gzip, deflate HTTP header Always encrypt your Oauth access and refresh tokens

31 Rate Limiting Rate limiting: each user + remote access app combination gets 200 requests per hour Requests to endpoints outside /chatter and /connect are not counted in this rate limit Image requests not rate limited Sobject API requests count against org-wide rate limit Use separate remote access apps for production and development to avoid being rate limited Also use different users if your automated tests run often

32 Tips Javascript served from non-salesforce domain Use a controller pass-thru to work around Single Origin Policy for ajax requests Two approaches to rendering: pass JSON responses through server as-is and render using client side template library such as Mustache, Handlebars, or Eco Deserialize and render to HTML on the server and send to client Requests from HTML (img tags, HTML forms) must also use controller pass-thru to put Oauth token into HTTP header

33 Tips Javascript served from salesforce domain Can make ajax requests directly to Chatter API and render to HTML on client. When Connect in Apex goes GA, you can also make requests to a controller to get custom rendered HTML. Use an ajax proxy if you re on a custom domain. (see the salesforce ajax toolkit) to work around SOP.

34 Tips Apex Apex Now Call the Chatter API using Apex callouts Use session Id from UserInfo Apex Future ConnectAPI class will provide Chatter API resources directly

35 Connect in Apex (Pilot in Summer) Exposing the same Chatter API resources and data in Apex Use cases include: Customized social experiences in Visualforce Custom Chatter feed rendering in Visualforce Posting feed items in Apex Modifying user and group photos in Apex Taking pilot nominations over the next two weeks.

36 How do I begin?

37 Take Aways Chatter can drive better user engagement with external applications Easy to build integrations with existing applications Wealth of interesting use cases emerge from news feed integration.

38 Q&A