19
Aug
2009
Siebel – Case Insensitivity (CIAI) Wizard
CIAI stands for Case Insensitive and Accent Insensitive in Siebel. This can be called the first post on GeeksBlogging@dotCOM on Siebel 8 New Features.
I had discussed about some traditional methods of controlling Case Sensitivity in Siebel queries. However, in version 8.0, Siebel has introduced a new feature of the CIAI Wizard which goes a step further in controlling this functionality. This has been carried forward in Siebel 8.1 albeit with some minor modifications.
13
Aug
2009
Siebel – Symbolic Strings – Usage
Symbolic Strings appear directly in Siebel Tools’ Object Explorer, an independent object. It has a child object of Symbolic String Locale, where you may define the individual translations for all the different languages in use in your project.
In case it is not visible directly, navigate to View -> Options -> Object Explorer tab, and enable the Symbolic Strings object if not already visible.
12
Aug
2009
Siebel – Left, Right and from the Middle
Extracting a sub string from a lengthy string in Siebel. What is the best solution you can think up for this typical problem? I know, I know, you and you colleagues have done this thousands of times before. But, have you ever successfully done it without using a single line of scripting?!!
Now, it becomes interesting! 
12
Aug
2009
Siebel – Symbolic Strings
Consider this a brief introductory tutorial on Symbolic Strings in Siebel. Symbolic Strings are from amongst the most commonly used entities in Siebel, especially in Siebel Multi lingual deployments.
They can greatly reduce the job of initializing, deploying, tracking, modifying all the plethora of error/warning messages that you may generally come across in a typical Siebel CRM application.
28
Jul
2009
Siebel – Autosave Opportunity data – Sample Code
This is a follow up post on my previous post, Siebel – Autosave Opportunity data – The concept where I introduced the concept and analysis of the following problem statement:
“System should have capability to automatically save opportunity (RFPs) data in Draft state after a certain interval.”
Following is the sample code for solving the above problem statement.
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.
24
Jul
2009
Siebel – Fetch Active view properties – III
I will discuss a practical example, and the corresponding Inputs as a usage example for the “FINS Data Transfer Utilities”. If you have not already done so, I would suggest going through the previous posts for a better understanding:
Siebel – Fetch Active view properties
Siebel – Fetch Active view properties – II
23
Jul
2009
Siebel – Fetch Active view properties – II
We discussed about fetching the values from the active view in my post yesterday.
However, I also felt that it was a very crude way of doing it. We can only get the information we need, by writing a small script for it. Moreover, the information was very limited.
22
Jul
2009
Siebel – Fetch Active view properties
Hi,
Working on a typical requirement recently, I came across a need to fetch the properties from the user’s active view. This was an attempt to recognize the user, and the details about the Siebel view/screen he was in.
On research we can see that there are a number of Application level methods which we have at our disposal.
22
Jul
2009
Siebel – Automating Merge Records by script – II
I call this Part II, as I have already introduced the Merge Records Siebel functionality, and discussed its usage in his post. One of the interesting discussions we had was how such a data could possibly be inserted into the Siebel system, since Siebel has so many mechanisms to prevent Data Corruption. We had also zeroed in on EIM and EAI as the basic culprits which could possibly insert inconsistent data into the Siebel Database.
