Siebel Object Interfaces Reference > Programming > Siebel Object Interface Events and Siebel Extension Events >

Siebel Business Component Events

Events can be invoked from data operations on business components. These are defined on a per-business component basis. Events can be invoked before or after the specified standard behavior.

The only means of trapping modifications to a multivalue field is through the underlying MVG business component. If the multivalue field is modified without popping up the MVG applet, then the PreSetFieldValue and SetFieldValue events for those fields are not triggered. The only way in which the PreSetFieldValue and SetFieldValue events are fired for a multivalue field is if the field is updated within the MVG applet. If the user makes a change to the multivalue field through the MVG applet, then only the events on the MVG business component are called. No events on the parent business component are called.

Table 17 and Table 18 list BusComp events.

Table 17.  Server Side BusComp Events
Method
BusComp_Associate
BusComp_ChangeRecord
BusComp_PreCopyRecord
BusComp_CopyRecord
BusComp_InvokeMethod
BusComp_NewRecord
BusComp_PreAssociate
BusComp_PreDeleteRecord
BusComp_PreGetFieldValue
BusComp_PreInvokeMethod
BusComp_PreNewRecord
BusComp_PreQuery
BusComp_PreSetFieldValue
BusComp_PreWriteRecord
BusComp_Query
BusComp_SetFieldValue
BusComp_WriteRecord

Table 18.  Browser Side BusComp Events
Method
BusComp_PreSetFieldValue


 Siebel Object Interfaces Reference 
 Published: 18 June 2003