A mini framework for event handling on the OpportunityContactRole (OCR) and AccountContactRole (ACR) objects. Using a custom (dynamic) Visualforce page driven by a controller extension, you can replace the standard related lists

1. Custom Event Handling with
Visualforce
Opportunity Contact Roles
Ritesh Aswaney, Technical Solution Architect, salesforce.com
@techtrekker

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 product or service availability, 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, new products and services, 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 any
litigation, risks associated with completed and any 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 and in our quarterly report on Form 10-Q for the most recent
fiscal quarter. These documents and others containing important disclosures 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 presentations, 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. Ritesh Aswaney
Technical Solution Architect
@techtrekker

4. About : me
Technical Solution Architect
§ Salesforce Services
• Based in London
• Certified Advanced Developer
• On the Road to CTA
§ Experience
• 10 years of Enterprise Software
• 4 years of working on the Force.com Platform
• StackExchange junkie

5. Second among equals
Object Types
§ ‘First Class’ Objects
• Triggers, Workflow
• Custom Fields
§ Non ‘First Class’ Objects
• No Triggers or Workflow
• ‘Junction’ Objects
• No Custom Fields

6. Business Need
Junction Objects model real world business relationships, hotbed
of custom business logic
§ Opportunity / Account Contact Role
• Sales Team need to know if Business Decision Maker Changes
• Downstream Systems notified of changes in OCR
§ Account Team
• Custom Business Logic when people are added to Account Teams

7. Solution Option 1: Custom Junction Object
§ Lose OOTB functionality such as sharing with teams
§ Triggers, Workflow can be created
§ Custom Fields can be added
§ Overhead of keeping (Custom & Standard Object) records in sync

8. Solution Option 2: Custom Visualforce Section
§ Retain OOTB functionality
§ ‘Touch’ Parent Object and update custom field
§ Multiplex Triggers, Wokflows to cater for Junction Objects
§ Integration Hooks to trigger Outbound Messages to External Systems

9. Meet the Paramters
§ saveURL
• Redirect to this URL when a user hits Save
§ retURL
• Redirect to this URL when a user hits Cancel
§ https://cs1.salesforce.com/02Z/e?retURL=
%2FRECORD_ID&saveURL=/apex/VF_PAGE_NAME

10. Solution Design : How does it flow

11. Demo

12. Solution Elements : URL Decoration
$j( 'input[type="button"]', this ).each(function()
$j( this ).attr('onclick', "window.parent.location=" + onclicklink +
"&saveURL=/apex/SavePage?actionURI={!objId}_" + rlName + "';");!
});!
!
$j( 'a.actionLink', this ).each(function() {!
onClickUrl += '&saveURL=/apex/SavePage?actionURI={!objId}_'+ rlName;!
$j( this ).attr('onclick', "window.parent.location='" + onClickUrl +
"'" ); });!
!

13. Solution Elements : Save Handler
String[] tokens = actionURI.split('_');!
Id entityId = tokens[0];!
String relatedList = tokens[1];!
!
if(entityId.getSObjectType() == Opportunity.sObjectType){!
! !if(relatedList == 'Contact Roles')!
handleOpportunityContactRole(entityId); //callback!
else if(relatedList == 'Opportunity Team')!
handleOpportunityTeam(entityId); //callback!
!
}!

14. Solution Element: Visualforce Event Handler Page
§ Invoking Apex Code (Controller) on Page Load
§ Use action attribute
<apex:page action="{!handleOnLoad}"
controller="SavePageCon”>

15. Solution Elements : Dynamic Visualforce Controller
if(objId.getSObjectType() == Opportunity.sObjectType)!
!Schema.DescribeSObjectResult R =!
!Opportunity.SObjectType.getDescribe();!
!
List<Schema.ChildRelationship> C = R.getChildRelationships(); !
List<String> relations = new List<String>();!
! ! for (Schema.ChildRelationship cr: C) {//only some relationships!
! ! !if ( (cr.getRelationshipName().contains('Role’) ) !
relations.add(relName);!
! ! }!

16. Solution Elements : Dynamic Visualforce Controller
public Component.Apex.OutputPanel getOpportunityRelatedLists() {!
!Component.Apex.OutputPanel dynOutPanel= new
!Component.Apex.OutputPanel();!
for(String rel: relations) {!
Component.Apex.RelatedList dynRelList = new
! ! ! !Component.Apex.RelatedList();!
dynRelList.list = rel;!
dynOutPanel.childComponents.add(dynRelList);!
}!
return dynOutPanel; !
!}!

17. Solution Element: Dynamic Visualforce Page
§ Visualforce Markup generated dynamically in the Controller
§ Dynamic generation of custom related lists based on the relationship
<apex:dynamicComponent componentValue="{!
OpportunityRelatedLists}"/>!
!
!

18. Ritesh Aswaney
Technical Solution Architect,
@techtrekker