siebel

Welcome back to the next (!last) post in UMF series. In this we will discuss how we can capture responses and perform actions from the popup applet. It basically involves two steps: 1 - Creation of business service with different methods which needs to be invoked on selecting responses from message applet.Create a new business service "ResponseService". Add three Methods to this BS: AddInfo AssignRequest OpReq function Service_PreInvokeMethod (MethodName, Inputs, Outputs) { switch(MethodName) { case "AssignRequest": fnAssignReassign(Inputs, Outputs); return(CancelOperation); case "AddInfo": fnAddInfo(Inputs, Outputs); return(CancelOperation); case "OpReq": fnOpReq(Inputs, Outputs); return(CancelOperation); } return(ContinueOperation); } The best part is entire payload of the message is passed to the response thus allowing us to use them in response functions. 2 - Now its time to map the business service and met...

Many times we have resorted to browser scripts for displaying message and based on the input given have decided steps to follow but with the introduction of UMS the dependency on the browser script can be avoided. We can do wonders with the UMS framework which can really help in orchestration of system. UMS is highly used in Order Management however Siebel is kind enough to allow us to use this for any other standard BO. However we need certain level of customization and scripting to achieve this. The main advantage of this framework is to invoke popup applets from workflow. I was not sure whether it was possible or not but as they say absence of evidence is not evidence of absence. A more than little help from support web and universal buddy Google made it. The details of Unified Messaging Service is available in OrderManagement guide. Here we will try to construct and invoke message from Service Request List Applet. It will display snapshot of Service Request which will help SR agent...