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
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.
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.
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.
Siebel – Merge Records Functionality
How many times have we realized that there are multiple records exisiting in our database with nearly the same values? The next though with a bolt of lightning is, how the hell were two records with similar data entered into the system, with all the fundamentals of Primary Keys and User Keys.
Well, the answer could be that though none of the User Keys were violated, data was common in the other fields except the User Key fields. For example, we may end up having two Contact records in our system, which we realize actually point to the same CONTACT. So much so for blasphemously expensive CRM Systems!
Siebel – FINS Teller UI Navigation
Siebel is POWERFUL! Now, need I even say that? And, in all its beauty and glory is the vanilla functionality. I keep coming across something new and novel everyday, and wondering, what percentage of 1% of Siebel do I now understand?!!
Here is another such Business Service that I came across the other day, “FINS Teller UI Navigation”. It has the following methods (my uncalled personal analysis is mentioned herewith):
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 – Looping Multiple Records – III
Looping through multiple records is a requirement we come across multiple times in almost all Siebel Implementations. And, I can’t recall how many times I have seen dirty scripts to achieve the objective.
I call this Part III, as we have already covered this before on GeeksBlogging@dotCOM, in the articles,
Siebel – Looping multiple records – Query and Process
Siebel – SIA BC Utility Service – Loop multiple records
Siebel – Popup Update Only
Hi all,
I was working with Siebel Multi Valued Links (MVLs) for some of the configuration requirements in our project. Siebel Configuration is a vast world in itself. I always feel I am learning something new everyday!
We generally use MVLs to fetch data through typical “Links” that we configure in Siebel BCs. We once across an interesting requirement which I am sharing with all of you.
Requirement: To suppress the opening of the MVG Pop up Applet for a particular Multi Valued Field (MVF).
Siebel – LOV Number Limitation
Siebel List of Values is probably the most commonly used entity in almost all the Siebel EAI projects. I have seen people use LOVs for all sorts of crazy things – storing Language Translations (most common use!), reverse translations, holding Pricing Information, identifying incoming interfaces, setting up a list of allowed values (for eg. in an incoming XML tag), using the Description field to increase the max length that can be stored and what not!
Siebel List of Values have found such profound use and application, possibly because of the famous LookUpValue() function, which can quickly pick out values from the S_LST_OF_VAL table. The LOVs are cached which make this function work even faster and helps Performance. It does have its own set of pains, however.
Siebel – Make MVG Field required – II
Hi friends,
This is a follow-up post of the post by Prachi yesterday about making an MVG field Required. You can read the post here. Yes, this truly is an issue in development as the straight OOB methods don’t seem to work at first. However, I personally am quite strongly against scripting in any case anyways!
Nice work, Prachi. But, I feel we may be able to implement the same requirement by simple configuration. Just that it is not so evidently displayed at first.
Siebel – Make MVG Field required
Siebel supports the concept of Multi Valued Fields, or the MVF. These generally relate to fields such as Addresses, or Contacts which may possibly be more than one for a particular Account record. You would generally notice an Inter table which would further store the details.
One of the major problems that pops up is to make these fields Required. This does not work if set at Field level or using the Required User Property for these Multi Value fields.
This can really frustrate the developer.