Configuring Siebel eBusiness Applications > Overview of Configuring Siebel Applications > About the Siebel Operating Architecture >

About Standard and High Interactivity


Siebel applications are deployed in either standard interactivity or high interactivity mode.

Standard interactivity mode resembles most traditional Web applications. It supports many different types of browsers. Page refreshes occur often, such as when users create new records, submit forms, and browse through lists of records. Customer applications are deployed in standard interactivity mode.

High interactivity mode is designed to resemble a Windows client. It supports fewer browsers than standard interactivity mode, but it includes a set of features that make data entry easier for users. For example, page refreshes do not occur as often as they do in standard interactivity mode. Users can create new records in a list, save the data, and continue browsing without a page refresh having to occur. Siebel employee applications are typically deployed in high interactivity mode.

Other features supported by high interactivity mode are:

  • Browser scripting. In high interactivity, you have access to Siebel objects using browser script. This allows you to build data validation logic on the client side to reduce the number of page refreshes needed.
  • Implicit commit. Allows the application to automatically save a record when the user steps off the record.
  • User interface features. Features include drag-and-drop column reordering, drag-and-drop file attachments, keyboard shortcuts, pop-up controls for calendar, calculator and currency functions, and applet scroll bars.
  • Extensible toolbars. In high interactivity you can extend JavaScript toolbars and create new ones. JavaScript toolbar objects reside in the JSSApplication hidden frame, which usually does not reload during the application life cycle. Therefore, they are not redrawn when there is a page refresh. The UI part of the JavaScript toolbar resides in a visible HTML frame (recommended to be a persistent frame that reloads infrequently) and redraws when the HTML frame reloads.

NOTE:  Partner applications can be deployed in either standard interactivity or high interactivity mode.

One way to differentiate between standard and high interactivity modes is by the underlying technologies used by each mode (see Table 7).

Table 7.  Technology Differences Between Standard and High Interactivity
Technologies
Standard Interactivity
High Interactivity

Uses Java technology

 

X

Uses JavaScript technology

X

X

Uses Active X technology

 

X

Uses Document Object Model

 

X

Configuring Siebel eBusiness Applications