siebel

Time again to stimulate your grey cells. Architectural differences between SI and HI clients are well documented. Recently working with SI application we observed a strange thing. SI client handles processing of error/Validation messages from BC layer and UI layer in different ways. While invoking RaiseErrorText from BC error message was displayed on the top view bar but while invoking the same from applet was taking to different error web page resulting in context loss. User has to click Back button to go to previous page. Same holds true for DVM messages. While invoking from BC layer using run time events the error message is displayed on the same view but while invoking from UI layer error message is displayed in different error web page. I am not able to break this thing why it behaves differently on different layers. Any insight/thought on this would be of some help. Happy Debugging!!

Issues are inevitable as sugar and cholesterol. In my recent heist in configuring recipient groups i was dumbstruck with some untold user property. We wanted to add Person as recipient group for Service Request. As per siebel support we added desired values in the "COMM_RECIP_SRC" LOV table. Email started to flowing using this recepient group. But the interesting part is "Person" BC is not defined with the Recipient* user properties instead of that only one user property is defined as Name - SecUsernameFieldSubstitution: EMail Addr Value - Email Address Unknown of its usage thought of throwing this to siebel forum. A little insight on this user property will be of great help. Happy Cracking!!

Lot of things in siebel are still not documented. Talk about those magical user properties or custom classes with super natural powers, most of them needs to be discovered by trial only. Recently while working on the Siebel ASI, my eyes started gleaming when i saw "Siebel-Authored" flag in Data Map editor screen. My initial hollow guess was this flag might be used by siebel to identify predefault data mappers which are used by ASI. But after checking in sample i confronted that this flag was blank for all records. Out of curiosity i started searching for usage of this flag but was not able to hunt down much. Please feel free to add comment in case you have any clue about this flag. Happy Cracking!!

One of the admirable features of Siebel is its GUI, which allows us to accomodate all the frills and fancies of user. Recently i was asked by one of my colleague to implement i-want-this type of functionality which involved character counter for TextArea field, which should display count of remaining characters which could be filled, in standard siebel eService application. After hours of hit and trial, i came up with one dirty solution. Lets consider we need to have character counter in place for Description(Maximum 250 characters) in form applet. A basic solution is to have a control below the Description which will display the count of characters left. The document Id for Description is 's_1_1_11_1' and Counter is 's_1_2_45_1'. We can obtain the document ids by richt click on the page. Now comes the key part where we need to add logic to count the characters in Description and populate the counter. This could be accomplished by HTML Attributes property of Descriptio...

Workflow Policy Programs are generic events that used to trigger certain actions whenever policy conditions are met. Siebel comes with predefined set of Program types. Policy programs can be of any developer's delight if used effectively. However these Policy Programs are invoked only by workflow Policies (as per my awareness). So the question for all siebel gladiators is whether it is possible to invoke Workflow Policy Program by any other means. Any clue on this piece of puzzle will be of great help. Keep cracking!!

Working on a Project without any issue is like watching batman movie without joker. An alien issue which has been bugging me from long time is how we can have different columns in list applet while opening in Query mode. Consider an example of SR list applet. "Edit List" applet mode is being used in the View web template which displays SR Number, Status and Area but when user queries on this applet he should see Sub Area and Sub Status along with above fields in query mode. One go to solution is to use "Base" mode in View web template but this will not suffice other scenarios. Any tip/thought/comment/break from you siebel champions will be of great help. Let the quest begins.