Bookshelf Home | Contents | Index | Search | PDF

Siebel Tools Reference > Siebel Architecture (Basic Concepts) > Operating Architecture Overview >

Enabling High Interactivity

---

If using high interactivity, the layout of a Siebel application view is loaded from the server the first time you navigate to it. The layout is subsequently loaded again (and the view frame containing the applet refreshes) only if some action requires that the applet should be displayed using a different template.

A page refresh is expected only when there is a layout change. If you see a page refresh and the page layout has not changed, then it needs to be researched further. There are some exceptions as noted below.

NOTE:  High interactivity is not supported in customer applications.

High interactivity is enabled through two methods:

Updating the application configuration (.cfg) file
Applet class definitions

A view is a high interactivity view when the underlying classes of all the applets in the view have the High Interactivity Enabled property set to 2, 3, 4, or 5. The possible values for the High Interactivity Enabled property are summarized in Table 4.

Table 4. High Interactivity Enabled Property Values

Value	Works with High Interactivity	Works with Standard Interactivity	Cachable
1	No	Yes	No
2	Yes	No	Yes
3	Yes	No	No
4	Yes	Yes	Yes
5	Yes	Yes	No

NOTE:  You cannot configure the High Interactivity Enabled property.

To enable high interactivity in the application configuration file

Verify that the application is an employee application.
Open the application configuration (.cfg) file.
In the SWE section in the .cfg file, add the parameter HighInteractivity with value = TRUE:

[SWE]

HighInteractivity=TRUE

Save and close the .cfg file.

NOTE:  When running an application with HighInteractivity=TRUE, the Web framework attempts to show views in high interactivity only if every applet contained in the view supports this. Otherwise, the view will be displayed in standard interactivity.

To test whether a view uses high interactivity

In the application, navigate through multiple records.
Note whether the page refreshes completely with each record, or whether the data simply changes through DOM-based update.
In Siebel Tools, check that the view and the applets it contains are correctly configured.

Views that have applets supporting high interactivity are shown in standard interactivity under certain conditions:

One of the applets is in the Query mode.

Because high interactivity implicitly supports query operations from the user interface, it does not support the explicit use of the Query mode.

One of the applets is in the New mode and uses a New template that is different from the Edit template used in its default mode.

This can be avoided by inactivating New templates associated with the applets used in high interactivity applications. The framework will then default to using the Edit template itself to create new records.

One of the list applets has multi-row edits or multi-row select enabled.
One of the list applets is a hierarchical list applet.
The view uses a template that shows applets in a catalog-style layout.

None of the employee applications should be using this layout.

A combo box picklist uses Long Lists or has an associated pick applet.

For example, if you perform an action from a high interactivity applet that causes a pick applet to be displayed, the pick applet will not be in high interactivity.

Bookshelf Home | Contents | Index | Search | PDF