Siebel CRM 7.8 – Signals Demystified.

Anybody who has worked on Siebel 7.8 must have come accross the term ‘Signal‘. I came across this term just a few months ago. When were wroking for some Performance issues in our Project. It is one of the most useful thing that I have come across in Siebel in past 2 years of experience. It has the ability to change the way we do lot of things.

What I found out during my Reaserch to find out more on singals is the fact that it is absolutely not a new thing in siebel. It has been part of siebel from very start which is way back in Siebel 6. I know you might be confused a little bit. Let me explain.we all know that siebel is a Event Driven language. We can choose to handle those events or let siebel handle those events.In events we do some coding for the custom methods that we have defined. And we all know that in the end we have to write a statement ‘return(CancleOperation)‘. Of Late what I knew was that we just have to write this statement otherwise we get and error message ‘MethodName is not Supported’.The reason for this kind of behaviour is ‘Signals’ that’s right!!! Signals are responsible for it. Now I will explain how.

Everything Method Invoked in Siebel is a ‘Signal’ which is passed on to the C++ code that makes the core siebel. When a vanilla method is invoked such as ‘SetFieldValue’ , ‘GetFieldValue’, ‘InvokeMethod’ Siebel has the code in it is C++ Classes to handle it. But when we invoke the custom method Siebel has absolutely no idea how to handle that code. So, we write the statement ‘return(CancleOperation)’ so that the custom method never reaches Siebel C++ code.

Now the question is what has changed in Signals in version 7.8? Well, the answer is Prior this version of siebel we coudn’t create custom signals and we couldn’t modify the existing signals. But now in Siebel 7.8 we can change vanilla singals and also create new signals.

The view that let’s us do that is Adminstration ==> Order Management ==> Signals.You can see in this view a lot of signals related to pricing as they are used extensively for Pricing in siebel. But you can also see signals like ‘SetFieldvalue’.In my next post I will be explaining in detail how we used Copy and Revise Vanilla Signals to rectify the performance issues related to Copy and Revision of Quote.

If this post has been helpful. Please post your comments and visit again for more.

18 Responses to Siebel CRM 7.8 – Signals Demystified.

  1. hai,
    good to know about a new term in siebel,which i havent heard till now..i want to know more on this with examples and would like to know where to find more info on this topic “signals”.

    Thanks& Regards
    Phani

  2. hai, good to know about a new term in siebel,which i havent heard till now..i want to know more on this with examples and would like to know where to find more info on this topic “signals”. Thanks& Regards Phani

  3. Well, I myself have been trying to find more information in siebel. But they are poorly documented in Siebel 7.8 bookshelf without any examples. I have included another post to show more details. Hope,you have read that. Will update once I am able to find more details on comments

  4. Well, I myself have been trying to find more information in siebel. But they are poorly documented in Siebel 7.8 bookshelf without any examples. I have included another post to show more details. Hope,you have read that. Will update once I am able to find more details on comments

  5. Hi All,
    Signals are well defined in the Order Management Infrastructure guide. i have worked with Signals and the documentation helped me enough to suffice many functionalities. To add on above. Signals are the messages which are passed from One entity to another in order to communicate. Like if you are working on Orders and you want to create a workflow to operate on Orders and line items. You can provide the workflow name in the signals and can use the same signal using invoke method(signal name) behind a button. Signals can invoke BS and Wf which help us work on entities. I belive the Signals are very specific to Order management entity and it should be licenced.

    NS

  6. Hi All,
    Signals are well defined in the Order Management Infrastructure guide. i have worked with Signals and the documentation helped me enough to suffice many functionalities. To add on above. Signals are the messages which are passed from One entity to another in order to communicate. Like if you are working on Orders and you want to create a workflow to operate on Orders and line items. You can provide the workflow name in the signals and can use the same signal using invoke method(signal name) behind a button. Signals can invoke BS and Wf which help us work on entities. I belive the Signals are very specific to Order management entity and it should be licenced.

    NS

  7. hello author,
    i would like to add my understanding to the article that is about signal and classes

    according to my understanding on signals, is signals are dependent on specific class based BC like quote.
    and that is because pricer engine is designed such a way.

    If you can explain us how classes are internally configured , and whether or not we can configure them to support signals on other BC’s
    just to cross check this ,just change the class of quote/item BC and then try to invoke any signal.
    let us know the output.

  8. hello author,
    i would like to add my understanding to the article that is about signal and classes

    according to my understanding on signals, is signals are dependent on specific class based BC like quote.
    and that is because pricer engine is designed such a way.

    If you can explain us how classes are internally configured , and whether or not we can configure them to support signals on other BC’s
    just to cross check this ,just change the class of quote/item BC and then try to invoke any signal.
    let us know the output.

  9. Hi Neel,
    Your contribution to siebel through this website is awesome. I recently visited this site and was very impressed with the information and the way it was presented.

    Can you explain me about the variable maps with a case study if possible as i found the bookshelf is too confusing

  10. Hi Neel,
    Your contribution to siebel through this website is awesome. I recently visited this site and was very impressed with the information and the way it was presented.

    Can you explain me about the variable maps with a case study if possible as i found the bookshelf is too confusing

  11. This seems to be the True definition of “Signals” as per Siebel perspective.

    Signals can be known as means of Communication between the Entities with the help of Wfs or BS.

  12. Hi Neel,

    Thanks for the wonderful post!

    Due to performance issues, we have decided to switch back to manual pricing procedure from the dynamic one. I am unable to figure out what signal changes I would have to make in order to switch it back to the basic pricing procedure. (There are a no of signals – CalculatePrice, CalculatePriceAll, CalculatePrice_Configurator etc.) Any light on this topic would be really helpful.

    Thanks.

  13. Great explanation for the statement ‘return(CancleOperation) in case of custom mathods.I used to use it for my scripts but now its crystal clear why we write this statement.Thanx a lot.

    regards
    Dharmvir

  14. Sorry to say that. But you’re absoletly wrong about Signals and Events.
    Signals are introduced in 7.8 by Order Management to make events administrable. To modify or add a signal you need C/OM (Customer Order Management licence).
    When Invoking a method on applet or BC or BS without CancelOperation, siebel tries to invoke the method on the class (no signals are raised). You can check this on your client logs.
    MethodName is not Supported’ means that the class doe not have or does not expose the method.

Leave a Reply

Contribute