ELEVATE Advanced Workshop

2,007 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,007
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
59
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Check this again – find that transaction / average time stat
  • Here is an overview of what our data model will look like. Recommended: Break into a demo of building data in the browser, either custom object wizard or schema builder depending on audience/workbooks
  • We are going to start the day by talking about unit testing, and then in a bit SOQL. Because these are aspects of the platform which are really a dialtone, something we should be constantly evolving with.And yes, that’s a real bug. The first real bug.So if our new fictional job is to enhance this existing Warehouse application, how we write our unit tests are going to be very important.
  • So let’s talk about what some of your best practices are? Or if you’re brave, some of your worst?OK, let’s actually look at some really bad examples.
  • So to recap – Unit Tests should prove out not just code, but use cases. You should try to cover as much of your code as possible. And when should you test?
  • One theor
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • Indexed fields are fields tracked specifically by the database, and hence can lend to greater performance when your queries use them.
  • Apex can automatically create Maps from any SOQL result, and you can use that feature to either easily loop through the results or even to easily track the result in the map. For instance, the example here on the bottom would make it possible to find a specific contact in the result with one call from the map.
  • It’s also good to remember that you can pull children from the parent in one SOQL call. Let’s take a look at that in the Dev Console.SELECT Name, (SELECT Merchandise__r.Name from Line_Items__r) from Invoice__c LIMIT 5
  • You can also assign the SOQL result directly to a list, and then loop through that array. This allows you to quickly bulkify your code by generating loops and then performing any necessary DML when those loops are done.
  • One feature added recently to SOQL was the ability to use a readOnly annotation or flag to declare the results unusable in DML, but greatly expanding the number of results that can be handles. For instance, this visualforce page would normally only be able to handle an array of 1,000, but with readOnly that limit is relaxed to 10,000.
  • Some of the fields in the database are polymorphic, but until a few releases ago – SOQL didn’t really recognize that fact. Now that it does, you can cue specific results from those fields based on their Sobject type. Here’s an example in the Dev Console.SELECT Subject, TYPEOF What WHEN Account THEN Phone, NumberOfEmployees WHEN Opportunity THEN Amount, CloseDate ENDFROM Event
  • OFFSET allows you to create paginated results easily. The query on the left would give us the first 10 results, and the query on the right would give us the next 10. To see that in the Dev Console:SELECT NAME from Merchandise__c LIMIT 5 OFFSET 0SELECT NAME from Merchandise__c LIMIT 5 OFFSET 10(Or use Contact depending on the org)Now one key limit on OFFSET is that the maximum offset is 2000, so you’ll need to be paginating through a recordset smaller than that.
  • Aggregate searches allow a developer to do powerful mathematical searches against the database. In the example on the top here, you’ll get a count of merchandise by name for a specific invoice. Think of it like a highly customizable rollup field.The example on the bottom takes that same search, but shows you how it is split up. We’re summarizing an integer field, getting a child name field and then grouping it by that field. Here’s another example, where we can see how much a line item is worth by merchandise:SELECT SUM(Quantity__c) quantity, Merchandise__r.Name name from Line_Item__c Group By Merchandise__r.Name
  • The platform now supports geolocation. In order to do a dynamic search, like above, you’ll need to construct the string and then use a dynamic query. Using these queries, you could easily gather data based on physical location, for instance if you wanted to find the contact closest to where you parked.Here’s an example in the dev console:SELECT Name FROM Account WHERE DISTANCE(Location__c, GEOLOCATION(37.7945391,-122.3947166), 'mi') < 1
  • So SOSL isn’t exactly new – we’ve had in the system for some time. But if you are trying to search across different Sobject types, nothing beats it. Here we can find Tim even if he is a contact or account. Let’s look at an example in the Dev Console (in Execute Anonymous):List<List<SObject>> allResults = [FIND 'Tim' IN Name Fields RETURNING lead(id, name), contact(id, name, LastModifiedDate), account(id, name, LastModifiedDate), user(id, name, LastModifiedDate) LIMIT 5];System.debug(allResults);
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • Explain the ID trick, - for SOQL injection protection
  • Explain the ID trick, - for SOQL injection protection
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • Controller testing should also include page reference asserts if you are moving from page to page
  • We’re used to thinking about Visualforce as a component based library, and that let’s us create HTML based interfaces very quickly and easily by binding those components to data. But what about using those components to mix and match Visualforce across your instance?
  • For instance, you can use Visualforce to create very custom dashboards, and then put those on your homepage. Here’s an example I’ve got with the Warehouse app, which is showing recently created Invoices:( /home/home.jsp )Now if I click into one of those Invoices, we’re also seeing visualforce.
  • Because, and this is probably one of the more common use cases for Visualforce, anything with a Standard Controller can be used in place of the standard list, view, edit style pages. On this page, I’m still displaying the page layout via the detail component, but we wanted to be able to leverage a new footer across different detail pages(show WarehouseDetail
  • And we’re keeping that new detail consistent by using a template. We can define our inserts, and then define our content. This allows us to maintain a lot of different look and feels across different object types, but controlling the parts that will the same in one place.
  • And of course, as we customize that layout, we can create custom components which can take incoming attributes and then render what we need. For instance, in my footer I am using a visualization jQuery plugin called isotope, which allows us to view the line items in a very different way than the related list. You’ll see more about jQuery later.
  • And of course, if I want that Visualforce in the middle of my layout, I can use a StandardController to embed that right into it. In fact, in this layout – this section is not being generated here on Salesforce.
  • It’s actually 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.
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • Apex controllers are probably the most common use case for the language, but triggers merit a second place.
  • And with all of those potentials triggers in your system, they can easily get out of hand. There are a few best practices people have found to make them more maintainable.First, consider having only one trigger per object. Within the trigger class itself, break out every possible event, before and after, and start putting system.debugs around them. At the very least, this will make it very easy to track down in debug logs where the logic is getting fired.Second, consider handing off the actual logic to delegate classes. Send them the current scope of the trigger and let them sort it out. This will neatly divide the functionality that your trigger is trying to accomplish.
  • A delegate also gives you more breathing room. Look at all the variables we are using to properly track what this delegate wants to do – if you started stacking all the logic into the trigger itself, this will start to get unruly really fast. Don’t let your triggers become a battleground, they should be more like highways.
  • Another trick is using static variables in another class to track progress in your trigger. Changes to these flags will be visible for the span of the trigger context. So if, for instance, another process kicks off your trigger logic a second time, and you don’t want it to – you could swap the first flag here to true, and then not execute any logic if that flag is true.
  • And remember one of the more powerful uses of triggers is in association with Chatter. Let’s take a look at a Force.com labs app, Chatter Blacklist, which illustrates this very well.
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • Self Service case structure by Email
  • Update this subtitle
  • How does privacy work with Chatter? Can you accidentally share a record I’m not supposed to see?
  • statue
  • ELEVATE Advanced Workshop

    1. 1. Advanced Developer Workshop Joshua Birk Developer Evangelist @joshbirk joshua.birk@salesforce.com Sanjay Savani Solutions Engineer @efxfan ssavani@salesforce.com
    2. 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, 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.
    3. 3. Interactive Questions? Current projects? Feedback?
    4. 4. 1,000,000 Salesforce Platform Developers
    5. 5. 9 Billion API calls last month
    6. 6. 2.5x Increased demand for Force.com developers
    7. 7. YOU are the makers
    8. 8. BETA TESTING Warning: We’re trying something new
    9. 9. Editor Of Choice For the Eclipse fans in the room
    10. 10. Warehouse Data Model Merchandise Name Price Inventory Pinot $20 15 Cabernet $30 10 Malbec $20 20 Zinfandel $10 50 Invoice Number Status Count Total INV-01 Shipped 16 $370 INV-02 New 20 $200 Invoice Line Items Invoice 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
    11. 11. http://developer.force.com/join
    12. 12. Apex Unit Testing Platform level support for unit testing
    13. 13. Unit Testing  Assert all use cases  Maximize code coverage  Test early, test often o Logic without assertions o 75% is the target o Test right before deployment
    14. 14. Test Driven Development
    15. 15. Testing Context // this is where the context of your test begins Test.StartTest(); //execute future calls, batch apex, scheduled apex // this is where the context ends Text.StopTest(); System.assertEquals(a,b); //now begin assertions
    16. 16. Testing Permissions //Set up user User u1 = [SELECT Id FROM User WHERE Alias='auser']; //Run As U1 System.RunAs(u1){ //do stuff only u1 can do }
    17. 17. Static Resource Data List<Invoice__c> invoices = Test.loadData(Invoice__c.sObjectType, 'InvoiceData'); update invoices;
    18. 18. Mock HTTP @isTest global class MockHttp implements HttpCalloutMock { global HTTPResponse respond(HTTPRequest req) { // Create a fake response HttpResponse res = new HttpResponse(); res.setHeader('Content-Type', 'application/json'); res.setBody('{"foo":"bar"}'); res.setStatusCode(200); return res; } }
    19. 19. Mock HTTP @isTest private class CalloutClassTest { static void testCallout() { Test.setMock(HttpCalloutMock.class, new MockHttp()); HttpResponse res = CalloutClass.getInfoFromExternalService(); // Verify response received contains fake values String actualValue = res.getBody(); String expectedValue = '{"foo":"bar"}'; System.assertEquals(actualValue, expectedValue); } }
    20. 20. Unit Testing Tutorial http://bit.ly/dfc_adv_workbook
    21. 21. SOQL Salesforce Object Query Language
    22. 22. Indexed Fields • Primary Keys • Id • Name • OwnerId Using a query with two or more indexed filters greatly increases performance • Audit Dates • Created Date • Last Modified Date • Foreign Keys • Lookups • Master-Detail • CreatedBy • LastModifiedBy • External ID fields • Unique fields • Fields indexed by Saleforce
    23. 23. SOQL + Maps Map<Id,Id> accountFormMap = new Map<Id,Id>(); for (Client_Form__c form : [SELECT ID, Account__c FROM Client_Form__c WHERE Account__c in :accountFormMap.keySet()]) { accountFormMap.put(form.Account__c, form.Id); } Map<ID, Contact> m = new Map<ID, Contact>( [SELECT Id, LastName FROM Contact] );
    24. 24. Child Relationships List<Invoice__c> invoices = [SELECT Name, (SELECT Merchandise__r.Name from Line_Items__r) FROM Invoice__c]; List<Invoice__c> invoices = [SELECT Name, (SELECT Child_Field__c from Child_Relationship__r) FROM Invoice__c];
    25. 25. SOQL Loops public void massUpdate() { for (List<Contact> contacts: [SELECT FirstName, LastName FROM Contact]) { for(Contact c : contacts) { if (c.FirstName == 'Barbara' && c.LastName == 'Gordon') { c.LastName = 'Wayne'; } } update contacts; } }
    26. 26. ReadOnly <apex:page controller="SummaryStatsController" readOnly="true"> <p>Here is a statistic: {!veryLargeSummaryStat}</p> </apex:page> public class SummaryStatsController { public Integer getVeryLargeSummaryStat() { Integer closedOpportunityStats = [SELECT COUNT() FROM Opportunity WHERE Opportunity.IsClosed = true]; return closedOpportunityStats; } }
    27. 27. SOQL Polymorphism List<EVENT> events = [SELECT Subject, TYPEOF What WHEN Account THEN Phone, NumberOfEmployees WHEN Opportunity THEN Amount, CloseDate END FROM Event];
    28. 28. Offset SELECT Name FROM Merchandise__c WHERE Price__c > 5.0 ORDER BY Name LIMIT 10 OFFSET 0 SELECT Name FROM Merchandise__c WHERE Price__c > 5.0 ORDER BY Name LIMIT 10 OFFSET 10
    29. 29. AggregateResult List<AggregateResult> res = [ SELECT SUM(Line_Item_Total__c) total, Merchandise__r.Name name from Line_Item__c where Invoice__c = :id Group By Merchandise__r.Name ]; List<AggregateResult> res = [ SELECT SUM(INTEGER FIELD) total, Child_Relationship__r.Name name from Parent__c where Related_Field__c = :id Group By Child_Relationship__r.Name ];
    30. 30. Geolocation String q = 'SELECT ID, Name, ShippingStreet, ShippingCity from Account '; q+= 'WHERE DISTANCE(Location__c, GEOLOCATION('+String.valueOf(lat)'; q+= ','+String.valueOf(lng)+'), 'mi')'; q+= ' < 100'; accounts = Database.query(q);
    31. 31. SOSL List<List<SObject>> allResults = [FIND 'Tim' IN Name Fields RETURNING lead(id, name, LastModifiedDate WHERE LastModifiedDate > :oldestDate), contact(id, name, LastModifiedDate WHERE LastModifiedDate > :oldestDate), account(id, name, LastModifiedDate WHERE LastModifiedDate > :oldestDate), user(id, name, LastModifiedDate WHERE LastModifiedDate > :oldestDate) LIMIT 5];
    32. 32. Visualforce Controllers Apex for constructing dynamic pages
    33. 33. Viewstate Hashed information block to track server side transports
    34. 34. Reducing Viewstate //Transient data that does not get sent back, //reduces viewstate transient String userName {get; set;} //Static and/or private vars //also do not become part of the viewstate static private integer VERSION_NUMBER = 1;
    35. 35. Reducing Viewstate //Asynchronous JavaScript callback. No viewstate. //RemoteAction is static, so has no access to Controller context @RemoteAction public static Account retrieveAccount(ID accountId) { try { Account a = [SELECT ID, Name from ACCOUNT WHERE Id =:accountID LIMIT 1]; return a; } catch (DMLException e) { return null; } }
    36. 36. Handling Parameters //check the existence of the query parameter if(ApexPages.currentPage().getParameters().containsKey(„id‟)) { try { Id aid = ApexPages.currentPage().getParameters().get(„id‟); Account a = [SELECT Id, Name, BillingStreet FROM Account WHERE ID =: aid]; } catch(QueryException ex) { ApexPages.addMessage(new ApexPages.Message( ApexPages.Severity.FATAL, ex.getMessage())); return; } }
    37. 37. SOQL Injection String account_name = ApexPages.currentPage().getParameters().get('name'); account_name = String.escapeSingleQuotes(account_name); List<Account> accounts = Database.query('SELECT ID FROM Account WHERE Name = '+account_name);
    38. 38. Cookies //Cookie = //new Cookie(String name, String value, String path, // Integer milliseconds, Boolean isHTTPSOnly) public PageReference setCookies() { Cookie companyName = new Cookie('accountName','TestCo',null,315569260,false); ApexPages.currentPage().setCookies(new Cookie[]{companyName}); return null; } public String getCookieValue() { return ApexPages.currentPage(). getCookies().get('accountName').getValue(); }
    39. 39. Inheritance and Construction public with sharing class PageController implements SiteController { public PageController() { } public PageController(ApexPages.StandardController stc) { }
    40. 40. Controlling Redirect //Stay on same page return null; //New page, no Viewstate PageReference newPage = new Page.NewPage(); newPage.setRedirect(true); return newPage; //New page, retain Viewstate PageReference newPage = new Page.NewPage(); newPage.setRedirect(false); return newPage;
    41. 41. Unit Testing Pages //Set test page Test.setCurrentPage(Page.VisualforcePage); //Set test data Account a = new Account(Name='TestCo'); insert a; //Set test params ApexPages.currentPage().getParameters().put('id',a.Id); //Instatiate Controller SomeController controller = new SomeController(); //Make assertion System.assertEquals(controller.AccountId,a.Id)
    42. 42. Visualforce Components Embedding content across User Interfaces
    43. 43. Visualforce Dashboards <apex:page controller="retrieveCase" tabStyle="Case"> <apex:pageBlock> {!contactName}s Cases <apex:pageBlockTable value="{!cases}" var="c"> <apex:column value="{!c.status}"/> <apex:column value="{!c.subject}"/> </apex:pageBlockTable> </apex:pageBlock> </apex:page> Custom Controller Dashboard Widget
    44. 44. Page Overrides Select Override Define Override
    45. 45. Templates <apex:page controller="compositionExample"> <apex:form > <apex:insert name=”header" /> <br /> <apex:insert name=“body" /> Layout inserts Define with Composition <apex:composition template="myFormComposition <apex:define name=”header"> <apex:outputLabel value="Enter your favorite m <apex:inputText id=”title" value="{!mealField}" </apex:define> <h2>Page Content</h2>
    46. 46. <apex:component controller="WarehouseAccounts <apex:attribute name="lat" type="Decimal" descrip Query" assignTo="{!lat}"/> <apex:attribute name="long" type="Decimal" desc Geolocation Query" assignTo="{!lng}"/> <apex:pageBlock > Custom Components Define Attributes Assign to Apex public with sharing class WarehouseAccountsCont public Decimal lat {get; set;} public Decimal lng {get; set;} private List<Account> accounts; public WarehouseAccountsController() {}
    47. 47. Page Embeds Standard Controller Embed in Layout <apex:page StandardController=”Account” showHeader=“false” <apex:canvasApp developerName=“warehouseDev” applicationName=“procure”
    48. 48. Canvas Framework for using third party apps within Salesforce
    49. 49. 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 Canvas Anatomy
    50. 50. Non-HTML Visualforce Tutorial http://bit.ly/dfc_adv_workbook Geolocation Component Tutorial
    51. 51. jQuery Integration Visualforce with cross-browser DOM and event control
    52. 52. jQuery Projects DOM Manipulation Event Control UI Plugins Mobile Interfaces   
    53. 53. noConflict() + ready <script> j$ = jQuery.noConflict(); j$(document).ready(function() { //initialize our interface }); </script>  Keeps jQuery out of the $ function  Resolves conflicts with existing libs  Ready event = DOM is Ready
    54. 54. jQuery Functions j$('#accountDiv').html('New HTML');  Call Main jQuery function  Define DOM with CSS selectors  Perform actions via base jQuery methods or plugins
    55. 55. DOM Control accountDiv = j$(id*=idname); accountDiv.hide(); accountDiv.hide.removeClass('bDetailBlock'); accountDiv.hide.children().show(); //make this make sense  Call common functions  Manipulate CSS Directly  Interact with siblings and children  Partial CSS Selectors
    56. 56. Event Control j$(".pbHeader") .click(function() { j$(".pbSubsection”).toggle(); });  Add specific event handles bound to CSS selectors  Handle specific DOM element via this  Manipulate DOM based on current element, siblings or children
    57. 57. jQuery Plugins  iCanHaz  jqPlot  cometD  SlickGrid, jqGrid Moustache compatible client side templates Free charting library Flexible and powerful grid widgets Bayeux compatible Streaming API client
    58. 58. Streaming API Tutorial http://bit.ly/dfc_adv_workbook
    59. 59. LUNCH: Room 119 To the left, down the stairs
    60. 60. Apex Triggers Event based programmatic logic
    61. 61. Controlling Flow trigger LineItemTrigger on Line_Item__c (before insert, before update) { //separate before and after if(Trigger.isBefore) { //separate events if(Trigger.isInsert) { System.debug(„BEFORE INSERT‟); DelegateClass.performLogic(Trigger.new); //
    62. 62. Delegates public class BlacklistFilterDelegate { public static Integer FEED_POST = 1; public static Integer FEED_COMMENT = 2; public static Integer USER_STATUS = 3; List<PatternHelper> patterns {set; get;} Map<Id, PatternHelper> matchedPosts {set; get;} public BlacklistFilterDelegate() { patterns = new List<PatternHelper>(); matchedPosts = new Map<Id, PatternHelper>(); preparePatterns(); }
    63. 63. Static Flags public with sharing class AccUpdatesControl { // This class is used to set flag to prevent multiple calls public static boolean calledOnce = false; public static boolean ProdUpdateTrigger = false; }
    64. 64. Chatter Triggers trigger AddRegexTrigger on Blacklisted_Word__c (before insert, before update) { for (Blacklisted_Word__c f : trigger.new) { if(f.Custom_Expression__c != NULL) { f.Word__c = ''; f.Match_Whole_Words_Only__c = false; f.RegexValue__c = f.Custom_Expression__c; } else f.RegexValue__c = RegexHelper.toRegex(f.Word__c, f.Match_Whole_Words_Only__c); } }
    65. 65. Scheduled Apex Cron-like functionality to schedule Apex tasks
    66. 66. Schedulable Interface global with sharing class WarehouseUtil implements Schedulable { //General constructor global WarehouseUtil() {} //Scheduled execute global void execute(SchedulableContext ctx) { //Use static method for checking dated invoices WarehouseUtil.checkForDatedInvoices(); }
    67. 67. Schedulable Interface System.schedule('testSchedule','0 0 13 * * ?', new WarehouseUtil()); Via Apex Via Web UI
    68. 68. Batch Apex Functionality for Apex to run continuously in the background
    69. 69. Batchable Interface global with sharing class WarehouseUtil implements Database.Batchable<sObject> { //Batch execute interface global Database.QueryLocator start(Database.BatchableContext BC){ //setup SOQL for scope } global void execute(Database.BatchableContext BC, List<sObject> scope) { //Execute on current scope } global void finish(Database.BatchableContext BC) { //Finish and clean up context }
    70. 70. Unit Testing Test.StartTest(); ID batchprocessid = Database.executeBatch(new WarehouseUtil()); Test.StopTest();
    71. 71. Asynchronous Apex Tutorial De-duplication Trigger Tutorial http://bit.ly/dfc_adv_workbook
    72. 72. Apex Endpoints Exposing Apex methods via SOAP and REST
    73. 73. OAuth Industry standard method of user authentication
    74. 74. Remote Application Salesforce Platform Sends App Credentials User logs in, Token sent to callback Confirms token Send access token Maintain session with refresh token OAuth2 Flow
    75. 75. Apex SOAP global class MyWebService { webService static Id makeContact(String lastName, Account a) { Contact c = new Contact(lastName = 'Weissman', AccountId = a.Id); insert c; return c.id; } }
    76. 76. Apex REST @RestResource(urlMapping='/CaseManagement/v1/*') global with sharing class CaseMgmtService { @HttpPost global static String attachPic(){ RestRequest req = RestContext.request; RestResponse res = Restcontext.response; Id caseId = req.requestURI.substring(req.requestURI.lastIndexOf('/')+1); Blob picture = req.requestBody; Attachment a = new Attachment (ParentId = caseId, Body = picture, ContentType = 'image/
    77. 77. Apex Email Classes to handle both incoming and outgoing email
    78. 78. Outgoing Email Messaging.SingleEmailMessage mail = new Messaging.SingleEmailMessage(); String body = count+' closed records older than 90 days have been deleted'; //Set addresses based on label mail.setToAddresses(Label.emaillist.split(',')); mail.setSubject ('[Warehouse] Dated Invoices'); mail.setPlainTextBody(body); //Send the email Messaging.SendEmailResult [] r = Messaging.sendEmail(new Messaging.SingleEmailMessage[] {mail});
    79. 79. Incoming Email global class PageHitsController implements Messaging.InboundEmailHandler { global Messaging.InboundEmailResult handleInboundEmail( Messaging.inboundEmail email, Messaging.InboundEnvelope env) { if(email.textAttachments.size() > 0) { Messaging.InboundEmail.TextAttachment csvDoc = email.textAttachments[0]; PageHitsController.uploadCSVData(csvDoc.body); } Messaging.InboundEmailResult result = new Messaging.InboundEmailResult(); result.success = true; return result; }
    80. 80. Incoming Email Define Service Limit Accepts
    81. 81. Custom Endpoint Tutorial http://bit.ly/dfc_adv_workbook
    82. 82. Team Development Tools for teams and build masters
    83. 83. Metadata API API to access customizations to the Force.com platform
    84. 84. Migration Tool Ant based tool for deploying Force.com applications
    85. 85. Continuous Integration Source Control Sandbox CI Tool DE Fail Notifications Development Testing
    86. 86. Tooling API Access, create and edit Force.com application code
    87. 87. Polyglot Framework PaaS allowing for the deployment of multiple languages
    88. 88. Heroku Integration Tutorial http://bit.ly/dfc_adv_workbook
    89. 89. Double-click to enter title Double-click to enter text The Wrap Up
    90. 90. check inbox || http://bit.ly/elevatela13
    91. 91. Double-click to enter title Double-click to enter text @forcedotcom @joshbirk @metadaddy #forcedotcom
    92. 92. Double-click to enter title Double-click to enter text Join A Developer User Group http://bit.ly/fdc-dugs LA DUG: http://www.meetup.com/Los-Angeles- Force-com-Developer-Group/ Leader: Nathan Pepper
    93. 93. Double-click to enter title Double-click to enter text Become A Developer User Group Leader Email: April Nassi <anassi@salesforce.com>
    94. 94. Double-click to enter title Double-click to enter text http://developer.force.com http://www.slideshare.net/inkless/ elevate-advanced-workshop
    95. 95. simplicity is the ultimate form of sophistication Da Vinci
    96. 96. Thank You Joshua Birk Developer Evangelist @joshbirk joshua.birk@salesforce.com Matthew Reiser Solution Architect @Matthew_Reiser mreiser@salesforce.com

    ×