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 for High Interactivity Mode

Table 112 lists the Document Object Model events you can use in high interactivity mode. 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 112. Document Object Model Events You Can Use in High Interactivity
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 in high interactivity mode only, use the Applet_PreInvokeMethod event that is associated with the applet. For more information, see Using a MiniButton Control to Call a Custom Method.

Document Object Model Events for Standard Interactivity Mode

Table 113 lists the Document Object Model events and template modes you can use in standard interactivity mode. The Type property for each control uses a type that is native to the browser.

Table 113. Document Object Model Events You Can Use in Standard Interactivity
Control
Event
Description

Button

You can use the following events:

  • OnBlur (Base/Edit)
  • OnFocus (Base/Edit)
  • OnMouseOut (Base/Edit)
  • OnMouseOver (Base/Edit)

Not applicable

CheckBox

You can use the following events:

  • OnBlur (Base/Edit)
  • OnChange (Edit)
  • OnFocus (Edit)
  • OnMouseOut (Edit)
  • OnMouseOver(Edit)

Siebel CRM renders a CheckBox control in the following ways:

  • In Base mode, as a Y or N text value
  • In Edit mode, as Input Type is CHECKBOX

Link

You can use the following events:

  • OnBlur (Base/Edit)
  • OnClick (Base/Edit)
  • OnFocus (Base/Edit)
  • OnMouseOut (Base/Edit)
  • OnMouseOver (Base/Edit)

Siebel CRM renders a Link control in the following ways:

  • In Base mode, through paired anchor tags
  • In Edit mode, as INPUT TYPE is TEXT

Mailto

You can use the following events:

  • OnBlur (Base/Edit)
  • OnChange (Edit)
  • OnFocus (Base/Edit)
  • OnMouseOut (Base/Edit)
  • OnMouseOver (Base/Edit)

Siebel CRM renders a Mailto control in the following ways:

  • In Base mode, as anchor tags with HREF is mailto
  • In Edit mode, as INPUT TYPE is TEXT

MiniButton

You can use the following events:

  • OnBlur (Base/Edit)
  • OnClick (Base/Edit)
  • OnFocus (Base/Edit)
  • OnMouseOut (Base/Edit)
  • OnMouseOver (Base/Edit)

Not applicable

Password

You can use the following events:

  • OnBlur (Edit)
  • OnChange (Edit)
  • OnFocus (Edit)
  • OnMouseOut (Edit)
  • OnMouseOver (Edit)

Siebel CRM renders a Password control in Edit mode as Input type is password.

Text

You can use the following events:

  • OnBlur (Edit)
  • OnChange (Edit)
  • OnFocus (Edit)
  • OnMouseOut (Edit)
  • OnMouseOver (Edit)

Siebel CRM renders a Text control in the following ways:

  • In base mode, as plain text, unless a pop-up window is associated with the control.
  • In Edit mode, as INPUT TYPE is TEXT, unless the control is attached to a picklist. If the control is attached to a picklist, then Siebel CRM renders it as INPUT TYPE is SELECT.

TextArea

You can use the following events:

  • OnBlur (Edit)
  • OnChange (Edit)
  • OnFocus (Edit)
  • OnMouseOut (Base/Edit)
  • OnMouseOver (Edit)

Siebel CRM renders a TEXTAREA control in the following ways:

  • In base mode, as plain text, unless a pop-up window is associated with the control
  • In Edit mode, as INPUT TYPE is TEXTAREA

URL

You can use the following events:

  • OnBlur (Base/Edit)
  • OnChange (Edit)
  • OnFocus (Base/Edit)
  • OnMouseOut (Base/Edit)
  • OnMouseOver (Base/Edit)

Siebel CRM renders a TEXTAREA control in the following ways:

  • In Base mode, through paired anchor tags with an HREF that is the underlying field value
  • In Edit mode, as INPUT TYPE is TEXT

Tree

Scriptable events are not available.

Not applicable

List Column

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