A great tip shared by Sekhar user of Siebel Unleashed Forum and reader of my blog to make debugging easier in Siebel. This is bound to help all.

================================================================

The Easiest way to troubleshoot the events the actions fired on those events is through LOG. You just need to give a parameter in Client CFG

In the [Siebel] section of the CFG, enter the below

PersonalizationLog = C:\Personalization.Log

It will log all the Events and Actions fired in Personalization.Log file.

==============================================================

I tested it myself and below are the contents from Personalization log file

{S(1)T(1217307942.748)U(SADMIN)K(13)Y(Event)N(Y)}
——————————————————————————-
Event, at 07/29/08 10:35:42.920, sequence 2
Object type: Application
Object name: Siebel Power Communications
Event: WebSessionStart
Sub-event:

Processing action set ‘CUT eSales Web Session Start Action Set’ …
processing action ‘SetApplicationName’ …
processing action ‘SetPriceList’ …
processing action ‘CUT Set at Login’ …

{S(2)T(1217307942.920)U(SADMIN)K(13)Y(Event)N(N)}
——————————————————————————-
Setup Profile, at 07/29/08 10:35:46.030, sequence 3

84 user profile attributes initialized.

{S(3)T(1217307946.030)U(SADMIN)K(13)Y(Setup Profile)N(N)}

Thanks sekhar for sharing it with us.

OkAvarageGoodVery GoodExcellent (5 votes, average: 4.8 out of 5)
Loading ... Loading ...