Check Domain & Buy at Low Cost

Tuesday, March 18, 2008

High Interactivity Framework Problem.

We faced this problem quite often in Siebel 7.7. I am yet to face this error in Siebel 7.8 but I think there are lot of people that are still using Siebel 7.7 or even Siebel 7.5 so they might be facing this kind of problem.


When clicking on Pick Applet in Siebel 7.7 application the application IE instance used to crash and we had to reopen the application. It happened only in case we were working with Pick Applet.


This error was due to High Interactivity Framework files getting corrupt. For those who feel this is new term I will just give a background.

Siebel can operate with two types of framework

  • Standard Interactivity
  • High Interactivity.

The difference between both the frameworks is how Siebel Client communicates with Server. In case of standard interactivity the changes you make to record are not committed automatically to the database and use has to explicitly save the record and in High interactivity even if you step of the record or screen the changes are committed automatically.


Solution of this problem is to go and remove the High Interactivity framework files and open the application again. When you open your application Siebel downloads fresh interactivity file from server.

These are steps you can follow to remove and reinstall the interactivity files

Goto Internet Explorer –> Tools Menu –> Internet Options

Click on Settings Button

Siebel setting for Internet Explorer

Click on View Objects Button

Siebel setting for High Interactivity Framework

Locate High Interactivity Files

Siebel High Interactivity Files

Right Click and choose remove

*You will need to have Administrator Rights in order to remove these files.
PS: You can define at application level in Siebel Tools the mode of interactivity that you want to use.

Monday, March 17, 2008

Siebel How To - enable or disable a button conditionally?

I was working on my desk one day and newbie to siebel approached me to ask a question(also a avid reader on asked me the same question on mail). He asked me about a simple requirement or rather I should say the requirement that appeared simple to me.

The requirement was :

A button on an Applet should be enabled if a particular user logs into the application otherwise it should remain disabled.

The Solution is a simple script that we can write on Applet_PreCanInvoke event to enable or disable a button conditionally.I am providing the pseudo code for that script below

function WebApplet_PreCanInvokeMethod (MethodName, &CanInvoke)
if (MethodName == “UrButtonMethod”)
if(UserLogin == “AuthorisedUser”)
return (CancelOperation);
return (CancelOperation);