Posts

Siebel provides tens of ways to accomplish one task. Creating files is a good example to explore the myriad ways to create a text file and populate it with content.

Most IT projects I have seen suffer from the low-estimate syndrome. I take full responsibility for projects I own and execute, since I behave like an idiot and be too aggressive when it is not required.

Insight.ly calls itself #1 for small businesses, and over 50,000 users. So, does insight.ly cut it when it comes to CRM. Let’s go check it out. What is Insightly? #Insightly is an integrated CRM and project management application that is targeted at small businesses.

Siebel scripting is powerful. But, frustratingly slow to create - thanks to the slow debugging process in Siebel. When you are writing scripts, you follow a simple process - Select a specific event in the Applet, BC or Application Create the script (hopefully review it) Compile script Test, and find something that is not working Rinse, and repeat In the age of dynamic languages, this introduces a slow process for script development.

Well, we have all been there at some time. The problem is frustrating, but the answer seems deceivingly simple. This time it is Siebel client. It does not really matter whether it is local database, or sample.

Siebel Mobile Clients are not only the only way to enable disconnected application for “remote” users, but also have been the development platform for Siebel developers. It was quite sometime back that Siebel provided two modes for a disconnected client - Siebel Mobile Client and Siebel Developer Client.

Really. What constitutes CRM? If I can put it down in bullets, they would probably be: Know who your current and potential customer is (hitherto known simply as ‘customer’) Engage your customer and “manage” all touch points with customer Know what customer is telling you and about you directly and indirectly Know your own performance against your stated objectives regarding customer A few thoughts on why only four points are below.

I am of the view that: Development = 80% debugging, 20% writing new stuff. Debugging your own code, or that written by others is what you will do most of your coding life.

Siebel has multiple debugging tools, but sadly not much is said or written about them. Here is one tool that is used by a section of developers, but ignored by others.

“Communication templates” - so boring a name for such an exciting thing that enables sending emails. Siebel had communication templates as long as I can remember. Their function was simple and straight forward - enable user/system to send emails ad-hoc or using a pre-defined template.