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.
27
Jul
2009
Siebel – Autosave Opportunity data – The concept
Requirement:
System should have capability to automatically save opportunity(RFPs) data in Draft state after a certain interval.
Presumption:
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.
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.
16
May
2009
Siebel – millisecond dates on Applet
I had discussed in my previous posts about invoking a BS in a calculated field for complex calculated calculations, and, about finding out dates accurate to milliseconds. You can read about them from the links below:
Invoking a BS in a calculated field
finding out dates accurate to milliseconds
Today, I will discuss as to how we can show dates on Applets with upto millisecond accuracy. This could be of immense importance in EAI projects as one example, wherein we need to calculate the time spent on each step. Performance debugging could be really enhanced by using this method.
15
May
2009
Siebel – getMilliseconds() usage
Siebel by default displays all dates in the system accurate to the seconds place. However, at times, especially in EAI based projects or performance intensive projects, it is often a requirement to calculate accuracy down to the last millisecond.
Siebel provides a ready made function called getMilliseconds() for this functionality.
I wrote a simple script in Siebel Local Client to demostrate this functionality. The contents of the script, “Dummy Get_MS Test” is:
12
May
2009
Siebel – Looping multiple records – Query and Process
In my last post, I discussed as to how we can query and update multiple records in Siebel Database. You can find it in the link below:
Siebel – Looping multiple records – Update.
Today, let’s see if there are some good ways to loop through multiple records in Siebel in Query mode, and process the data in each of the records one by one. Let’s assume the requirement statement is, “To query for these multiple records and send them to external interface one by one”.
11
May
2009
Siebel – Looping multiple records – Update records
Hi,
We often come across a requirement where we need to loop through multiple records satisfying a certain search spec on a particular BC.
Let’s assume a simple search spec, for eg. to update the Status of all Sales Orders to Submitted which have their Account as “Nitin Test Account”.
10
May
2009
Siebel – InvokeServiceMethod() on Calculated Fields
InvokeServiceMethod() is used to invoke Business Services and take values from it in case of Calculated Fields.
I actually wanted to post on something else, but, I guess this has to be a precursor to it.
All of us know of Calculated Fields in Siebel Business Components. I am sure they must have solved some very big problems for you at times, as they have for me. However, not all of us know that we can actually invoke Business Service scripts from within the Calculated Fields, rather than just calling some in built functions or playing around with the other fields in the BC. This functionality enhances the already huge functionality of the Calculated Fields in Siebel.
4
May
2009
Siebel – EAI Queue – a Critique’
I had introduced the Siebel EAI Queue and its usage in my last articles. Though Siebel EAI Queue is a very good Siebel feature, there are some serious shortcomings as well. An architect would, thus, need to critically evaluate all the pros and cons before deciding to implement the OOB EAI Queue or a custom solution in a Siebel EAI project.
First let’s look at all the areas where Siebel EAI Queues stand strong.
1) No customisation needed
This is an OOB fucntionality. So, no custom coding is necessary. The vanilla BS can directly be called from the WF to help operate the EAI Queues. Custom code comes with its own sets of problems – dedicated human resources, architecting, implementing, testing, debugging, performance, scalability, expandability, robustness.
1
May
2009
Siebel – ActivateField() split wide open
In Siebel, we generally tend to use the fields on the BC level in a number of ways, one of them being their use in Siebel scripts. The most common functions for operating on BC fields are GetFieldValue() and SetFieldValue() used for getting a value, or setting a value of the corresponding field in the BC. However, Siebel requires using ActivateField() before operating on any field of the BC.
Fields that are not active at runtime should not be used in script. Runtime errors, flawed logic and lost data may be the result of such a practice.
22
Apr
2009
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.
