24
Jul
2009
Siebel – Merge Records – Checklist
I call this Part III, and concluding part of a series of my posts on the Merge Records functionality in Siebel CRM. You may want to take a look at the previous 2 parts below:
Siebel – Merge Records functionality
Siebel – Automating Merging Records by script – II
Though this looks like a very interesting and useful utility from the face of it, it can be dangerous too.
7
Jul
2009
Customer Relationship Management – not just fancy software
Customer Relationship Management (CRM) is a very wide domain in itself. I always like to see Customer Relationship as a concept (of which Software is one part) rather than the Software Solution itself.
I am sure I have better relationships with my local Grocer than the fancy stores and supermarkets all over the place. Refer to the KMart, Coles, Fanklin’s, Reliance Fresh, or the Birla Group’s more.. supermarkets, none of them knows me better than my local guy who has been selling me spices, flour, paddy, and my other daily needs for so many years now.
4
May
2009
Siebel – EAI Queue – a Critique’
I had introduced the Siebel EAI Queue and its usage in my last articles. Though Siebel EAI Queue is a very good Siebel feature, there are some serious shortcomings as well. An architect would, thus, need to critically evaluate all the pros and cons before deciding to implement the OOB EAI Queue or a custom solution in a Siebel EAI project.
First let’s look at all the areas where Siebel EAI Queues stand strong.
1) No customisation needed
This is an OOB fucntionality. So, no custom coding is necessary. The vanilla BS can directly be called from the WF to help operate the EAI Queues. Custom code comes with its own sets of problems – dedicated human resources, architecting, implementing, testing, debugging, performance, scalability, expandability, robustness.