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 – HTML Code displayed in Error Message
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..
Siebel – Showing red asterisk on a conditionally required field
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.
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.
Siebel Assets List view – Performance issue / Cannot display records
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.