We all must have used Outbound Communications Manager business service for sending mails. There are various methods available to send mail and most commonly methods that are used to send mail are
- SendMessage
- SubmitRequest
The difference between both the methods is:
SubmitRequest is an Asynchronous way to send mail. When you use SubmitRequest method a job is created on Siebel Server to send mail and a record is created in S_SRM_REQUEST table. Siebel Server picks up record from there and processes it.
SendMessage you have the choice to control the way it is executed. If you pass the value of Argument ‘Process Mode’ with value as ‘Remote’ then it works similar to SubmitRequest method and if you specify “Process Mode” as ‘Local’ then execution of job happens in synchronous way and no record is created in S_SRM_REQUEST table.
Important thing to note:
According to the bookshelf documentation the default value for the “Process Mode” if it is not given by user is ‘Local’ which means that it should execute in Synchronous way and no record should be created in S_SRM_REQ
A Documentation Defect:
But after testing this in Siebel 7.8.2.6 Call Center module I found out that if “Process Mode” argument is not supplied then default process mode for SendMessage method is ‘Remote’ and not ‘local’ as mentioned in bookshelf.
So, If you want to SendMessage not to create record in S_SRM_REQUEST and be executed in Synchronous way then always provide Input argument ‘Process Mode’ with value as ‘Local’.
In the next post I will discuss the reason why you should always supply the value of ‘Process Mode’


(3 votes, average: 3.67 out of 5)
4 Comments at "Outbound Communications Manager and SendMessage"
Really good information
Neel,
I haven’t found any table with name S_SRM_REQ in version 7.8.3.7 but found a table S_SRM_REQUEST.
“In the next post I will discuss the reason why you should always supply the value of ‘Process Mode’”
–> Did you publish anything else regarding this ?
Could you give the Change Request / Bug Id ?
Sorry, I thought a bug was logged by Oracle. It is probably not the case.
Do you have any idea how to set the description on the Job created in Server Requests (Admin Server - Jobs) ?
Comment Now!