17
Aug
2009
15
Aug
2009
25
Jun
2009
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).
22
Jun
2009
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.
20
Jun
2009
Siebel – Different MiniButton types
You must have come across the so many different types of minibuttons that you can place on your applets. Have you ever gotten confused as to which minibutton to choose for which particular applet?
It’s so nice to be back! Hello to everybody.
I was working on a configuration requirement recently when I needed to add a minibutton on an applet. I noticed that I had many different minibuttons available, and it seemed that all of them perform the same task. I consulted my senior who asked me to just use MinibuttonEdit kind of button. I digged a little deep into it, and, I am sharing here my findings with everybody.
18
May
2009
Siebel – changing Textbox height
There are a number of HTML controls available in Siebel. One such control is the Textbox, or the Textarea. This is generally displayed as a big box on the screen having a height spanning multiple rows.
There was a requirement from my client to modify the number of rows being displayes on the Textbox. He wanted this textarea on the Applet to be 6 rows tall, such that most of the text is directly visible to the Customer Support guy using this view. I will discuss the solution that we implemented to this problem here.
17
May
2009
Siebel – DefaultFocus – User Property
In Siebel Application, whenever you navigate to a screen, the default focus of the cursor is set to the first editable field. You may have a requirement to instead set the default focus to a more commonly used field. So, whenever you navigate to that screen, the curson focus will be on the client required field first up, and the user will have to navigate to reach some other field in the applet.
This can be done easily by using a Siebel vanilla Applet level User Property called, DefaultFocus.
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:
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.
