Home » Archive

Articles in the Scripting Category

Configuration, Scripting, Tips & Tricks »

[4 Aug 2010 | Comments Off | ]

Power of Siebel eScripting or also called as ECMA Scripting

1. We some time faces issues to remove special characters in a Workflow Step, and look for a vanilla Workflow function to use, but cannot find the one.
2. We try for a custom business service to find and replace the special character. But some time that custom business service restrict you to only few character, but later you want to filter out some more chars, the you need to modify it. Also, you may have to do a while loop or for …

Configuration, Debugging Techniques, Tips & Tricks »

[23 Jun 2009 | 3 Comments | ]

When you goto Tools->Screen object, you cannot see ‘Bitmap Category’ field because it is HIDDEN in tools for a normal view. You need to enable it from Tools CFG.
Here are steps -
1. Open your Tools.cfg.
2. Search for “ClientConfigurationMode”, it might be there with value like
ClientConfigurationMode = Web
3. If you find it or did’t find it, just add/replace below value to the [Siebel] section of CFG. This is the first section of CFG.
ClientConfigurationMode = All
4. Relaunch your Tools. This will show certain hidden fields and Objects of Tools.
5. …

Configuration, Scripting »

[6 May 2009 | 3 Comments | ]

Suppose your data having special characters is stored in string variable sLoginName.
Then below is code that will do your job.
while(Clib.strchr(sLoginName, ‘ ‘) || Clib.strchr(sLoginName, ‘\n’) || Clib.strchr(sLoginName, ‘\r\n’)))
sLoginName = sLoginName.replace(“\r\n”,””);
sLoginName = sLoginName.replace(“\n”,””);
sLoginName = sLoginName.replace(” “,””);
Post your replies below and any question to Interview Forum.

Configuration, Scripting »

[6 May 2009 | 2 Comments | ]

When you select any record in a MVG applet, and then close the applet with that record selected, that record is shown on the MVF of parent. Now our requirement is that we want to show only the Primary Record of the MVG to show up in Parent MVF, how to achieve it –
Write the below code in the MVG Applet’s Server Script – WebApplet_PreInvokeMethod
function WebApplet_PreInvokeMethod (MethodName)
if (MethodName == “CloseApplet”)
this.BusComp().SetSearchSpec(“SSA …

Debugging Techniques, Featured, Scripting, Tips & Tricks »

[6 May 2009 | 2 Comments | ]

1. Create a simple batch file “SiebelKill.bat”
2. Right Click Edit the file with Notepad
3. Put the below text
TASKKILL /F /IM siebel.exe
TASKKILL /F /IM iexplore.exe /FI “WINDOWTITLE eq Siebel Call Center – Microsoft Internet Explorer*”
4. Save the file
5. Double click the file whenever you want your dedicated Siebel application and its task – Siebel.exe to get killed from Task Manager automatically.
And its done…

Debugging Techniques, Scripting »

[27 Apr 2009 | Comments Off | ]

Right Click on My Computer
Goto Properties -> Advanced -> Environment Variables
Goto System Variables. Click New. Add below values
Variable Value: can be (1,2,3,4,ALL). Highest value is “ALL”

Goto System Variables again. Click New. Add below values
Variable Name : SIEBEL_LOG_DIR
Variable Value: Directory where you wants logs like (c:LocalLogdir)

Debugging Techniques, Scripting »

[24 Apr 2009 | 7 Comments | ]

How to do Browser Script Tracing in Siebel
For tracing the browser script, you can follow the below procedure –
1. In Application Browser script, create new script with MethodName “trace_log”.
function trace_log(as_text)
var MyWindow = window.open(”,’DEBUG’,’toolbar=no,location=no,’ + ‘directories=no,status=no,menubar=no,’ + ‘scrollbars=yes,resizable=yes,’ + ‘width=400,height=300,left=20,top=20′);
MyWindow.document.write(as_text + “<BR><BR>”);
alert(“an error occurred in log ” + e.message + “n” + e.toString());}//catch
MyWindow = null; }//finally
2. Application Browser Script declarations write –
top.log = trace_log.
3. Now you can call top.log(“text”) function from any Browser Script(Application, Applet, BusComp, Business Service) , it will write logs to a pop-up …

Debugging Techniques, Scripting »

[24 Apr 2009 | 5 Comments | ]

During the development or testing phase of Siebel Application we may encounter errors in Siebel Dedicated or Tools. So how do we find out the source of error or where to raise log levels to get detailed log file.
Siebel provides some debugging techniques , just follow the below links for details
• Enable Client Side Tracing Scripts
• Siebel Environment Variables
• Spooling
• Siebel Debugger – Break Points