Siebel Database Upgrade Guide > Postmerge Development Tasks for Siebel 6.x Upgrades >

Migrating Siebel Business Component, Business Service, and Application Scripts

Upgrades from: Siebel 6.x.

Environments: Development environment only.

This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade.

The majority of application, business components, and business services scripts implemented in Siebel 6.x can remain unchanged and should not require any modification after the upgrade. If existing scripts refer to methods that became obsolete or contain references to the Siebel user interface, the scripts need to be edited.

The following application and business component methods became obsolete as of Siebel 7.x.

• Application.MsgBox
• Application.InputBox
• Application.ActiveBusComp
• Application.ActiveApplet
• Application.GotoApplet
• Application.ShowStatus
• Application.ActiveControl
• Application.FindApplet
• BusComp.AllowNotification
• BusComp.SuppressNotification

In many cases, Siebel 7.x implementation alternatives offer comparable functionality to the obsolete methods. For example, the ActiveBusComp method can typically be replaced with a combination of ActiveBusObject and GetBusComp. By using these two methods together in a script, you can get access to the active business component. Additionally, MsgBox and InputBox methods can typically be replaced with some core functions available in JavaScript (through browser script) and some methods introduced in Siebel 7.x.

For example, using browser script, you can use code JavaScript features to provide warnings, dialog boxes, or input boxes through the alert, confirm, and prompt functions. For more information about using JavaScript features available in browser script to replace MsgBox and InputBox, see FAQ 1562 on Oracle's Siebel SupportWeb.

The RaiseError and RaiseErrorText methods were introduced to provide an alert notification from server script. These methods allow an error message to be displayed as an alert in the Web Client. Lines of code that follow the RaiseError or RaiseErrorText methods are not executed.

For more information about using RaiseError and RaiseErrorText methods, as well as additional information about using browser script and server script in Siebel 7.x, see Siebel Object Interfaces Reference and Technical Note 386 on Oracle's Siebel SupportWeb.

Related Topics

About Migrating Siebel 6.x Scripts.

Migrating Siebel Scripts Attached to Controls

Migrating Siebel Scripts Attached to Applets