Archive for April, 2009
You are currently browsing the GeeKs Blogging @ dotCOM blog archives for April, 2009.
30
Apr
2009
A meeting with Siebel EAI
Hi,
Here I am, with my promise of introducing the Siebel EAI Series. My Analytics stats show a lot of people new to Siebel venturing onto GeeksBlogging@dotCOM, and so I thought it might just be a good idea to have a cup of tea with Siebel EAI, just from the introduction point of view, before we get into detailed topics.
I will just twist the acronym EAI aka Enterprise Application Integration to mean Integration of various Enterprise Applications. Siebel CRM Software to realize CRM, the concept, has to exist for our discussion to center around Siebel EAI!
30
Apr
2009
Sugar CRM launches Sugar On Demand
Sugar CRM has been the most prominent Open Source CRM available in the market. Though others are close on the heels, I believe Sugar’s adoption and influence has by far been the greatest of all the Open Source CRM packages available. So much so, it also packs the greatest number of features in the Open Source competition space.
Sugar has now launched “Sugar Express”, the On Demand or the hosted version of Sugar CRM aka Oracle’s CRM On Demand and Salesforce.com.
29
Apr
2009
Siebel – Scrolling between records – UP and DOWN
Generally in Siebel Client, we very often have the need to scroll Up and Down among the records. Most of the users would need an easy solution of scrolling UP and DOWN in the records using the normal UP and DOWN arrow keys on the keyboard. Siebel provides an Out of the Box functionality where we use the CTRL + UP or CTRL + DOWN keys to scroll through the records.
I will try to cover here as to how we can customize and modify this OOB functionality such that user can scroll among records using the normal UP and DOWN arrow keys on the keyboard.
28
Apr
2009
Siebel – EAI Series on GeeksBlogging@dotCOM
Siebel EAI, aka Enterprise Application Integration is generally the most sought after area in Siebel among most of the Siebel Developers that I have come across, whether they are currently working on Siebel or not. Honestly speaking, I am still trying to understand the confusion. As far as I am concerned, “I like EAI because I like interacting with other systems, not just Siebel”. Does that work out enough in my support?!! 
26
Apr
2009
Siebel – Unable to launch Local Client
Hi all,
I was making a fresh install of Siebel yesterday, when something very strange happened. I could not launch my Local Client. This was even more strange because:
1) I could successfully launch my Sample Client
2) I could successfully launch my Local Client when invoking it in Debug mode from within Siebel Tools!
25
Apr
2009
Siebel – Unable to check out objects
I will discuss the following most prominent ways to enable or disable object level check-outs in Siebel here:
1) EnableObjectCOCI parameter
2) Allow Object Locking
I will explain these terms here.
24
Apr
2009
Siebel – HTML Code displayed in Error Message
There was a requirement in our project to make Account Field required in Quote entity conditionally. I have already discussed the solution to this and to show the red asterisk in my previous posts below:
Making a field conditionally required
Showing * on a conditionally required field
When user was creating record from list applet and on saving the record he got the right message as “Account is a required field”.
But to our surprise, when record was being created from form applet and now if the user saves the record, he got the following message..
23
Apr
2009
Siebel – Showing red asterisk on a conditionally required field
In Siebel vanilla Application, we see a red asterisk ( * ) in case the field is Required. However, this asterisk is not shown in case the field is made required conditionally through customization.
We had a similar requirement, to show the red asterisk against a field in the form applet, which was required conditionally. I have already discussed how to make the field read only conditionally in my previous post.
22
Apr
2009
Siebel – Make a field Required, conditionally
There was a requirement in our project to make Account Field required in Quote entity conditionally. Had it not been optional, we would have done this by the setting the ‘Required’ property to TRUE for the field in the applet. But, then it would not be conditional, and would always be required.
22
Apr
2009
