Designing Salesforce Mobile Workflow Using Force.com (Apex) Triggers <br />Developers Track<br />Paolo Bergamo: salesforce...
Safe Harbor<br />Safe harbor statement under the Private Securities Litigation Reform Act of 1995: This presentation may c...
Agenda<br />Overview of Salesforce Mobile<br />Why choose Salesforce Mobile and demo<br />Examples of Force.com triggers t...
Overview of  Salesforce Mobile<br />
In The Future…<br />Salesforce apps all in one place<br /><ul><li> Suite of mobile apps available at m.salesforce.com
 Distributed through app stores
 Purpose-built apps solve specific problems
 Full integration with Salesforce
 Easy to find, download and use</li></li></ul><li>SalesforceMobile<br />Chatter Mobile<br />Mobile Products Today<br />
Instant access to customer data<br />Update records between appointments<br />Improve data and pipeline visibility<br />Sa...
Current Mobile Offerings<br />
SalesforceMobile Demo<br />
Write once, run everywhere<br />Crossplatformsupport<br />Security taken care of<br />Offline access<br />Ease of deployme...
SalesforceMobile demo<br />
SalesforceMobile overview<br />Overview of the client<br /><ul><li> Basic navigation
 Search / filter
 Integration with the OS (Log a call, etc)
 Dashboards and Visualforce Pages</li></ul>Administration<br /><ul><li> Application update
 What if the the device is lost or stolen</li></li></ul><li>SalesforceMobile and Triggers<br />
Parent/Child creation is not supported offline <br />record ID missing<br />New Account<br /><ul><li>New related contact</...
Offline Parent/Child creation: Solution #1<br />Use a “flattened” mirror object<br />Field1<br />Field2<br />Parent.Field1...
Offline Parent/Child creation: use case #2<br />Visit of a distributor to a store<br />Account<br />Visit January <br />Vi...
Offline Parent/Child creation: Solution #2<br />Create the parent object for next visit<br />Account<br />Visit Completed<...
Approval process: use case<br />Manager needs to approve an object<br />
Approval process: solution<br />Two different layouts<br />Start date<br /># of days<br />Start date<br /># of days<br />S...
Approval process: credit card validation use case<br />Salesforce Mobile on Windows Mobile:<br />peripherals integration<b...
Credit card information: solution<br />Let the server-side deal with validation<br />Credit Card company validation<br />
Credit card information: solution<br />Let the server-side deal with validation and copy the field into an encrypted field...
Upcoming SlideShare
Loading in …5
×

Designing Mobile Workflow Using Force.com (Apex) Triggers

2,005 views

Published on

Looking for an efficient mobile workflow? It's time to reach new heights in mobile productivity using Force.com (Apex) triggers with salesforce.com's mobile application. Join us to learn how to leverage picklists, booleans, and other fields to mobile-enable advanced tasks such as calculating an invoice total and generating a quote directly from a mobile device.

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

No Downloads
Views
Total views
2,005
On SlideShare
0
From Embeds
0
Number of Embeds
272
Actions
Shares
0
Downloads
44
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • • Two products: Salesforce Mobile and Chatter Mobile• Focus today on Salesforce Mobile – Single app that’s used for Service Cloud Mobile, Sales Cloud Mobile deployments• Though Chatter Mobile possibilities are great – leveraging experts, uploading photos, logging updates – not yet optimized for Service Cloud
  • Designing Mobile Workflow Using Force.com (Apex) Triggers

    1. 1. Designing Salesforce Mobile Workflow Using Force.com (Apex) Triggers <br />Developers Track<br />Paolo Bergamo: salesforce.com<br />
    2. 2. Safe Harbor<br />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.<br />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 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-K for the most recent fiscal year ended January 31, 2010. This documents and others are available on the SEC Filings section of the Investor Information section of our Web site. <br />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.<br />
    3. 3. Agenda<br />Overview of Salesforce Mobile<br />Why choose Salesforce Mobile and demo<br />Examples of Force.com triggers to be used with mobile<br />
    4. 4. Overview of Salesforce Mobile<br />
    5. 5. In The Future…<br />Salesforce apps all in one place<br /><ul><li> Suite of mobile apps available at m.salesforce.com
    6. 6. Distributed through app stores
    7. 7. Purpose-built apps solve specific problems
    8. 8. Full integration with Salesforce
    9. 9. Easy to find, download and use</li></li></ul><li>SalesforceMobile<br />Chatter Mobile<br />Mobile Products Today<br />
    10. 10. Instant access to customer data<br />Update records between appointments<br />Improve data and pipeline visibility<br />Salesforce Mobile: Take CRM Anywhere<br />
    11. 11. Current Mobile Offerings<br />
    12. 12. SalesforceMobile Demo<br />
    13. 13. Write once, run everywhere<br />Crossplatformsupport<br />Security taken care of<br />Offline access<br />Ease of deployment and update<br />SalesforceMobile: why?<br />
    14. 14. SalesforceMobile demo<br />
    15. 15. SalesforceMobile overview<br />Overview of the client<br /><ul><li> Basic navigation
    16. 16. Search / filter
    17. 17. Integration with the OS (Log a call, etc)
    18. 18. Dashboards and Visualforce Pages</li></ul>Administration<br /><ul><li> Application update
    19. 19. What if the the device is lost or stolen</li></li></ul><li>SalesforceMobile and Triggers<br />
    20. 20. Parent/Child creation is not supported offline <br />record ID missing<br />New Account<br /><ul><li>New related contact</li></li></ul><li>Offline Parent/Child creation: use case #1<br />Opportunity Line Item<br />Field1<br />Field2<br />Parent.Field1<br />Parent.Field2<br />Child.Field1<br />Child.Field2<br />Parent<br />Helper<br />Field1<br />Field2<br />Child<br /><make this pretty><br />
    21. 21. Offline Parent/Child creation: Solution #1<br />Use a “flattened” mirror object<br />Field1<br />Field2<br />Parent.Field1<br />Parent.Field2<br />Child.Field1<br />Child.Field2<br />Parent<br />Helper<br />Field1<br />Field2<br />Child<br />
    22. 22. Offline Parent/Child creation: use case #2<br />Visit of a distributor to a store<br />Account<br />Visit January <br />Visit February<br />Visit March<br />Questionnaire<br />recordType #3 <br />Questionnaire<br />recordType #1 <br />Questionnaire<br />recordType #2 <br />
    23. 23. Offline Parent/Child creation: Solution #2<br />Create the parent object for next visit<br />Account<br />Visit Completed<br />Questionnaire<br />recordType #1 <br />Visit Pending<br />New visit Pending<br />
    24. 24. Approval process: use case<br />Manager needs to approve an object<br />
    25. 25. Approval process: solution<br />Two different layouts<br />Start date<br /># of days<br />Start date<br /># of days<br />Status<br />Employee Layout<br />Manager Layout<br />
    26. 26. Approval process: credit card validation use case<br />Salesforce Mobile on Windows Mobile:<br />peripherals integration<br />New types of fields: MagneticStripe and BarCode<br />New types of objects: AllowSignature<br />PictureUploadas a related object<br />WM Peripherals Implementation Guide<br />
    27. 27. Credit card information: solution<br />Let the server-side deal with validation<br />Credit Card company validation<br />
    28. 28. Credit card information: solution<br />Let the server-side deal with validation and copy the field into an encrypted field, then lock the original record<br />Copy info to encrypted field<br />Create credit card record<br />(swipe)<br />Signature capture (via stylus and touch screen)<br /><ul><li>Lock record
    29. 29. Send email with receipt
    30. 30. Trigger other workflows</li></ul>Mask CC info on original record<br />CC validation<br />
    31. 31. Validation: use case<br />Complex validation rules that require (or not) apex code<br />Confirm record<br /><ul><li>Validation rules
    32. 32. Apex Code</li></ul>New record<br />OK<br />Not OK<br />Send record back to device in edit mode<br />
    33. 33. Summary<br />
    34. 34. Agenda<br />Why use Salesforce Mobile<br />crossplatform runtime that offers offline capabilities<br />Examples of triggers<br />Offline creation<br />Integration with peripherals<br />Approvals<br />Simple and complex validation rules<br />Salesforce Mobile offers a lot more!<br />
    35. 35. Thank you!<br />
    36. 36. How Could Dreamforce Be Better? Tell Us!<br />Log in to the Dreamforce app to submit<br />surveys for the sessions you attended<br />Use the Dreamforce Mobile app to submit surveys<br />OR<br />Every session survey you submit is a chance to win an iPod nano!<br />

    ×