This solution may lead to adverse effects on your Siebel application, particularly when used with single sign-on. Therefore, Siebel Systems does not recommend that you implement such a configuration.
Bug 12-D0996T - has been logged to address the siebel enhancement request that the object manager session should be released as soon as the browser window is closed.
Bug 10459718 - has been logged to address the Siebel enhancement request that unsaved record changes should be saved when the user closes the browser window.
This only applies if you have implemented customizations to the CCFrameBanner.swt file and browser scripting, to force the Siebel application to do a clean log-out if the user closes the browser window directly.
NOTE: Previously, FAQ 2083 was published on Siebel SupportWeb providing this solution, but this FAQ has been removed from SupportWeb, and the configuration it described, is no longer supported or recommended.
Users may experience a system hang when the browser window is closed.
If, on an existing browser session which is connected to a Siebel application, the user refreshes the browser view, or enters a new URL into the browser Address field, the browser window will close instead of refreshing or navigating to the new URL.
Single sign-on (SSO) may not function correctly. Normally, in a SSO-enabled environment, a warning pops up when a session times out. The user can normally click OK and be logged back into the application. With the browser script changes, this action will also trigger a log-out. This may create an infinite loop, leading to a possible crash on the database server or web server, or other inconsistency in the system or application.
If you have implemented this configuration, please remove it, and revert to the standard behavior when the browser window is closed without the user logging off. Educate your users to always use File > Log Out, before closing the Siebel Web Client browser window.