Siebel Experts

Post by Rachna Agarwal

The new features added for siebel 8.O eScript

1. The ST eScript Engine is enabled by default in Siebel 8.0

2. The Fix and Go option makes script testing more efficient by allowing scripts to be edited and the debugging process to continue without having to recompile the program after each change. Click to read the rest of this article »

Post by Rachna Agarwal

Browser Script executes in and is interpreted by the browser. Browser Scripts are written in
JavaScript and interact 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. The DOM for Internet Explorer and Netscape Navigator are different. Using Siebel Tools you can write scripts for the appropriate browser type by selecting the appropriate User Agent.

Browser Script may only be used with applications which run in high interactivity mode, except when scripting Control events supported by the Browser Document Object Model. Click to read the rest of this article »

The Siebel applications include two programming languages. Siebel VB is a Visual Basic-like programming environment that includes an editor, debugger, interpreter and compiler. Siebel VB runs on the Windows operating system only. Siebel eScript is, similarly, a JavaScript-like programming environment, which uses the same tools that Siebel VB uses. Siebel eScript runs on both Windows and UNIX operating systems. With these built-in languages, you can extend and configure your Siebel application beyond the capabilities provided by declarative object property definition. The languages are integrated with other Siebel tools, such as the Applet Designer, Siebel CTI, and Siebel SmartScript. Using this integration you can define object properties both with the designer and by attaching scripts. Click to read the rest of this article »

Purpose:Local Web Service is available in Siebel Enterprise Application version 7.5 and higher. Local Web Service provides customers with the ability to invoke inbound Web Service locally. When calling Local Web Service by the outbound Web Service, the request will not pass through the web server but directly call to the inbound Web Service. By using this characteristic you can use Local Web Service to test web service on a dedicated client.Follow given steps for setting up an Inbound Web Service as a Local Web Service

Click to read the rest of this article »

In general a developer or BA should avoid Siebel scripting where possible or to go for that  to a minimum . Attempt to meet business requirements by configuring in Siebel Tools where possible and generally implementing scripts for minor functionality where a given functionality cannot be met using declarative configuration.

Here are the list of Best practices for sibel scipting by siebel experts.

Click to read the rest of this article »

How Do You Send Email via Siebel Scripting or Object Interfaces Using Outbound Communication Manager                  

The Communications Outbound Manager processes outbound communications, for email, fax, wireless message, or page channels. It also supports outbound capabilities for Siebel Email Response and for the Send Email, Send Fax, and Send Wireless Message commands.

For further information, refer to Siebel Bookshelf version 7.5.x > Siebel Communications Server Administration Guide > Administering Siebel Communications Server > Administering Communications Outbound Manager.

Here is the eScript sample code:
//—-start

//instantiate the business service and the propertysets

var bs = TheApplication().GetService(”Outbound Communications Manager”);
var inputs = TheApplication().NewPropertySet();
var outputs = TheApplication().NewPropertySet();

//Communication profile to be used – must be must be a current profile defined in the application
var CommProfile = “MyProfile”;

var MsgToList = “s003@myexchangeserver.zeb.com”;
var MsgBody = “Hello testing hello! How are you today?”;
var MsgSubject = “Testing Message”;

//Where C:\ on the Siebel Server or the Siebel Client file system? Or where in a remote client?

var AttachFileList = “c:\\test.txt”;

inputs.SetProperty(”CommProfile”,CommProfile);

//for web client use ‘Remote’ instead of ‘Local’
inputs.SetProperty(”ProcessMode”,”Local”);

inputs.SetProperty(”MsgToList”,MsgToList);
inputs.SetProperty(”MsgBody”,MsgBody);
inputs.SetProperty(”MsgSubject”,MsgSubject);

inputs.SetProperty(”AttachFileList”,AttachFileList);

bs.InvokeMethod(”SendMessage”,inputs,outputs);

inputs = null;
outputs = null;
bs=null;

//—-end

NOTE: The sample code must be thoroughly tested before implementing in the production environment.The above code can be used via Siebel VB or Siebel Object Interfaces.

NOTE: The two arguments AttachFileList and AttachNameList are hiddenarguments belonging to the SendMessage method. Consequently it is possible to use these arguments, but they are technically not supported. As a result the sending of emails with attachments using the Outbound Communications Manager business service SendMessage method in scripting or workflow is not formally supported at present.

AttachNameList is a list of file names, each separated by “*” (asterisk). AttachFileList is a list of file paths, also each separated by asterisk. AttachNameList is optional. If omitted, the names in the file paths are used.

NOTE: The file paths must be accessible from the process that actually sends the email. That means the client process that calls SendMessage if the ProcessMode argument = Local, and the Communications Manager server component if the ProcessMode argument = Remote.