Slides for ELEVATE Workshop à Paris 3 avril, 2014.

1. Advanced Developer
Workshop
Peter Chittum
Developer Evangelist
@pchittum
pchittum@salesforce.com
Hervé Maleville
Platform Architect
@hmaleville
herve.maleville@salesforce.com

2. Wifi Access
SSID: Guest
Password: fBSuBLqe
http://bit.ly/elevate_adv_workbook
Login and Get Ready

3. Be Interactive

4. Free Developer
Environment
http://developer.force.com/join

5. 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.

6. Nos prochains évènements à Paris!
Salesforce1 Tour à Paris
Webinar en Français: Data Model & Relationships
Prenez le lead sur notre communauté de Développeurs en France !
Plus d‟information sur www.developer.salesforce.com
June
26th
April
29th
A vous
de jouer

7. Core
Services
Chatt
er
Multi-
langua
ge
Translati
on
Workben
ch
Email
Servic
es
Analyti
cs
Cloud
Databa
se
Schee
ma
Builder
Sear
ch
Visualfo
rce
Monitori
ng
Multi-
tenant
Ape
x
Data-
level
Securit
y
Workflo
ws
APIs
Mobile
Services
Soci
al
APIs
Analyti
cs
APIs
Bulk
APIs
Rest
APIs
Metada
ta
APIs
Soap
APIs
Private
App
Exchang
e
Custo
m
Action
s
Identi
ty
Mobile
Notificati
ons
Tooli
ng
APIs
Mobile
Packs
Mobile
SDK
Offline
Support
Streami
ng
APIs
Geolocat
ion
ET 1:1
ET
Fuel
Heroku1
Heroku
Add-
Ons
Sharin
g
Model
ET API
Salesforce1 Platform

8. Salesforce is a Platform Company. Period.
-Alex Williams, TechCrunch
600MAPI Calls
Per Day
6BLines of Apex
4M+Apps Built on
the Platform
72BRecords
Stored
Salesforce1 Platform

9. 1.5 Million

10. Editor Of Choice
For the Eclipse fans in the room

12. 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

13. 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

14. Apex

15. Introduction to Apex
 Object-Oriented Language
 Dot Notation Syntax
 Case Insenstive
 “First Class” Citizen on the Platform

16. Apex Anatomy
Chapter 1:
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;
}
}
Class and Interface based
Scoped Variables


Inline SOQL
Inline DML



17. Developer Console
 Browser Based IDE
 Create and Edit Classes
 Create and Edit Triggers
 Run Unit Tests
 Review Debug Logs

18. Apex Triggers
 Event Based Logic
 Associated with Object
Types
 Before or After:
 Insert
 Update
 Delete
 Undelete

19. 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);

20. Static Flags
public with sharing class AccUpdatesControl {
// This class is used to prevent multiple calls
public static boolean calledOnce = false;
public static boolean ProdUpdateTrigger = false;
}

21. 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;
}
}
}

22. Trigger Tutorial
 Basic: Tutorial 2
 Intermediate: Tutorial 4
 Beyond Intermediate: http://bit.ly/ELEV-triggers
http://bit.ly/elevate_adv_workbook

23. Unit Testing in Apex
 Built in support for testing
– Test Utility Class Annotation
– Test Method Annotation
– Test Data build up and tear down
 Unit test coverage is required
– Must have at least 75% of code covered
 Why is it required?

24. Unit Testing
• Declare Classes/Code as
Test
• isTest Annotation
• testmethod keyword
• Default data scope is test
only

25. 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

26. 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
}

27. Static Resource Data
List<Invoice__c> invoices = Test.loadData(Invoice__c.sObjectType,
'InvoiceData');
update invoices;

28. Mock HTTP Endpoints
@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;
}
}

29. Mock HTTP Endpoints
@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);
}
}

30. Unit Testing Tutorial

31. Batch Apex

32. Apex Batch Processing
 Governor Limits
– Various limitations around resource usage
 Asynchronous processing
– Send your job to a queue and we promise to run it
 Can be scheduled to run later
– Kind of like a chron job

33. Batchable Interface
global with sharing class WHUtil implements Database.Batchable<sObject>
{
global Database.QueryLocator start(Database.BatchableContext BC)
{ //Start on next context }
global void execute(Database.BatchableContext BC, List<sObject> scope)
{ //Execute on current scope }
global void finish(Database.BatchableContext BC)
{ //Finish and clean up context }
}

34. Implementing Apex Batch Processing
Apex Batch Processing Tutorial

35. Scheduled Apex

36. 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();
}
}

37. Schedulable Interface
System.schedule('testSchedule','0 0 13 * * ?',
new WarehouseUtil());
Via Apex
Via Web UI

38. Unit Testing Batch Apex
Test.StartTest();
System.schedule(‘once','0 0 13 * * ?',new,WarehouseUtil());
ID batchprocessid = Database.executeBatch(new WarehouseUtil());
Test.StopTest();

39. Scheduling Apex
Apex Scheduling Tutorial

40. Apex REST Services

41. 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/

42. Apex REST Services
REST Services with Apex Tutorial

43. Visualforce

44. Framework
 Server-side compiled web pages
– (Think PHP, JSP, etc.)
 Easily create salesforce UI
 Standard-compliant
 Can Interact With Apex for Custom Logic

45. Visualforce Tags
<apex:page docType=“html-5.0” />
<apex:input type=“email”/>
<apex:pageBlockSection collapsible=“false” />

46. Hashed information block to track server side transports
Viewstate

47. Apex Form
 Required for standard salesforce post
 Incurs Viewstate Overhead
<apex:form>
…
</apex:form
aspdoifuapknva894372h
4ofincao98vh0q938hfoq
iwnbdco8q73h0o9fqubov
ilbodfubqo3e8ufbw

48. Interacting with Apex
 ActionFunction allows direct binding of variables
 ActionFunction requires ViewState
 JavaScript Remoting binds to static methods
 JavaScript Remoting uses no ViewState
 Transient, Private and Static reduce Viewstate

49. Apex Remote Action
 Static
 No View State
 Invoked through JS API
 Invokes JS Callback
@remoteAction
global static String myMethod(String
inputParam){
...
}

50. Calling Apex Remote Action
Visualforce.remoting.Manager.invokeAction(’
{!$RemoteAction.RemoteClass.methodName}'
,
param,
function(result, event) {
//...callback to handle result
});

51. Event Object: Success Example
{
"statusCode":200,
"type":"rpc",
"ref":false,
"action":"IncidentReport",
"method":"createIncidentReport",
"result":"a072000000pt1ZLAAY",
"status":true
}

52. Event Object: Failure Example
{
"statusCode":400,
"type":"exception",
"action":"IncidentReport",
"method":"createIncidentReport",
"message":"List has more than 1 row for assignment to SObject",
"data": {"0":
{"Merchandise__c":"a052000000GUgYgAAL","Type__c":"Accident","Desc
ription__c":"This is an accident report"}},
"result":null,
"status":false
}

53. Interacting with the Publisher: Allow Submit
 Make Submit Active
 Payload true/false
Sfdc.canvas.publisher.publish(
{
name: "publisher.setValidForSubmit",
payload:true
});

54. Interacting with the Publisher: Subscribe to Submit
 Attach to Submit Event
Sfdc.canvas.publisher.subscribe({
name: "publisher.post",
onData:function(e) {
// This subscribe fires when the user hits 'Submit'
in the publisher
postToFeed();
}});

55. Interacting with the Publisher: Close Publisher
 Make the Submit Happen
Sfdc.canvas.publisher.publish({name:
"publisher.close", payload:
{ refresh:"true"}});

56. The Future! (Well, Spring „14)

57. Remote Objects
 Standard CRUD/Q functionality without Apex
 Similar to remoteTK or SObjectData
 Visualforce components define data models
<apex:jsSObjectBase shortcut="tickets">
<apex:jsSObjectModel name="Ticket__c" />
<apex:jsSObjectModel name="Contact" fields="Email" />
<script>
var contact = new tickets.Contact();
contact.retrieve({
where: {
Email: {
like: query + '%'
}
}
}, function(err, data) {

58. Canvas

59.  Only has to be accessible from the user‟s
browser
 Authentication via OAuth or Signed
Response
 JavaScript based SDK
 Within Canvas, the App can make API calls
as the current user
 apex:CanvasApp allows embedding via
Visualforce
Any Language, Any Platform
How Canvas Works

60. OAuth

61. 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 Authentication Flow

63. Tools for teams and build masters
Team Development

64. API to access customizations to the Force.com platform
Metadata API

65. Access, create and edit Force.com application code
Tooling API

66. Double-click to enter title
Double-click to enter text
The Wrap Up

67. Nos prochains évènements à Paris!
Salesforce1 Tour à Paris
Webinar en Français: Data Model & Relationships
Prenez le lead sur notre communauté de Développeurs en France !
Plus d‟information sur www.developer.salesforce.com
June
26th
April
29th
A vous
de jouer

68. Questionnaire en ligne
Répondre au questionnaire en ligne sur cet
ELEVATE: http://bit.ly/elevateFR

69. check inbox
http://bit.ly/elevateFR

70. Double-click to enter title
Double-click to enter text
@forcedotcom
@pchittum
@dcarroll
#forcedotcom

71. Double-click to enter title
Double-click to enter text
Join A
Developer User Group
http://bit.ly/fdc-dugs
PARIS DUG:
http://www.meetup.com/Paris-
Salesforce-Developer-User-Group/
Leader: Mohamed EL MOUSSAOUI

72. Double-click to enter title
Double-click to enter text
Become A
Developer User Group Leader
Email:
April Nassi
<anassi@salesforce.com>

73. Thank You
Peter Chittum
Developer Evangelist
@pchittum
pchittum@salesforce.com
Hervé Maleville
Platform Architect
@hmaleville
herve.maleville@salesforce.com