Siebel Application is a like a stitched cloth and sometimes, you want to do some enhancements so as to look and suit better

for the given requirement. Generally, scripting is used to complement existing configurable capabilities by allowing developers to fill in functionality gaps with concise, simple scripts and fine tune the application to meet the requirement. There are two kinds of scripting: 1. Server Scripting 2. Browser Scripting I think its not necessary to mention again that Keep your scripting as low as possible in your Siebel application and do not use it unless you dont find a smarter way to achieve the task. Browser Scripting is used for 2 main purposes: 1. UI Trigger Based actions 2. Simple Validations Browser Script works only with applications that run in High interactivity mode. Browser Script executes in and is interpreted by the browser. Browser Scripts interacts with the Document Object Model (DOM) as well as with the Siebel Object Model available in the browser through the Browser Interaction Manager. A developer can script the behavior of Siebel events as well as the browser events that are exposed through the DOM. When you write browser script on an object and compile it, a .js file is automatically generated and created in the browser script folder for that object in the location C:\Siebel\8.1\Client_1\PUBLIC\ENU. But sometimes, there is a need to generate .js files corresponding to the browser script manually and in my experience, most of the times, .js files wont be generated. These errors can be because of patch issues or other browser issues. Siebel has provided us with a utility called genbscript which allows to manual generation of .js files for the browser scripts written.

Genbscript This utility is located at C:\Siebel\8.1\Client_1\BIN\genbscript.exe You have to run this utility from command prompt. Follow the steps given: 1. Open Command Prompt 2. cd C:\Siebel\8.1\Client_1\BIN 3. genbscript C:\Siebel\8.1\Client_1\BIN\ENU\publicsector.cfg C:\Siebel\8.1\Client_1\PUBLIC\ENU { genbscript path to .cfg file path where browser script to be generated You can automate this process using a Batch file also. Follow the steps given:

1. Open Notepad 2. Paste the code: cd C:\Siebel\8.1\Client_1\BIN genbscript C:\Siebel\8.1\Client_1\BIN\ENU\publicsector.cfg C:\Siebel\8.1\Client_1\PUBLIC\ENU 3. Save the file as .bat file After you are done, just double click it and the task would be done.

Difference between Siebel Browser Script and Server Script Execution Context: Siebel Server Scripts are executed in Siebel Application Servers by Application Object Manager (AOM). {AOMs are hosted as components in the Siebel Server and run on the application server (the machine that hosts the Siebel Server). The Siebel Server provides the infrastructure for an AOM to serve multiple Siebel Web client users. Multiple AOM components can run on a single Siebel Server installation} Siebel Browser Scripts are executed at Client Side by Client Browser (Internet Explorer etc). Browser script executes in the client browser Javascript interpreter. Files: Siebel Browser Scripts are converted in JS (Java Script) files and stored in PUBLIC\ENU directory. No JS files are created for Server Scripts and they are executing using Siebel Scripting Engine either T engine for versions 7.7, 7.8 and 8.0 or ST engine for 8.0 and above versions. Scripting Language: Only eScript can be used in Browser Script whereas in Server Script, both VB / eScript can be used.