Siebel – Symbolic Strings
Consider this a brief introductory tutorial on Symbolic Strings in Siebel. Symbolic Strings are from amongst the most commonly used entities in Siebel, especially in Siebel Multi lingual deployments.
They can greatly reduce the job of initializing, deploying, tracking, modifying all the plethora of error/warning messages that you may generally come across in a typical Siebel CRM application.
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 – 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.
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.
Siebel – Remove About SRF Window
In my previous post, I had discussed as to how we can control how we can control the data being displayed in the Siebel Client, About SRF window. You can read the article here.
One impromptu question came up from the audience, “What if I want to limit opening of the About SRF window itself in the first place?”. I said, “Nice question!”.
Try out the following steps to disable the About SRF window itself from Siebel Web Client.
Siebel – About SRF Window – Remove data
Okay. This is something those who like to toy with Siebel may find interesting. I will discuss today, how we can play with the Siebel ‘About SRF’ window when you go Help -> About SRF in Siebel Client Application.
I guess almost all the Siebel users would have seen or used the Siebel ‘About SRF’ window to know about the latest SRF that has been compiled, or other technical information for the application that they just logged into.
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.
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.
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.