GeeKs Blogging @ dotCOM » User Property

Siebel – changing Textbox height

Prachi Sharma — Mon, 18 May 2009 04:58:16 +0000

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.

Navigate to the Applet in Siebel Tools, where you need to show this textbox of height equal to 6 rows.
In the Object Explorer, select Controls.
Navigate to the Control which has the Textbox / Textarea.
In the corresponding columns, you will find a property called, “HTML Height”. Set this value as 100.
Compile into the Siebel SRF, and restart Siebel Web Client. You should now see the Textbox with a large height as desired.

Siebel seems to take this value in terms of pixels on the screen. 100 seemed to be reasonable in our case.

Similarly, if you want to change the width of the Textbox, there is another property corresponding to the Textarea control called, “HTML Width”. You can change the width of this textarea to as much as your requirements.

We tried doing this on the Form Applet and it worked.

Related posts:

Siebel – Number of rows displayed in List Applet Siebel Web Client by default shows only the first 7...

Siebel – DefaultFocus – User Property In Siebel Application, whenever you navigate to a screen, the...

Siebel – Custom Applet Title There is an Applet title on the top of the...

Siebel – About SRF Window – Remove data Okay. This is something those who like to toy with...

Siebel – Remove About SRF Window In my previous post, I had discussed as to how...

Siebel – DefaultFocus – User Property

Prachi Sharma — Sun, 17 May 2009 04:59:26 +0000

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.

In order to use this, simply navigate to the ‘Applets’ object manager in Siebel Tools. Navigate to ‘Applet User Prop’ under the ‘Applets’ Object Manager.

Do a NewRecord and set the following values:
Name : DefaultFocus
Value :

Here, is the name of the column where you want to set the Default focus.

Compile your changes into the Siebel SRF and run. You will now see that the default focus whenever you navigate to the screen, has been set on the required column in the Applet.

This will run for both Form and List Applets. But, somehow this does not run in High Interactivity mode! This works in Standard Interactivity mode only. I hope this article helps somebody someday.

Related posts:
Siebel – Custom Applet Title There is an Applet title on the top of the...

Siebel – Automatic User Logout Logging out a user automatically, when the user does not...

Siebel – Forcing User Logoff Hi all, Somebody recently asked me if there is a...

Siebel – HTML Code displayed in Error Message There was a requirement in our project to make Account...

Siebel – Showing red asterisk on a conditionally required field In Siebel vanilla Application, we see a red asterisk (...

Siebel – HTML Code displayed in Error Message

Madhvi Arora — Fri, 24 Apr 2009 03:45:13 +0000

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..

img src=”images/icon_req.gif” alt=”Code Validated” border=”0″ space=”0″ hspace=”0″>Account is a required field.

We always thought that required field message is displayed with the name of the field which is in the BC. But after getting this message, it made me think that this error message takes the reference of the caption for the field in the applet.

This is the expected Siebel behavior to show the full caption of the field that is set to require so if the caption is different than the field name the user will be notified about the field name they see through the user interface.
The workaround to our problem was to either use scripting or do some configuration.
Using scripting was not a good idea, so I used configuration and it worked.

I followed following configuration steps which are described below:
(Note: This is for the case for form applet which uses Grid Layout)

1. Remove caption from the control for the field which is needed to be required.
2. Create a new record in Control in that applet with HTML Type as Label with just the html in the caption to show the asterisk with the name.eg. img src=”images/icon_req.gif” alt=”Code Validated” border=”0″ space=”0″ hspace=”0″>Account.
3. Place this next to the label of the required field so the required field does not need the html in the caption property

Then when the error is displayed you will not need to worry about the html because it’s in a different control.

Related posts:
Siebel – Showing red asterisk on a conditionally required field In Siebel vanilla Application, we see a red asterisk (...

Siebel – Number of rows displayed in List Applet Siebel Web Client by default shows only the first 7...

Siebel – Make a field Required, conditionally There was a requirement in our project to make Account...

Siebel – Autosave Opportunity data – Sample Code This is a follow up post on my previous post,...

Siebel – Custom Applet Title There is an Applet title on the top of the...

Siebel – Showing red asterisk on a conditionally required field

Madhvi Arora — Thu, 23 Apr 2009 04:33:28 +0000

In Siebel vanilla Application, we see a red asterisk ( * ) in case the field is Required. However, this asterisk is not shown in case the field is made required conditionally through customization.

We had a similar requirement, to show the red asterisk against a field in the form applet, which was required conditionally. I have already discussed how to make the field read only conditionally in my previous post.

We implemented this by setting the caption of our field on the applet as:
img src=”images/icon_req.gif” alt=”Code Validated” border=”0″ space=”0″ hspace=”0″>Account”

The caption at the Control level in the applet accepts HTML coding for custom display. This worked. Now, we could see a red asterisk ( * ) against our field which was previously implemented conditionally required by using the BC field level User Property “Required”.

Related posts:
Siebel – Make a field Required, conditionally There was a requirement in our project to make Account...

Siebel – HTML Code displayed in Error Message There was a requirement in our project to make Account...

Siebel – Make MVG Field required Siebel supports the concept of Multi Valued Fields, or the...

Siebel – Make MVG Field required – II Hi friends, This is a follow-up post of the post...

Siebel – Custom Applet Title There is an Applet title on the top of the...

Siebel – Make a field Required, conditionally

Madhvi Arora — Wed, 22 Apr 2009 10:51:29 +0000

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.

So, we used an BC field level User Property, ‘Required’. We created an expression which conditionally evaluated to TRUE or FALSE as per our requirement, and we used this against the Required User Property.

Thus, we were able to set the field to required successfully. Though this solved our problem initially, it brought with itself another set of problems which I will discuss in the posts to come.

Related posts:
Siebel – Showing red asterisk on a conditionally required field In Siebel vanilla Application, we see a red asterisk (...

Siebel – Make MVG Field required Siebel supports the concept of Multi Valued Fields, or the...

Siebel – Make MVG Field required – II Hi friends, This is a follow-up post of the post...

Siebel – HTML Code displayed in Error Message There was a requirement in our project to make Account...

Siebel – Admin Mode Flag In my last project,we had a requirement of Admin Views,...

Siebel Assets List view – Performance issue / Cannot display records

Himanshu Bajpai — Tue, 14 Apr 2009 08:00:57 +0000

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.

Application will hang for some time and after that it will show an error message similar to the following -

“There were more rows returned than can be shown on the screen. Please ask the System Administrator for support.”

In a typical CRM software, Order Management cycle, we start from an opportunity, and proceed to Quote, Order and finally a billable Asset in that Order. Then Asset to Opportunity, and the cycle repeats itself.

Assets are end results and in all probability, Assets are in million of numbers.

The problem being discussed is that the user has to see All Assets or some cases At least All Asset headers.

Approach 1-

If User can restrict his search, we can go in for a PDQ that return lesser number of records (<10000). This will ensure at least the first load is quick. However, on Blank Query it will again return the same error described above.

Approach 2 (Preferred Approach) -

So, if the developer needs a permanent solution to this problem, he can follow the steps below to show millions of assets without any error-

Login Siebel Tools>

Query for Asset Mgmt – Asset List Applet Applet.

Go To Applet User prop>search for “Disable Buscomp Hierarchy”.If it is set to “FALSE”, make it “TRUE”. After compilation Assets screen will show millions of records without any error. Voila! Problem solved.

This property would be even more helpful for performance if used to show Asset Headers Only.

Please put in your comments. Feel free to add your solution, in case you have come across a different one.

Related posts:
Siebel Admin Mode Flag – II – Issue Log In the last post I described about Admin Mode Flag....

Siebel – Number of rows displayed in List Applet Siebel Web Client by default shows only the first 7...

Siebel – Looping multiple records – Update records Hi, We often come across a requirement where we need...

Login Failed in Dedicated Web Client : MVF Issue Recently I have met with the Problem in form of...

Siebel – Fetch Active view properties Hi, Working on a typical requirement recently, I came across...