Extra ChangeRecord is fired on source Business Component, when user performs Drilldown
(Doc ID 2064711.1)
Last updated on MARCH 15, 2019
Applies to:Siebel CRM - Version 8.1.1  and later
Information in this document applies to any platform.
It was noted, that the "ChangeRecord" event handler ("BusComp_ChangeRecord") is invoked to executed server-side script (Siebel eScript or Siebel VB)
for source Business Component, every time as user clicks on the Business Component (BC) field shown in the list applet to execute the Drilldown to some destination BC (View and Applet).
However the "ChangeRecord" for source BC when the Drilldown was made on the 1st (top) record of the list.
Execution of following event chain was observed, when drilldown was made on the first record of the list applet.
1. Current applet PreInvoke
2. Destination Applet Load
3. Destination BC changeRecord
However different sequence was seen, when drill down was made on the second (third etc) record of the list applet:
1. Current Applet PreInvoke
2. Current BC Change Record
3. Destination Applet Load
4. Destination BC ChangeRecord
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!