Posts

Siebel 8.1.1.10 brought with it what is called “Incremental Repository Merge” known simply as Siebel IRM. The objectives are novel: Move away from the optional ACRs to apply incremental changes for a point release (e.

You want to order a new cooking gas cylinder (most of us here in India do not have piped gas, bear with me). What would you rather do? Visit your friendly distributor to ask about his health and order the cylinder using that opportunity Talk to a grumpy guy over at the customer service representing the gas company or distributor through phone Order the cylinder through the web site Send a SMS For most of the people like me #4 should be an obvious choice.

Siebel has not been a big follower of market trends recently. But from time to time we see a new story that catches the imagination of Siebel developers, if none else.

Recently we were evaluating options to cater to Siebel infrastructure needs of a customer external to their data center, and the most obvious choice was Amazon Web Services. It is not only that AWS is big, and the best known player in the market, but also that it provides the most flexible, more powerful options for any company looking to move out of its own data center.

Performance in Siebel is often the cause of angst for IT architects, managers and developers (not necessarily in that order). Typically a Siebel performance issue in production goes through following steps:

We have mostly expected news and somethings unexpected in the recent Gartner Magic Quadrant for CRM (2013). We talk about Sales Force Automation (SFA) here, since that is the most common talked about area.

Oracle is not on the CRM Magazine’s 2013 leader board. I would probably not even notice this, except for the pretty bad patch that Siebel is going through. A few facts that puts this in the perspective though:

Unit testing is something that I always want to attain perfection in, but almost never do. Not delving in the challenges/resolution action in the process/ execution in a packaged product implementation scenario, I want to take this article in a different direction – test driven development for Siebel.

A discerning reader might remember the trace on demand utility posted here last time. It was fairly simple vb script that gets the job done, and is adequate for a developer.

Adding complex, dynamic business rules in Siebel has never been an easy task (well, for all verticals anyway). Architects and designers have learnt to play around with Siebel SmartScripts, tools/client-side scripts in combination with Siebel Workflows and other business layer validations to achieve the required flexibility and maintainability, but not compromising on performance.