Author: Siddhi Aithal (Principal QA Engineer, Siebel CRM Development)
Working with Browser Scripts in Siebel CRM 17
Browser scripts are a crucial part of Siebel scripting. These are essentially java scripts that are executed on the client side. A .js file (which contains the code snippet) is created for every script generated on a Siebel object; in a browser script folder. Traditionally, browser script folders are located in the eappweb folder; which is fundamentally the web server location.
However, from release 17.x onwards, the traditional eappweb folder used to read and create .js files used for browser scripts is not present. Hence, user has to perform certain steps manually for siebel to read the js files from the webserver location that is the SWSM location.
The steps mentioned below are a technique to generate browser scripts and have the siebel client read them from the webserver location:
NOTE:
Please take a backup copy of the siebel.war file before updating and deploying the contents. Changes made to the siebel.war file are permanent and if user directly updates the existing siebel folder instead of the war file, the changes are retained only until the next deployment, which is not a recommended practice.
Like Browser Scripts, any changes done to the OOTB .js, .css, .gif file types, also have to undergo the same process to be effective into the application. It is also applicable if a user wants to deploy custom .js, .css or image files into Siebel applications. Essentially any customization has to go through the siebel.war file only, by placing the custom files into appropriate locations.
Frequently used locations for different file types are referenced below:
.js :
.css :
Image files :