Standard Interactivity in Open UI

Are you upset about an SI Siebel View embedded in a High Interactivity application doing a complete view refresh every time you operate on it? Or are you wondering why Open UI refuses to display certain pre-existing applets? Or why Applications which were completely Standard Interactivity based, do not work properly in Open UI? This post is for you...

Let me explain what we mean by Standard and High Interactivity modes.

Standard interactivity (SI) means that the server sends completely data bound HTML content to the client browser. This is just like a normal website which does page navigations and redraws your complete Siebel view area.

The flicker noticed is a blessing:-) 

High Interactivity (HI) means that the server sends data and UI (HTML with active objects in legacy HI or JavaScript controls in Open UI) as different responses and the client binds the data onto the HTML and renders the same. The next time a data refresh is needed, the client gets only that much from the server and no layout comes in. And data rebinds to the already available UI. This offers least flickers to the UX.

As all of you might have seen, a HI list applet will refresh just its records when you operate on it. It could also enable/disable UI controls with no repainting.

The general downsides of a Siebel SI applet/view are:

a) Complete View refresh on any operation on Applets

b) No standard focus handling among the controls of the Applets and between the View and rest of UI

c) Limited control over the data shown in the client, since it is in a data bound page served up in one shot from the Siebel server. You can tie browser scripts to specific HTML events emitted from the page and react to it. You will not be able to participate to a complete extent in the various phases of data preparation and post back to server

d) Even a single applet being SI makes the complete view SI, in a sense demoting all of those otherwise HI applets to SI

e) Limited support in terms of dynamic UI, since any UI change will require a server roundtrip

Now that we know what these interactivity modes are and their pros and cons, let us see how a Siebel Server decides when a Siebel View is designated to operate in one of these modes.

A View becomes SI if any of the below criteria are met:

1. Contains one or more  Applets which are not bound to a Business Component

2. Contains one or more Applets whose “Class” properties points to a Class which derives from classes that implement the base functionality of Standard Interactivity

3. Contains one or more Applets whose associated Class have “High Interactivity” set to 1

4. Contains one or more Applets with User property: High Interactivity Enabled = N

5. Contains one or more Applets outside of a View i.e. not associated to a view web template other than standard popups (MVG/Pick/Assoc). eg., “About Record”

6. The server side Renderer  implements Standard Interactivity

7. Contains one or more Applets with a portlet in it

8. Product Catalog style layouts

In Open UI, we elevate all applets which do not belong to category 6 to High Interactivity, automatically. In other words, the “configuration” surrounding steps 1- 5 that you would have done to explicitly make an Applet/View SI, will not work in Open UI.

Now coming to what happens to applets which fall under category 6. These will presently be blocked in Open UI and remainder of the view will function as a complete HI view.

This is what you will see for those applets:

Views that expose portlets and catalogs will also function as HI with respect to the applets other than those.

Applets for which you see a message above, are being progressively migrated, so we will have to wait :-)

Lastly, as far as customizations done on a GA Siebel application are concerned, the claims above hold good. If you have some rendering customizations via browser/server scripts, done on applets falling under 6, these Applets will have to be migrated to the High Interactivity style rendering of Open UI first, after which the customization may work as is, but most probably will need to be re-looked at and rewritten using the new client stack.

Until next post, bye .

Vishal Thilak



What does this mean for a eSales application. Is there a change in configuration side to implement
Open UI for an eSales,as its a SI application. To be honest I am not able to figure out which category 1-5 or 6 or it falls to


Posted by guest on June 01, 2013 at 10:28 AM PDT #


"Now coming to what happens to applets which fall under category 6. These will presently be blocked in Open UI and remainder of the view will function as a complete HI view."
- When will the rendering of the applet be completed?

Posted by guest on July 25, 2013 at 12:51 AM PDT #

Just wanted to know when would the item line 6 be resolved. i saw some place where it says we would have to customize it and gave the Configure Open UI guide in Bookshelf. i searched and can't find anything.

Posted by Chigo on January 08, 2014 at 01:29 AM PST #

And How To Solve It????!!!!!!!!!!

Posted by guest on January 15, 2014 at 03:49 AM PST #

I am wondering if it is technically possible to rewrite Standard Interactivity eSales to High Interactivity. Also it would be important to keep the licensing rules the same if such conversion were possible. In other words do not re write using a clone of the Call Center object manager which would be subject to different licensing than eSales. And besides authentication of external users would be kind of a problem to figure out, if at all.

Can the eSales object manager support high interactivity?

I would think it best to wait for IP2016 to see what Oracle has to offer in this regard.



Posted by Dave Delaney on February 22, 2016 at 08:34 AM PST #

Post a Comment:
  • HTML Syntax: NOT allowed

Insights on Open UI Architecture, Best Practices for Open UI Development and Examples of Open UI Customization - Straight from the Open UI Development Team!


« July 2016