You should regard coding as a last resort.
Siebel Tools provides many ways to configure your Siebel application without coding, and these methods should be exhausted before you attempt to write your own code, for three reasons:
- Using Siebel Tools is easier than writing code. More important, your code may not survive an upgrade.
- Customizations created directly in Siebel Tools are upgraded automatically when you upgrade your Siebel application, but code is not touched, and it may need to be reviewed following an upgrade.
- Finally, declarative configuration through Siebel Tools results in better performance than implementing the same functionality through code.
Siebel eScript Language
You can opt to use the updated functionality of this engine, including the Siebel ScriptAssist tool, or you can opt to leave this updated functionality inactive.
Components of the Siebel Programming Environment
- Server Script:
* Siebel VB language
A programming language that is syntactically and semantically compatible with Microsoft Visual Basic™. Because the language uses most of the same commands and standards as Microsoft Visual Basic, you can extend your Siebel application and reduce training costs.
* Siebel eScript language
- Browser Script
- Siebel Script Editor
An integrated editor used to create, view, edit, and save custom program routines. The script editor has a code editing feature called Script Assist (introduced in version 7.8). Script Assist provides auto-complete, auto-indentation, method listing, and method signature capabilities to help minimize errors as you develop script. For more information about the Siebel Script Editor, including how to enable Script Assist, see Using Siebel Tools.
- Siebel Debugger
This assists you in detecting errors contained within Siebel programming language routines. It does not assist in detecting errors outside of the context of custom program routines. The Siebel Debugger can be invoked automatically from Siebel applications when a runtime
error occurs if the Siebel application was invoked with the debug option, /H, on the command start-up line. The Debugger can also be invoked from the Debug toolbar and Debug menu. The Debugger is described in more detail in Using Siebel Tools.
A nonvisual component of the Siebel programming languages that compiles and executes Siebel custom program routines. It is similar to Microsoft’s Visual Basic Language Interpreter. Siebel language routines are compiled into p-code and stored with the other object definitions in the SRF file.
- Object Interfaces
A collection of selected objects that expose their data and functionality to custom routines. The interface provides access to Siebel business objects with defined methods, events, and associated data. The object interfaces are the subject of this book.