Recently I have met with the Problem in form of defect. The Problem was related to Record Visibility in Activity.
There were activities created for SR as a result of Email Response and properly visible in Activity List Applet under SR. We have Pick Applet in SR Applet for fetching all Email related activities. But strangely same activities were not visible in the Pick Applet.
In my last project,we had a requirement of Admin Views, so the admin users if required can change the data from frontend and not going to backend and running update queries.
Admin Views are those views in which all the records are visible to the person who has access to this view irrespective of the position of the person.
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.
This is a nice tip I ran across. All the Siebel Developers use Siebel Tools and Siebel Web Client extensively. And, each one of us run over a hundred queries daily. However, when querying for some data, for eg. a Business Service Name in Tools, Siebel generally demands we enter the correct case. To streamline the process and improve productivity, I continuously keep making minor modifications in my environment settings.
This is a smaill tip I was working on, which got me interested in Symbolic Strings all of a sudden. We have already discussed previously about the Symbolic Strings
Siebel – Symbolic Strings
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.
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!
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.
Consider this article as a simple overview of Siebel Configuration. We will cover how a typical day in the life of a Siebel Configurator is most likely to be like.
Siebel is a Tool in itself. It is a Customer Relationship Management system, which Oracle has kept as close to the global standards as it could, and it has done a good job at that, I must say. In most cases, it is similar to any customized CRM software you may come across, just that most of the views, and Data Organization that you would yearn for, would be available Out of the Box when you install Siebel CRM.
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.
System should have capability to automatically save opportunity(RFPs) data in Draft state after a certain interval.
1) The Business Component to be used for the UI applet should not have any required fields at the Table or BC level itself or All the required fields should be pre-defaulted with some unique values.
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.