Service_InvokeMethod Event
Siebel CRM calls the Service_InvokeMethod event after it calls the InvokeMethod method on a business service. This event does not return any information. For more information, see Service_PreInvokeMethod Event.
Server Script Format
Service_InvokeMethod(MethodName, InputArguments, OutputArguments)
The arguments you can use in this format are the same as the arguments that are described in InvokeMethod Method for a Business Service.
Browser Script Format
OutputArguments=oService.InvokeMethod(methodName, InputArguments)
The following table describes the arguments for the Browser Script format of the Service_InvokeMethod Event
Argument | Description |
---|---|
methodName |
A string that contains the name of the method that Siebel CRM must run. |
InputArguments |
A property set that identifies the arguments that the method uses as input. |
In Browser Script, you cannot use an output property set for this format.
Usage
You can use this event in the following ways:
In Server Script. It can add properties to or modify values of the properties in the property set that the OutputArguments argument identifies.
In Browser Script. It cannot modify, store, or update the values of the properties in the output property set.
If you call a business service method through Browser Script, then the business service that this method calls can use a browser or the Siebel Server. Siebel CRM determines if the business service resides in the browser. If the business service does not reside in the browser, then it sends the request to the Siebel Server.
Browser Script can call a business service on the browser or the Siebel Server. Server Script can call only a business service on the Siebel Server.
Used With
Browser Script, Server Script
Examples
To handle transactions that are not approved, the following example in Siebel eScript adds custom logic to the predefined Credit Card Transaction Service business service:
function Service_InvokeMethod (MethodName, Inputs, Outputs)
if (Outputs.GetProperty("SiebelResponseMessage") != "Approved")
{
// special handling for failed transactions here
}