|Bookshelf Home | Contents | Index | PDF|
The PreSetFieldValue event is called after a value is changed in the user interface (when the user attempts to leave the field) or through a call to SetFieldValue, but before any field-level validation is performed. This event is intended to allow the developer to introduce complex validation before any repository validation is applied.
When using a picklist to populate multiple fields, PreSetFieldValue is fired for each field that is populated. For example, you have an applet that you use to populate Last Name, First Name, and Contact ID. Therefore, PreSetFieldValue fires three times, once for each field.
CancelOperation stops the execution of the underlying Siebel code associated with the event. However, if there is code in the same script following CancelOperation, that code runs regardless of the CancelOperation. In the preceding example, if your script returns CancelOperation for a field, that field is not populated. However, PreSetFieldValue still fires for the other two fields populated by the picklist.
NOTE: To prevent infinite recursions, if the PreSetFieldValue event is running it does not run again for the same business component instance, even if used on a different field in the business component.
This Siebel VB example uses the PreSetFieldValue event to check if a quote discount is greater than 20 percent, and to take appropriate action if it is. For other examples of BusComp_PreSetFieldValue, read LoginId Method, and ExecuteQuery Method.
Function BusComp_PreSetFieldValue (FieldName As String,
function BusComp_PreSetFieldValue (FieldName, FieldValue)
|Siebel Object Interfaces Reference||Copyright © 2008, Oracle. All rights reserved.|