Siebel – Symbolic Strings – Change default ‘X_’
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
Siebel EIM – USING SYNONYMS
Performance is always a major issue in most of the Siebel Intallations. In a project where large scale EIM Processing is needed, rest assured, Performance would be the from amongst the most discussed topics, at least from the Acceptance Testing phase, if not before!
EIM Data loads can turn out to be for millions of records, and many tens of GBs of Data being imported is a common sight (talking in terms of the Oracle Database Data File footprint). The customer has to be around that size, if he is actually going in for a Siebel CRM implementation I guess!
Siebel – Automatic User Logout
Logging out a user automatically, when the user does not explicitly logoff.
This one came up as a request from NP on GeeksBlogging@dotCOM. I believe this would possibly be a very frequent issue and a common problem in almost all the Siebel Installations. The users generally come from a Sales background. They hardly care how they actually close the Siebel Application. In most cases, they just press the (X) button on top of the Browser window, rather than explicitly selecting File -> Logout.
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.
Siebel – Refresh Applet retaining existing context
RefreshRecord() does not work in all cases, does it?
This is a very common requirement I have seen in almost all Siebel EAI implementations. We have data flowing IN and OUT of the Siebel CRM system. It is updated in the Database alright, but, how do we update the user on the UI. I am assuming a quick data interchange in Real-time using a VBC or a Web Service or something similar. Whenever we update the Database using a Workflow or a script here, the UI will not refresh automatically, and though the process would end successfully (I hope it does), the user would never come to know about the successful updation until he manually does a Query + Go on the Applet, or uses the famed Alt+Enter Hotkey.
Siebel – EAI Siebel Adapter – Looping Multiple Records
This is a follow-up post on the post, Siebel – Looping Multiple Records – III. We are looking at possibly more conventional methods to loop through multiple records in Siebel, than the SIA BC Utility Service.
We will make use of EAI Siebel Adapter’s QueryPage method to achieve the same. Knowledge of Siebel Workflow processes is essential to understanding this post.
The QueryPage method allows us to input an additional parameter, NumOutputObjects, to define the number of records that we want to output. Why not set this value to ‘1′?
Following is an outline of the Dummy Workflow I used to achieve this.
Siebel – EAI Siebel Adapter Search Spec
Hi,
I can bet that for anybody who has worked on Siebel EAI, ‘EAI Siebel Adapter’ is not an Alien term. This post is about EAI Siebel Adapter’s Query method.
How to restrict the number of Child records returned in Siebel adapter’s Query.
Scenario – Order and related Order Line Items
Siebel – FINS Industry XML Query Service
“Extracting values from a tag deep down in the Hierarchy.” How many times have you come across this problem, and how many times have you wished that Siebel has an OOB method to help you extract these values?
Well, here it is. The “FINS Industry XML Query Service” in Siebel does just that. I am covering this here because of lack of documentation on the same by Oracle, and the immense use that this can be put to. This BS can save you a lot of headache of writing custom scripts to parse the entire XML Hierarchy in Siebel eScript, which can be a real pain in the neck.
This blog post will target the detailed usage of the BS, “FINS Industry XML Query Service” in Siebel CRM. This BS can be used directly in a Siebel Workflow, since this is vanilla. No scripting is needed which is as per the recommendations of Siebel Best Practices.
Siebel – EnableServiceArgTracing – Logging Messages
Hi,
We have already discussed at quite a length the logging methods, the most prominent of these being the usage of vanilla Siebel EAI Queues. You can read about the entire series through the following links:
A meeting with Siebel EAI
Siebel – EAI Queue
Siebel – EAI Queue – Usage
Siebel – EAI Queue – a Critique’
I recently came across another vanilla method (EnableServiceArgTracing) to log the messages. Using this, the various Siebel logs can be created, and the Input and the Output messages to some of the Business Services can be written in XML format to a file. These XML files would appear as Siebel Dump files with a “.dmp” extension. These can be read off any standard text reading tool like Notepad, Editplus, Notepad++, etc. This process works with EAI Siebel Adapter and EAI Dispatcher business services.
Siebel- Close Browser window when logging off
In case of standard interactivity applications like eSales , eService, when user logs off, he is directed to the page through which he logged in the application. But there is a requirement to close the IE when user logs off. Here we are doing this for eSales Application. This can be done in following manner:
• Create a new .swt file say “LogOffDestination “ which contains following HTML script:
<html>
<head>
</head>
<body>
</body>