Data Controls Implementation Guide

Data Controls Implementation Guide

Loose Coupled Controls

The Hierarchy Manager and History IDC controls are loosely coupled with the third-party applications in which they are embedded. The URL that invokes the control is the only interface between the control and the third-party application. The control is unaware of the containing third-party application and does not communicate with it.
The details of embedding an IDC control in a third-party application depend on the particular application. As an example, here is a Salesforce.com VisualForce page for an Account that includes a Hierarchy Manager control.
<apex:page standardController="Account" showHeader="true" tabStyle="account" > <style> .activeTab {background-color: #236FBD; color:white; background-image:none} .inactiveTab { background-color: lightgrey; color:black; background-image:none} </style> <apex:tabPanel switchType="client" selectedTab="tabdetails" id="AccountTabPanel" tabClass="activeTab" inactiveTabClass="inactiveTab"> <apex:tab label="Details" name="AccDetails" id="tabdetails"> <apex:detail relatedList="false" title="true"/> <apex:iframe src="http://hostname:port/bdd/bdc/hmEn/sag:Party,systemName:SFA,sourceKey: {!$CurrentPage.parameters.id}/hm/component.jsf" height="500" scrolling="false" id="siperianHM1"/> <apex:relatedList subject="{!account}" list="contacts" /> <apex:relatedList subject="{!account}" list="opportunities" /> <apex:relatedList subject="{!account}" list="OpenActivities" /> </apex:tab> </apex:tabPanel> </apex:page>
In this example, the
http://hostname:port/bdd/bdc/hmEn/sag:Party,systemName:SFA,sourceKey: {!$CurrentPage.parameters.id}/hm/component.jsf
URL invokes the control. This URL uses the system name and source key to invoke the control. The system name is a constant –
SFA
. The source key is dynamic -
{!$CurrentPage.parameters.id}
. This is the VisualForce syntax used to substitute the ID for the current account.

0 COMMENTS

We’d like to hear from you!