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:
//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 = “email@example.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”;
//for web client use ‘Remote’ instead of ‘Local’
inputs = null;
outputs = null;
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.