X

Achieving Digital Transformation with Oracle's Siebel CRM

Try Oracle Cloud Platform For Free

Working with Browser Scripts in Siebel CRM 17

John Bedford
Director, Product Strategy

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:

  • Create a folder under <Drive:>\<build>\ses with name public
  • Open legacy Siebel Tools and create a workspace. Write the required browser script and checkpoint the workspace from Siebel Tools
  • Login to the application (the desired application for example Callcenter, Fins on which user wants the browser scripts to be active) and navigate to the WSUI dashboard to deliver the workspace
  • Once the workspace is delivered successfully, browser scripts get generated in the above <Drive:>\<build>\ses\public folder typically with the naming convention as srf………
  • Navigate to <Drive:>\<build>\swsm\applicationcontainer\webapps location and copy the browser script folder created above into the siebel.war file. (User needs to extract the archive and manually paste the browser script file into the siebel.war archive contents)
  • The deployment of the srf….. browser script folder will happen into the extracted siebel directory as well in parallel
  • Launch the desired siebel application and check for the presence of the browser scripts

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 :

  • <Drive:>\<build>\swsm\applicationcontainer\webapps\siebel\scripts
  • <Drive:>\<build>\swsm\applicationcontainer\webapps\siebel\scripts\siebel
  • <Drive:>\<build>\swsm\applicationcontainer\webapps\siebel\scripts\siebel\samples
  • <Drive:>\<build>\swsm\applicationcontainer\webapps\siebel\scripts\siebel\custom

.css :

  • <Drive:>\<build>\swsm\applicationcontainer\webapps\siebel\files
  • <Drive:>\<build>\swsm\applicationcontainer\webapps\siebel\scripts\3rdParty

Image files :

  • <Drive:>\<build>\swsm\applicationcontainer\webapps\siebel\images
  • <Drive:>\<build>\swsm\applicationcontainer\webapps\siebel\<language>\images

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.

Recent Content