Date post: | 15-Jan-2015 |
Category: |
Technology |
Upload: | cloudsense |
View: | 238 times |
Download: | 2 times |
CloudSense.com
@CloudSense
+44 20 7580 6685
Leveraging Force.com: When, Why & How?
Implementation Best Practices
Your presenters
Fawzi FaresEnterprise Solutions Director & Co-FounderSalesforce Certified Technical Architect
Davor DubokovicShared Services Director & Co-Founder
100%cloud native
Triple digit year on year
growth
Media & telecoms heritage
9.5/10customer satisfaction
141certifications
150+ peopleacross Europe
B2B & B2C success
Multi-device
Salesforce Platinum Partner
Experts in multi-channel environments
Award winning
Founded in 2009
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
Salesforce1 Platform services
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
• Environments • Source code control• Deployment / testing automation• Configuration before customisation• Development considerations• Integration considerations• Security
Build on solid foundations
• Developer sandbox (one or more)
• Systems integration sandbox
• User acceptance testing• Pre-production• Training• Production
Environments
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
Deployment & testing automation
ANT build tool provided by Salesforce
Deploy from the source code repository ONLY
Regular scheduled deployments to an integration sandboxAutomate a regression testing harness
Never make changes directly to production
Automate deployment of code and configuration
Jenkins Selenium
• 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
• 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
Integration
Use the “Generate From WSDL” platform service Test your integrations thoroughly
You can consume Webservices via HTTP requestsExpose 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
• User profiles• Organisation-wide sharing model• Role hierarchy• License types & feature access requirements
Security
Don’t forget your reporting requirements
• 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
Saba, CloudSense since 2011
Case Study:BBC 500 Words Competition
• 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
• 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
• 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
Site domain
• Reverse proxy• URL writing• Page rewriting
Site administration
• Site availability is configurable using date ranges
• Approval of teachers • Approval of stories for
suspicious content• Reports and dashboards
Richard, CloudSense since 2009
Summary
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
CloudSense.com
@CloudSense
+44 20 7580 6685
Thank you
For further questions reach us at: