Example of Capturing User Drilldown Behavior
In this example, the Com Invoice Profile comes predefined with Siebel CRM starting with Siebel CRM release 8.1.1.10. It tracks the parent Account Id when the user navigates away from the Account Summary View. This view displays the following information:
Account details in a form applet that references the CMU Com Invoice Profile business component
Invoice profiles in a list applet that references the Com Invoice Profile business component
These business components reference the same database table, but no link exists that Siebel CRM can use that allows the CMU Com Invoice Profile business component to access the Account business component. Assume your implementation must get billing details from an external system when the user drills down on a billing profile. To support this requirement, Siebel CRM must send an integration object message that includes the following data:
Data from the CMU Com Invoice Profile business component, including values for the Invoice Profile Name field and the Account Id field that Siebel CRM uses as key fields to get billing information for the SOAP and HTTP Web service call. This billing information includes invoices, payment adjustments, balance, and so on.
The Account Id of the account that Siebel CRM displays in the Account Summary View when the user drills down on the Profile Name field of the business component record that Siebel CRM displays in the Com Invoice Profile list applet.
Siebel CRM includes the following predefined objects to capture this Account Id:
Adds the Profile Name drilldown object to the CMU Com Invoice Profile List Applet. The View property of this drilldown object references the CMU Billing Invoice View. The business component property of this applet references the Com Invoice Profile business component.
Adds the following user properties to the Com Invoice Profile business component.
Name Value DrilldownObject0
Profile Name
Profile Name:ProfileAttributeName1
Service Account Id
Profile Name:ProfileAttributeName2
Service Account
Profile Name:ProfileAttributeValue1
Account Id
Profile Name:ProfileAttributeValue2
Account Name
ProfileAttributeValue1 and ProfileAttributeValue2 each provide the name of a business component field. In this example, ProfileAttributeValue must contain the name of a business component field that currently exists. ProfileAttributeName can contain a text string.
Adds the following fields to the CMU Com Invoice Profile business component:
Name Calculated Value Service Account
GetProfileAttr("Service Account")
Siebel CRM uses the value of the ProfileAttributeName2 profile defined in step 2 to calculate the Service Account.
Service Account Id
GetProfileAttr("Service Account Id")
Siebel CRM uses the value of the ProfileAttributeName1 profile defined in step 2 to calculate the Service Account Id.