Developer Workshop Workbook
•Transferir como PPTX, PDF•
1 gostou•2,250 visualizações
This document provides information about an upcoming developer workshop, including details about the presenters, login credentials, and links to resources like an online workbook. It also includes standard legal disclaimers about forward-looking statements and a safe harbor statement. The workshop will cover topics like the Salesforce1 platform, building applications with declarative logic and Apex code, integrating apps via APIs, and customizing for mobile.
Recomendados
Mais conteúdo relacionado
Semelhante a Developer Workshop Workbook
Semelhante a Developer Workshop Workbook (20)
Mais de Salesforce Developers
Mais de Salesforce Developers (20)
Último
Último (20)
Developer Workshop Workbook
- 1. Developer Workshop Pat Patterson Developer Evangelist Architect @metadaddy ppatterson@salesforce.com Samantha Ready Developer Evangelist @samantha_ready sready@salesforce.com
- 2. Login and Get Ready Internet Username / Password SF13 / SF13 http://bit.ly/dfc_beg_workbook
- 6. 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, 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-K for the most recent fiscal quarter ended July 31, 2011. This document and others 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.
- 7. Introduction to the Salesforce1 Platform
- 8. Salesforce1 Platform APIs Mobile Services Core Services SOAP APIs REST APIs Bulk APIs Tooli ng APIs Metada ta APIs Analyti cs APIs Soci al ET API Streami ng APIs APIs Mobile SDK Mobile Packs Offline Support Geolocat ion Custo m Action s Identi ty Private App Exchang e Mobile Notificati ons Visualfo rce1 Chatt er Workflo ws Analyti cs Ape x Multilangua ge Heroku AddOns Email Servic es ET 1:1 ET Fuel Multitenant Cloud Databa se Datalevel Securit y Schem a Builder Sharin g Model Translati on Workben ch Sear ch Heroku1 Monitori ng
- 9. Build Employee Apps Fast with the Salesforce1 App All your past investments... All Your Apps All Your CRM ...are now in the future Notifications Platform Flexible UI All Your Customizations All Your Devices Download the Salesforce1 App today. Publisher Actions
- 10. Salesforce1 Platform 6B Lines of Apex 500M API Calls Per Day 4M+ Apps Built on the Platform 72B Records Stored Salesforce is a Platform Company. Period. -Alex Williams, TechCrunch
- 11. 1.4 Million
- 12. Data Modeling
- 13. Spreadsheet Versus Application OR Relational Data Validated data Process driven workflows Approval System Field Auditing Users, Profiles and Permissions Enterprise Collaboration With the same amount of programming…
- 14. Let’s Build an App
- 15. Warehouse Application Requirements • Track price and inventory on hand for all merchandise • Create invoices containing one or more merchandise items as a line items • Present total invoice amount and current shipping status
- 16. Warehouse Application Requirements • Track price and inventory on hand for all merchandise • Create invoices containing one or more merchandise items as a line items • Present total invoice amount and current shipping status
- 17. Warehouse Application Requirements • Track price and inventory on hand for all merchandise • Create invoices containing one or more merchandise items as a line items • Present total invoice amount and current shipping status
- 18. Warehouse Data Model Invoice Number Status Count Total INV-01 Shipped 16 $370 INV-02 New 20 $200 Merchandise Invoice Line Items Line Merchandise Units Sold Unit Price Value INV-01 1 Pinot 1 15 $20 INV-01 2 Cabernet 5 10 $150 INV-01 3 Malbec 10 20 $200 INV-02 1 Pinot 20 50 $200 Name Price Inventory Pinot Invoice $20 15 Cabernet $30 10 Malbec $20 20 Zinfandel $10 50
- 19. Chatter Social framework for the enterprise
- 20. Tutorial 100 Optional: Tutorial 110
- 22. Declarative Apps Creating business applications with clicks not code
- 24. Formula Fields Operations for performing common logic
- 25. Excel style formulas Support for commons functions Math Text Date & Time Logical Can chain functions together: AND ( OR ( ISPICKVAL(StageName, "Closed Won"), ISPICKVAL(StageName, "Negotiation/Review")), ISBLANK(Delivery_Date__c) )
- 26. Validation Rules Formulas which block data entry if evaluated as true
- 27. WHEN IF Record is being inserted or updated Formula evaluates to true THEN Return error message
- 28. Roll-Up Fields Field type calculating on rows of child data
- 29. Child of Master-Detail Count or Aggregate
- 30. Workflows Event based business logic
- 31. When this happens Meets this Criteria? Perform These Actions
- 33. Approvals System to route approvals through an organization
- 34. Define Criteria Define Actions Track Approval History
- 35. Single/Multi/Skip step processes Route based on roles, or queues Approval via emails or Chatter
- 36. Security Identity, data security and user services
- 37. User Profiles Groups, Queues and Hierarchies Permission Sets SSO, SAML, OAuth 2.0 Connected Apps
- 38. TUTORIAL 120 OPTIONAL: TUTORIAL 150
- 40. APEX
- 41. Apex Cloud based programming language
- 42. Apex Anatomy Class and Interface based Scoped Variables public with sharing class myControllerExtension implements Util { private final Account acct; public Contact newContact {get; set;} public myControllerExtension(ApexPages.StandardController stdController) { this.acct = (Account)stdController.getRecord(); } public PageReference associateNewContact(Id cid) { newContact = [SELECT Id, Account from Contact WHERE Id =: cid LIMIT 1]; newContact.Account = acct; update newContact; Inline SOQL } } Inline DML
- 44. Common Use Cases Controllers Custom API and HTTP Callouts Scheduled and Batched Tasks Inbound/Outbound Email Services Triggers
- 45. Trigger Anatomy Object Definition Event Definition trigger MerchandiseTrigger on Merchandise__c (before insert, before update) { Merchandise__c[] merch = Trigger.new; if(Trigger.isInsert) { MerchandiseUtil.checkMerchandise(merch); } Trigger.old and new // Do more stuff... Bulkify code }
- 46. Unit Testing @isTest static public void testRequiredFields() { Merchandise__c m = new Merchandise__c(Name = 'Test'); try { insert m; System.assert(false, 'Shouldn't be able to insert Merchandise without’ + ' quantity & price!'); } catch (DMLException e) { // Expect to see an exception here – all is good } m.Quantity__c = 0; m.Price__c = 9.99; insert m; }
- 47. Unit Testing public WarehouseCSVController() { Boolean dummy = ApexPages.currentPage().getParameters().get(’dummy') != null; if (dummy) { allMerchandise = new List<Merchandise__c>(); for(Integer x = 0; x < 1500; x++) { Merchandise__c m = new Merchandise__c( Name = 'Widget ’+ String.valueOf(x), Quantity__c = 100, Price__c = 49.99); allMerchandise.add(m); } } else { allMerchandise = WarehouseDataQuery.getAllMerchandise(); } }
- 48. TUTORIAL 300
- 49. VISUALFORCE
- 50. Model View Controller Application design paradigm to divide data, logic and UI
- 51. Visualforce Cloud based component framework for interfaces
- 52. Visualforce Anatomy Controllers StandardControllers Custom Custom Extensions <apex:page StandardController="Contact" extensions="duplicateUtility" action="{!checkPhone}"> <apex:form> Data bound components Controller Callbacks <apex:outputField var="{!Contact.FirstName}” /> <apex:outputField var="{!Contact.LastName}" /> <apex:inputField var="{!Contact.Phone}" /> <apex:commandButton value="Update" action="{!quicksave}" /> </apex:form> </apex:page>
- 53. } JavaScript Remoting @RemoteAction public static String updateMerchandiseItem(String productId, Integer newInventory) { List<Merchandise__c> m = [SELECT Id, Total_Inventory__c from Merchandise__c WHERE Id =: productId LIMIT 1]; if (m.size() > 0) { m[0].Total_Inventory__c = newInventory; try { update m[0]; return 'Item Updated'; } catch (Exception e) { return e.getMessage(); $(".updateBtn").click(function() { } var id = j$(this).attr('data-id'); } var inventory = parseInt(j$("#inventory"+id).val()); else { $.mobile.showPageLoadingMsg(); return 'No item found with that ID'; } MobileInventoryExtension.updateMerchandiseItem(id, inventory,handleUpdate); } }); Access Apex from JavaScript Asynchronous Responses Apex JavaScript in Visualforce
- 54. Custom Components <apex:component controller="GeoComponentController"> <apex:attribute name="lat" type="Decimal" description="Latitude for geolocation query" assignTo="{!lat}” /> <apex:attribute name="lon" type="Decimal" description="Longitude for geolocation query" assignTo="{!lon}” /> <c:GeoComponent lat=”8.9991" lon=”10.0019" />
- 55. Page Templates <apex:page > <apex:insert name="detail" /> <div style="position:relative; clear:all;"> <apex:insert name="footer" /> </div> </apex:page> <apex:page StandardController="Invoice__c" > <apex:composition template="WarehouseTemplate"> <apex:define name="detail"> <apex:detail subject="{!Invoice__c.Id}" /> </apex:define>
- 57. Common Use Cases Email Templates Embed in Page Layouts Mobile Interfaces Generate PDFs Page Overrides
- 58. TUTORIAL 330
- 59. INTEGRATION
- 60. OAuth Industry standard method of user authentication
- 61. OAuth2 Flow Invoke OAuth User logs in, Tokens sent to callback Remote Application Salesforce Platform Call API Return Data Maintain session with refresh token
- 62. WORKBENCH
- 63. REST API API leveraging industry standard HTTP
- 64. REST API 1. Authenticate login.salesforce.com Mobile Application 2. Access API /services/data/query?q= SELECT+Id,+Name+FROM+Account 3. Get JSON or XML { “Id” : “001E0000002Jv2bIAC”, “Name” : “GenePoint” } Salesforce Platform
- 65. WORKBENCH
- 66. SOAP API XML messaging and WSDL based API
- 67. SOAP API 1. Authenticate login.salesforce.com Java Web Server 2. Access API <QUERY><SOQL> SELECT Id from Account </SOQL></QUERY> 3. Get XML <RECORDS> <RECORD type=“Account”> <id>oax02fdr756aFdad</id> </RECORD> </RECORDS> Salesforce Platform
- 68. Bulk API Asynchronous API for handling large datasets
- 69. Bulk API 1. Pull Recent Records ETL Tool TITLE: AppCo STREET: 1 Market Street REF:0001 Legacy Database 2. Push Updates NAME: AppCo MailingStreet: 1 Market Street ExternalID:0001 Salesforce Platform
- 70. Streaming API Bayeux implementation for real-time delivery of data
- 71. Streaming API 1. Handshake Java Web Server 2. Subscribe to Topic 3. Get Updates Salesforce Platform
- 73. TUTORIAL 370
- 75. Double-click to enter title The Wrap Up Double-click to enter text
- 77. Double-click to enter title Double-click to enter text @forcedotcom @metadaddy @samantha_ready #forcedotcom #askforce
- 78. Double-click to enter title Join A Double-click to enter text Developer User Group http://bit.ly/fdc-dugs
- 80. Become Double-click to enter titleA Leader Developer User Group Double-click to enter text Email: April Nassi <anassi@salesforce.com>
- 81. Double-click to enter title http://developer.force.com Double-click to enter text
- 82. THANK YOU
- 84. Fundamentals for the Enterprise Mobile Social Identity Data Marketplace
- 85. Mobile SDK iOS and Android SDK for developing with Force.com
- 86. Mobile SDK: Accelerate App Development Tools for building native, hybrid, and HTML5 apps on iOS and Android OAuth2 http://developer.force.com/mobilesdk Secure authentication and refresh token management API Wrappers Interact with Salesforce REST APIs with popular mobile platform languages App Container Embed HTML5 apps inside a container to access powerful native device functionality Secure Offline Storage Store business data on a device with enterpriseclass encryption Push Notifications Dispatch real-time alerts directly to mobile devices
- 87. Canvas Framework for using third party apps within Salesforce
- 89. Canvas Anatomy Any Language, Any Platform • • • • • Only has to be accessible from the user’s browser Authentication via OAuth or Signed Response JavaScript based SDK can be associated with any language Within Canvas, the App can make API calls as the current user apex:CanvasApp allows embedding via Visualforce
- 91. Polyglot Framework PaaS allowing for the deployment of multiple languages
- 93. Heroku Github Repo Push Deployments Monitor Application Pull / Push Development Changes Local Repo $ git push heroku master Counting objects: 67, done. Delta compression using up to 4 threads. Compressing objects: 100% (53/53), done. Writing objects: 100% (67/67), 26.33 KiB, done. Total 67 (delta 5), reused 0 (delta 0)
- 94. HEROKU
- 95. AppExchange Application Market for the Salesforce Platform
Notas do Editor
- This is the deck for the Private Salesforce Developer Workshops as well as the Beginner’s Track of the ELEVATE program.For the private workshops, use the blue platform bumper slides. For ELEVATE, use the darker ELEVATE ones. The font included in the zip is for the ELEVATE slides.The speaker notes are provided as a guide, not necessarily specific speeches. These notes will not insist on demos, presenters should prep their presentations with the demos they are comfortable with.The recommended agenda can be found here: https://docs.google.com/a/salesforce.com/spreadsheet/ccc?key=0Akr6pvkAv8X5dGFEN2ZWNUxWbS1SVFBoRS1oZU5kQWc#gid=6Errors, comments, suggestions in either the deck or the workbook can be mentioned on Josh Birk’s Chatter feed, or written up in Google Docs and shared with Josh Birk and Mario Korf.
- Change this slide to match the local internet requirements.The bit.ly link points to the latest HTML draft of the new workbook. This is different than the official workbook on developer.force.com and there are schema differences, so attendees cannot mix and match.
- Highlight that this is not just a day of talking to them, this is a dialogue and they should ask questions as they like – even ones that don’t pertain to the current “section”. Projects they’re working on, features they have heard about, etc.
- Safe Harbor
- Safe Harbor
- So when you are first asked to start tracking data, it might be very tempting to just open up a spreadsheet and start adding rows. But why do that when for the same amount of programming you can get all these features on the right side?
- Let’s have an exercise in requirements gathering. Here is some of the core needs for our Warehouse application. What nouns here should we be looking at to model our data with?
- Let’s have an exercise in requirements gathering. Here is some of the core needs for our Warehouse application. What nouns here should we be looking at to model our data with?
- Let’s have an exercise in requirements gathering. Here is some of the core needs for our Warehouse application. What nouns here should we be looking at to model our data with?
- Here is an overview of what our data model will look like.
- We also have another thing built right into your data model: Chatter. Chatter is a collaboration engine for your users, and it can interact directly with your data.
- Safe Harbor
- When we say declarative, we might also refer to the as “clicks not code”. Or citizen development. This is development without needing to use programmatic logic, and it is a very powerful way to build and maintain your applications.
- Let’s revisit that spreadsheet idea. You can already see how custom objects and validation rules make for a more robust system. But we can take it even farther, even without coding a single line.
- You used a formula to define your validation rule – but what if you could define a field itself this way? This gives you data which is calculated in real time, but can be treated like a normal custom field.
- Formula fields work like formulas work in Excel spreadsheets.The formula here insists that a delivery date is needed for these stages.
- What’s more important than data? Clean data. Validation rules allow you to block bad data before it even gets into the system.
- Validation rules are applied anytime data is being inserted or updated. If your formula evaluates to true, the user will get an error instead of the system being updated.This is true no matter what, through the browser, through an API, through a mobile app. These are rules baked right into your data layer.
- Roll-up fields are similar to formula fields, but they play off that master-child relationship you created in the first tutorial. Here, you can do calculations on the fly based on that relationship.
- A simple roll-up field might simply count the number of children that are in the relationship. In terms of your invoice, you could count how many line items are related. Or, if you wanted, you could aggregate a child field like value – and get the full value of that invoice.
- Workflows are where we start to see specific business rules being replicated in the system. They allow you to perform actions on your data based on specific conditions.
- They are broken up like this: When you insert or update a record, and that record meets specific criteria you have set – the system allows you to perform various actions.
- The system could send an email, create a task, update a field, or even send a message to an external endpoint.These actions could occur immediately, or they could be time-based and occur at a specific point down the road.
- Approvals are where we can put a real human element to controlling your data. This is another example of a feature we have created because we know enterprise apps will need this. Instead of having you create your own approval app, just use our.
- Similar to workflows, records can be submitted to approval if they meet certain criteria. You can then perform actions based on if the record was submitted, approved or denied. For instance, you might want to change the status of the record so that you can easily track the progress.You can also track the whole approval history on the record layout.
- Approvals have lots of options.
- Security is another aspect of our platform we take very seriously. Yes, we want you to be able to create a robust data structure. Your app should have the ability to perform complex business rules. But on top of all that, we need to keep it secure.
- The Salesforce Platform is a robust family of Identity and security features. You can assign users profiles, and even define users within groups, queues and hierarches. Permission sets allow you to group specific privileges across profiles, making it easier to maintain exactly who can do what. We also have multiple options for how people sign in: we’re an Identity Provider ourself, we support SAML and have implemented OAuth 2.0. For mobile, we have defined connected apps specifically so that admins can maintain who can use what out in the field.
- Update to let them know where lunch is
- Safe Harbor
- For when declarative logic is not enough, we provide Apex. Apex is a cloud-based programming language, very similar to Java – except that you can code, compile and deploy all right from your Salesforce instance. You’ll see how we can create robust programmatic functions right from your browser.
- For those unfamiliar with OO, here’s what a simple class structure looks like. NOTE: If you’re using this slide deck for a very technical audience, breeze through this section and get to meatier features of Apex, otherwise go into a basic discussion about how Apex is divided into classes, refers to information with variables, etc.Now note however, the big difference – we can access and manipulate data with just a few lines of code, no additional configuration required. Apex will automatically know everything you’ve done declaratively for your application.
- So what can you use Apex? In the next tutorial, we’ll talk about Controllers – which is how you primarily use Apex without our custom page framework. However, you can also use Apex to both extend some our existing API’s, and also to call out to others. It has a full HTTP request and response library. You can also communicate via email, both outbound – send out emails to recipients … and inbound. With inbound email you setup an Apex class, get a email address associated with it, and then you can have Apex react programmatically to it.Scheduled and Batched Apex allows you to run tasks in the background. A scheduled Apex job will run at a specific time, perform some logic and be done. With a batch job, it will also run at a specific time – but it will run against a set of records defined by SOQL until it is done all those records. Scheduled jobs are great for checking against your data and send out updates or alerts, while batched jobs can provide functions like data archiving and clean up.Finally, we triggers. Let’s take a closer look at those.
- A trigger looks a lot like a class, and behaves in a very similar way – but part of the definition is specifically defining what object it should act on, and when. Unlike an Apex class, triggers are called when events occur on specific object types. For instance, here we will call a utility method any time Merchandise is updated.
- Want to make Chatter smarter? You can extend it with Apex Triggers to associate highly custom behaviors. Here if someone adds a hash tag “promote”, Apex will automatically add it to the promotion and even update the record to let everyone know it just did that. We’ll also be doing a deeper dive into Apex and triggers today as well.
- Unit testing is code to test your code. There are three basic parts to a good unit test – creating test data which simulates a scenario, and in a unit test all the data is transient … it never actually goes into the system. Next you will want to execute as much of your code as possible. We call that code coverage. To go from sandbox to production, you’ll need 75% coverage. But 75% probably shouldn’t be your target. Actually, 100% should probably be your target. The last bit is assertions, which prove that the outcome is what you expected.And we take this seriously on our side. Anyone want to guess how many of your unit tests Salesforce runs while testing our releases? It’s what you’d want – it’s 100%. So by writing good unit tests, you’re helping us not break your code.
- Here is an example of code coverage. In thise case, we’re not testing for the dummyscenario.
- If you aren’t familiar with the MVC paradigm: Model View Controller, here is an easy way to think about. Think about how your arm moves. It’s not just one slab of jelly. You start with bones – and the defines the basic structure of the arm. That’s your Model, or Data section. You’ve worked with this already, using the declarative process. Now how do those bones perform actions? Muscle. You’ve already added a little muscle with workflows and validation rules, and we’ll see more later with Apex. But for now, we want to talk about the skin – adding a cosmetic interface to the app.
- This is where Visualforce comes into play. Visualforce is our user interface framework in the cloud, allowing you to create custom pages quickly and easy via components.
- What do we mean by components? Well you’d start with a page component, and that will define how the whole page is going to be rendered. And then you can add things like a form and fields for the form. Now everything you see here will be HTML when it gets outputted. So you’d have and HTML form, HTML input tages, etc. To the browser, it is just standard HTML.But how are we binding data here? We define a controller, which gets access to server-side logic. Whenever you see these brackets and that exclamation point, you’re looking at dynamically bound data which will effect how the component is rendered.However, the server-side logic here is a little interesting. Do Standard Controller demo, then go back to describe custom controllers and extensions.
- Now that you’ve seen how controllers normally look, let’s look at a different trick Visualforce has. You can also access server-side code directly via JavaScript. The Apex code is specified with the @RemoteAction annotation, and then we can call it from JavaScript easily. This is a very lightweight approach to communicating with data. You’ll see an example of this as part of the tutorial.
- You can also create completely custom components with your own logic that utilize attributes you define. This makes your Visualforce portable and easy to maintain.
- On the flip side, Visualforce also has template support, you can define a page and which sections can be utilized, and then another page can define those sections for the template.
- Visualforce also has components specifically for duplicating the Chatter interface, if you want to use that with your pages.
- Other uses for Visualforce include creating custom email templates, embedding Visualforce into existing layouts, rendering PDF instead of HTML, creating custom Mobile interfaces and also completely overriding a page.
- Before we get into specifics about API integration – let’s talk a bit about Identity. Identity services, being able to authenticate your users securely – is incredibly important, especially once we start accessing the platform from third parties.Now many of you may have existing applications which use our API’s – who here has written a mobile or desktop app that logs into Salesforce, for instance? If you wrote that app with a username and password screen, consider what you are taking on there: you have to handle those credentials with the same care we do on login.salesforce.com, right?
- What if you didn’t have to? Stupid question time: who has used Facebook? Right, exactly – and if you’ve used Facebook you have probably seen those popups that say things like “Farmville would like to do these three things as you”. You hit confirm, and Farmville has access to some of your Facebook account, but only the parts you let it. And you never gave them your password. And at any time, you can revoke the app.That’s Oauth, and the Salesforce Platform has an excellent implementation of it. It works by having the app send the user to the first party platform, in this case Salesforce, who logs the person in. The application and the plattform essentially confirm each other, and then at the end of it – the app gets a session token with only the permissions you granted.
- Now let’s talk about our specific API’s. We have API’s to fit a wide range of use cases. Our REST API is very versatile, and one of the main use cases is mobile applications.
- That’s because the REST API is very lightweight. You access it with industry standard HTTP calls. So when you call http://cnn.com, that’s an HTTP GET call. Your browser returns HTML, and you see a web page. This is the same, but authenticated, and you get JSON back. JSON is a very lightweight data type and many languages and frameworks already know how to parse it.
- Now our old workhorse is our SOAP API.
- The flow of SOAP is very similar to REST, but the messaging is different. With SOAP, you are sending and receiving an XML message in a specific format. This can get heavy, size-wise, but it is also very stable and predictable. You can create a document called a WSDL (Web Services Definition Language) which defines how those messages look, and a lot of languages like Java and C# can easily consume a WSDL and create classes that talk to the API automatically.
- Now our Bulk API is meant specifically for loading large datasets. It’s asynchrounous to maximize the the server processing and allow for potentially lengthy load times.
- ETL (Extract Transform Load) tools can leverage the Bulk API to insert rows, pull data, and even modify the data in between … to say, match up columns with different names.
- Like the Bulk API – the Streaming API is designed for a very specific problem. What if you need real time updates, but you don’t want the API cost of constantly asking the server is anything has changed?{I usually talk about a Python dev who wrote a script to grab specific accounts, hand them off to a local process and then attach a resulting PDF to the account. It reduced a 45 minute process to a couple of minutes, and it made the system far more responsive. But to make it realtime, he polled the API every millisecond, which killed his API limit. Modified to work with the Streaming API, it now works great}
- The Streaming API gets a handshake from the platform, and then can subscribe to topics. Topics are mostly defined by SOQL to describe the kind of data the topic is pushing. Then, as long as that handshake is open – the updates get sent down to the client.
- Time to wrap things up
- Check inboxes for the survey link, or go to this link.
- You can find us easily on Twitter.
- Join your local DUG
- Or start one
- If there is one URL to remember…
- But now let’s talk about important parts of the platform that we don’t have time to cover today. Like the Mobile SDK, which allows you to easily create iOS and Android applications that run on the Salesforce Platform.
- Salesforce.com provides a host of Mobile SDK’s – Native, Hybrid, HTML5 – to help streamline your mobile app development efforts.These SDK’s are the fastest way to connect mobile apps on the extended Salesforce platform. In fact, they were designed so you can mobile-enable features from any of the major platforms that Salesforce offers.Mobile SDK’s can be found online at developer.force.com/mobile along with a handy developer workbook.
- Let’s talk about using Canvas, which allows me to easily put third part applications into Salesforce in a secure manner.
- For instance, maybe I have a large internal intranet applications. I don’t want to port all that functionality into Salesforce, but I do want to be able to integrate this one interface. Canvas allows you to easily bring that interface into the Salesforce UI, and in a very intelligent way.
- Heroku supports a polyglot framework: meaning it deploy many different languages.
- Describe AppExchange and packaging in general. If you’ve had the ISV team on hand, you can skip these as they would have already covered the material.