Table 1. What's New in Siebel Object Interfaces Reference, Version 8.0, Rev. B
|
|
Siebel Web Client Automation Server |
The EnableWebClientAutomation parameter is set for the Application Object Manager in version 8.0, not in the application configuration file. |
Accessing the Siebel Web Client Automation Server |
You cannot invoke the Siebel Web Client Automation Server directly from the active Siebel instance. |
Instantiating the Java Data Bean |
Updated the connect string to include explicitly the port for the SCBroker component. |
Java Data Bean and the siebel.properties File |
The maximum possible value for both siebel.conmgr.txtimeout and siebel.conmgr.sesstimeout in the siebel.properties file is the largest positive integer, 2,147,483,647. |
Inter-Application Variable Methods |
Removed the topic. These methods are described elsewhere in the documentation. |
Connect String |
Removed the http transport protocol, which is not valid for connect strings. |
Using Load Balancing with the Connect String |
When the COM Data Control operates in server mode in an environment that implements load balancing, the VirtualServer parameter in the connect string must match the VirtualServer parameter in the session manager rules in the lbconfig.txt file. |
Name Method |
Changed the function name in the Browser Script example to Applet_Load. |
Applet_ChangeRecord Event |
Added a note describing the difference between the BusComp.GetFieldValue() method and the control.GetValue() method when used in this event. |
GetSharedGlobal Method |
This method and the SetSharedGlobal method are not used with the Java Data Bean. Use GetProfileAttr and SetProfileAttr instead. |
GetDataSource Method |
Returns the data source defined in the DataSource server parameter, not in the application configuration file. |
LoadObjects Method |
The LoadObjects method does not return an Application object. It either returns nothing or throws an error. |
LoadUserAttributes Method |
If the row ID argument is the row ID of the current user, the user profile will be loaded into the "Me" profile. |
SetProfileAttr Method |
Added a note that system fields cannot be used with this method. |
Application_Start Event |
Added a caution not to use the RaiseErrorText() method in the Application_Start event. That method does not work in this event, and can cause the Application Object Manager to abort. |
ActivateField Method |
If the Show In List property of a list column is TRUE, the field will be active even if it is not shown on the applet. |
ExecuteQuery Method |
Added a note that you must activate fields by using the ActivateField method before executing a query for a business component. |
FirstRecord Method |
Added a note that this method can cause extra SQL code to be generated. |
InvokeMethod Methods for the Business Component Object |
Added the ClearLOVCache method. Added examples for the CreateFile, GetFile, and PutFile methods. |
BusComp_DeleteRecord Event and BusComp_PreDeleteRecord Event |
The BusComp_PreDeleteRecord and BusComp_DeleteRecord events do not execute for child records that are deleted due to the Cascade Delete property on a link. |
Service_PreInvokeMethod Event |
Added a note that Browser Script does not support output property sets with this event. Added explanations of the intended uses of the Browser Script and Server Script versions of the Service_PreInvokeMethod event. Described the differences in the handling of standard and custom business service methods. |
SetLabelProperty Method and SetProperty Method |
Color formats for the BgColor and FontColor properties start with a hash mark (#). |
Property Set Methods |
Removed the ToString method, which does not return a useful result. |
Business Component Methods for COM Data Control |
Added the SetUserProperty method. |
Application Methods for COM Data Server |
Removed the GetLastErrCode method, which is not used with the COM Data Server. |
Application Methods for Browser Script |
Added the ShowModalDialog method. |
Invoking Custom Methods with MiniButton Controls |
The declarative method of adding a button is strongly recommended over the server script method for performance reasons. |