Siebel – EAI Queue – Usage
I had introduced the concept of Siebel EAI Queues in my last post. You can read it here.
Today, I would discuss its usage, as to how we can use it in our implementations.
A simple ‘About View’ of the EAI Queue screen shows us that the two applets are based on the following -
| Business Component | Table |
| EAI Queue | S_EAI_QUEUE |
| EAI Queue Item | S_EAI_QUEUE_ITM |
Siebel – EAI Queue
Okay, what are you thinking about? Is it Middlewares in EAI with their queue managers and queues? No, those are not the ones I am talking about. Every EAI professional knows about those.
Siebel provides an Out of the Box Message Logging mechanism for Siebel EAI messages. This is done through a Siebel feature called ‘EAI Queue’ which I would be discussing in detail in this article.
I have tried to provide a basic idea about message interchange in EAI in my last post. You can read it by clicking here.
Siebel – HTML Code displayed in Error Message
There was a requirement in our project to make Account Field required in Quote entity conditionally. I have already discussed the solution to this and to show the red asterisk in my previous posts below:
Making a field conditionally required
Showing * on a conditionally required field
When user was creating record from list applet and on saving the record he got the right message as “Account is a required field”.
But to our surprise, when record was being created from form applet and now if the user saves the record, he got the following message..
Siebel – Make a field Required, conditionally
There was a requirement in our project to make Account Field required in Quote entity conditionally. Had it not been optional, we would have done this by the setting the ‘Required’ property to TRUE for the field in the applet. But, then it would not be conditional, and would always be required.
Siebel – LookUpName() and LookUpValue()
Hi all,
I was working for a multi lingual implementation recently. This means, the Status on the Order Header was in English if the language selection of logged in user was English, and in Swedish if the language of the logged in user was Swedish.
I came across this problem that at times when the user invoked my custom method on the Orders screen by clicking a button, the Order Status value was passed in his native language – English (ENU) or Swedish (SVE).
Siebel Assets List view – Performance issue / Cannot display records
Assets Screen Load is a major problem in Siebel, and a major pain area for the concerned developer. I am sure many of you would have come across it in one implementation or the other.
If there are more than 10,000 records in Assets screen, vanilla Siebel Application will not load the screen.