GeeKs Blogging @ dotCOM

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.

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:

1. Siebel – Number of rows displayed in List Applet Siebel Web Client by default shows only the first 7...
2. Siebel – DefaultFocus – User Property In Siebel Application, whenever you navigate to a screen, the...
3. Siebel – Custom Applet Title There is an Applet title on the top of the...
4. Siebel – About SRF Window – Remove data Okay. This is something those who like to toy with...
5. Siebel – EAI Queue Okay, what are you thinking about? Is it Middlewares in...
6. Siebel- Close Browser window when logging off In case of standard interactivity applications like eSales , eService,...
7. Siebel – Remove About SRF Window In my previous post, I had discussed as to how...