Bookshelf Home | Contents | Index | PDF     

Siebel Object Interfaces Reference > Browser Script Quick Reference > Object Interfaces Reference >

Document Object Model Events You Can Use

This topic describes Document Object Model events you can use.

Document Object Model Events

Table 109 lists the Document Object Model events. For each control, you can use the following events:

  • OnFocus
  • OnBlur

Note that scriptable events are not available for List Column and Tree controls.

Table 109. Document Object Model Events
Control
Siebel Control Type
Description

Button

Native

None

CheckBox

Native

Rendered as Input Type is CHECKBOX.

Link

Native

Rendered through paired anchor tags or as INPUT TYPE is TEXT in edit mode.

List Column

Native

None

Mailto

Native

Rendered as anchor tags with HREF is mailto or as INPUT TYPE is TEXT in Edit mode.

MiniButton

Native

None

Password

Native

Rendered as Input Type is password.

Text

Native

Rendered as INPUT TYPE is TEXT or as SELECT if attached to a picklist. If there is a pop-up window, then Siebel CRM renders it as an edit box plus a button.

TextArea

Native

Rendered as TEXTAREA.

Tree

Native

None

URL

Native

Rendered through paired anchor tags with an HREF equal to the underlying field value or as INPUT TYPE is TEXT in edit mode.

You cannot access a Siebel object from a Document Object Model event. Business components and applets are examples of Siebel objects.

You can typically call code in the General section from anywhere in an object. However, you cannot call code written in the General section from a Document Object Model event.

To associate a script with the control_OnClick event, use the Applet_PreInvokeMethod event that is associated with the applet. For more information, see Using a MiniButton Control to Call a Custom Method.

      
Siebel Object Interfaces Reference Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices.