CloudSense.com
@CloudSense
+44 20 7580 6685
Leveraging Force.com: When, Why & How?
Implementation Best Practices
Your presenters
Fawzi Fares
Enterprise Solutions Director & Co-
Founder
Salesforce Certified Technical Architect
Davor Dub...
100%
cloud native
Triple digit year
on year growth
Media &
telecoms
heritage
9.5/10
customer satisfaction
141
certificatio...
Proven in large enterprise
Our awardsOur customers
Salesforce platform experience
What is the Salesforce1 Platform?
Sales Cloud Service Cloud Marketing Cloud AppExchange
Salesforce1 Platform APIs
Salesfor...
Key platform uses
Heroku
High volume B2C
Integrations
Mixed technologies
Analytics & number crunching
Force.com
Employee a...
• Environments
• Source code control
• Deployment / testing automation
• Configuration before customisation
• Development ...
• Developer sandbox (one or
more)
• Systems integration sandbox
• User acceptance testing
• Pre-production
• Training
• Pr...
Source code control
How many developers?
How many streams of work?
The repository is the source of truth
Not only code (in...
Deployment & testing automation
ANT build tool provided by Salesforce
Deploy from the source code repository ONLY
Regular ...
• Building object model (Auto-generated CRUD
pages)
• Workflow (emails, tasks, field updates,
integration)
• Approval proc...
• Extend out-of-the-box features (don’t replace
them)
• Write your code ensuring it handles bulk
transactions
• Take advan...
Integration
Use the “Generate From WSDL” platform service
Test your integrations thoroughly
You can consume Webservices vi...
• User profiles
• Organisation-wide sharing model
• Role hierarchy
• License types & feature access requirements
Security
...
• Look to reuse before building
• Look at configurability not only
features
• Look for product roadmap
• Look for product ...
Saba, CloudSense since 2011
Case Study:
BBC 500 Words Competition
• Competition microsite
• Salesforce sites based
• Competition lifecycle automation
• Full security & privacy compliance
•...
• Bespoke look and feel required on
sites
• Need to distribute stories between
teachers evenly
• Story assignment is gover...
• Integrated to a Webservice to
provide standard look and
feel elements
• Header & footer
• Standard widgets (e.g. live
ra...
Site domain
• Reverse proxy
• URL writing
• Page rewriting
Site administration
• Site availability is configurable
using date ranges
• Approval of teachers
• Approval of stories for...
Richard, CloudSense since 2009
Summary
What to take away?
Control
• Environments (Dev, SIT, UAT, Training, PreProd, Production)
• Source code
• Deployment automa...
CloudSense.com
@CloudSense
+44 20 7580 6685
Thank you
For further questions reach
us at:
Upcoming SlideShare
Loading in …5
×

Leveraging Force.com: What, Why & Hows?

1,414 views

Published on

Practical advice for using Force.com, CloudSense share their recommendations and best practice for implementation of Force.com. Featuring the CloudSense case study with the BBC 500 words competition.

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

No Downloads
Views
Total views
1,414
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
40
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • CloudSense at a Glance - We have grown rapidly with last year achieving over $10m revenue and over 115 people delivering 9.5 out of 10 customer satisfaction. Our focus & heritage is both in B2C & B2B
  • Our Heritage - As you can see we have a strong track record in Enterprise size companies. We have already been recognised with awards and here is a selection from the last 6 months.
  • Discuss the different characteristics between the platforms – scaling approaches, multi-tenancy & elasticity, depth of stack
    Force.com stack, Heroku offers multiple technology options
    Possible name confusion between the Salesforce1 app and the platform
  • What are they suited to?

    Build anything.

    Some typical use cases. Not exclusive.

    Force.com: the hub. Run your business on it. All employees should have access. Join up a complete view of your customer – from social media through to in-life services and billing records. Rich platform provides out of the box reporting, dashboards, rapid app development, easy deployment across desktop and mobile

    Heroku: cut your cloth to fit. Incorporate heterogeneous technologies leveraging best in class existing tools for Java, Ruby, Node.js

  • Leveraging Force.com: What, Why & Hows?

    1. 1. CloudSense.com @CloudSense +44 20 7580 6685 Leveraging Force.com: When, Why & How? Implementation Best Practices
    2. 2. Your presenters Fawzi Fares Enterprise Solutions Director & Co- Founder Salesforce Certified Technical Architect Davor Dubokovic Shared Services Director & Co-Founder
    3. 3. 100% cloud native Triple digit year on year growth Media & telecoms heritage 9.5/10 customer satisfaction 141 certifications 150+ people across Europe B2B & B2C success Multi-device Salesforce Platinum Partner Experts in multi-channel environments Award winning Founded in 2009
    4. 4. Proven in large enterprise Our awardsOur customers
    5. 5. Salesforce platform experience
    6. 6. What is the Salesforce1 Platform? Sales Cloud Service Cloud Marketing Cloud AppExchange Salesforce1 Platform APIs Salesforce1 Platform services
    7. 7. Key platform uses Heroku High volume B2C Integrations Mixed technologies Analytics & number crunching Force.com Employee access Single view of the customer Rich platform facilities Apps
    8. 8. • Environments • Source code control • Deployment / testing automation • Configuration before customisation • Development considerations • Integration considerations • Security Build on solid foundations
    9. 9. • Developer sandbox (one or more) • Systems integration sandbox • User acceptance testing • Pre-production • Training • Production Environments
    10. 10. Source code control How many developers? How many streams of work? The repository is the source of truth Not only code (include configuration metadata) Not an after thought GIT Subversion Mercurial Perforce
    11. 11. Deployment & testing automation ANT build tool provided by Salesforce Deploy from the source code repository ONLY Regular scheduled deployments to an integration sandbox Automate a regression testing harness Never make changes directly to production Automate deployment of code and configuration Jenkins Selenium
    12. 12. • Building object model (Auto-generated CRUD pages) • Workflow (emails, tasks, field updates, integration) • Approval processes • Record types • Custom settings • Profile security and data sharing model • Partner and customer communities Configuration before customisation There are some exceptions to this rule
    13. 13. • Extend out-of-the-box features (don’t replace them) • Write your code ensuring it handles bulk transactions • Take advantage of built-in SOQL features • Build your code with security in mind • Take care of memory usage on your pages • Take care of recurring triggers • Use custom settings to make your code configurable Development considerations Develop with governor limits in mind
    14. 14. Integration Use the “Generate From WSDL” platform service Test your integrations thoroughly You can consume Webservices via HTTP requests Expose APEX Webservices where appropriate Consider the use of middleware as integration layers Use outbound workflow messages when you can Don’t forget the standard Salesforce API’s Informatica CastIron Tibco JitterBit
    15. 15. • User profiles • Organisation-wide sharing model • Role hierarchy • License types & feature access requirements Security Don’t forget your reporting requirements
    16. 16. • Look to reuse before building • Look at configurability not only features • Look for product roadmap • Look for product support • Look for implementation support AppExchange Consider modifying your business processes to fit in with industry best practice
    17. 17. Saba, CloudSense since 2011 Case Study: BBC 500 Words Competition
    18. 18. • Competition microsite • Salesforce sites based • Competition lifecycle automation • Full security & privacy compliance • Gather story entries • Manage teachers & librarians • Track flow of entries and capture scoring Background
    19. 19. • Bespoke look and feel required on sites • Need to distribute stories between teachers evenly • Story assignment is governed by data access rules • Large daily volumes of emails to be sent from the system • The site had to be part of the bbc.co.uk sub-domain Key challenges
    20. 20. • Integrated to a Webservice to provide standard look and feel elements • Header & footer • Standard widgets (e.g. live radio streaming) • Standard content and menus • Pictures & banners Look & feel
    21. 21. Site domain • Reverse proxy • URL writing • Page rewriting
    22. 22. Site administration • Site availability is configurable using date ranges • Approval of teachers • Approval of stories for suspicious content • Reports and dashboards
    23. 23. Richard, CloudSense since 2009 Summary
    24. 24. What to take away? Control • Environments (Dev, SIT, UAT, Training, PreProd, Production) • Source code • Deployment automation • Regression testing automation Configure • Configure before customise • Extend standard functionality do not attempt to replace it Standards • Apply development standards • Use governor limits to your advantage • Enforce proper unit testing not just code coverage
    25. 25. CloudSense.com @CloudSense +44 20 7580 6685 Thank you For further questions reach us at:

    ×