Using Siebel Tools > Siebel Script Editors >

About the Siebel Script Editors

The Siebel Script Editor is a window-based editor designed to create and maintain Siebel VB, Siebel eScript, and Browser Script programs. Scripting is used to implement functionality that cannot be achieved declaratively (that is, by changing object properties in the Siebel repository). The Server Script Editor and the Browser Script Editor are used to add scripts to Siebel objects. The Server Script Editor allows you to create and modify Siebel eScripts and Siebel VB. The Browser Script Editor allows you to write and edit Browser Scripts that run within the client. For more detailed information, including a list of scriptable events and callable methods on browser objects, see Siebel Object Interfaces Reference.

NOTE:  There are two versions of the eScript scripting engine available. The ST eScript engine—available with Oracle's Siebel Business Applications, version 7.8 and higher—is the default eScript scripting engine in version 8.0. It provides enhancements including strong typing of variables and the Script Assist utility. The T eScript engine is the traditional, previously available engine.

Except for a few key differences, the ST eScript engine is backward-compatible with eScript created with the T eScript engine. In this document, the engines are referred to by name only in contexts requiring differentiation.

For a list of enhancements contained in the ST eScript engine, and well as instructions on how to enable the ST eScript engine, see About the ST eScript Engine. For information on syntax differences between the two engines, see Siebel eScript Language Reference.

When creating Siebel custom programs, note the following:

• Check out or lock the project containing the object definitions being modified. If the project is not locked, you will not be able to add any text in the Editor window.
• Choose Debug > Check Syntax to verify the syntax of your VB or eScript program. The Siebel Compiler reports any syntax errors and indicates the lines where they occur.
• Choose File > Save when you have finished entering and editing the custom statements to save your work. Closing the Siebel Script Editor without saving your work discards the changes.
• Before you run the application, you must compile the projects that you have modified and generate a new SRF file. For more information, see Compiling and Testing.
• Run the application with the new application extensions by choosing Debug > Start or clicking the Start button in the Debug toolbar. The Siebel application executes with the new modifications incorporated.
• You may inadvertently create programming errors that, when encountered, halt the execution of the extension routine. If you started Siebel applications in debug mode (/H option on the command start-up line), a message box opens indicating the nature of the error. You can then return to the Script Editor and choose Debug > Check Syntax. For further details, see Checking Syntax.
• When a script error is encountered by an end user, or when the Siebel application is not running in Debug mode, the application displays an appropriate error message with an error code and returns control back to the point in the standard Siebel code just before the error.

  NOTE:  You can suppress the display of the scripting error message code SBL-EXL-00151 in
  pop-up error messages raised by the RaiseErrorText application method. Navigate to Screens > System Administration > System Preferences, and then set the value of the Suppress Scripting Error Code preference to TRUE. The default value is FALSE.