Anoop a reader of my blog asked me a question few days ago. It is an interesting question.
Question:
In Siebel Applet suppose we have a Limitation to show Only 40 Field (Control) and we want to show some more columns.how to configure in this scenario?
I had an idea how to do it but I hadn’t actually worked on it. After this question I decided to find out the answer and the result is the post below.
Solution:
As we all know that Siebel uses Siebel Web Template (SWT) files to render UI both our List Applet and Form Applet are based on Web templates. So, Answer in short is We can achieve our requirement by changing SWT files. Some other question that we have to answer before this question becomes complete are.
- Which SWT File?
- What to Change in that SWT File?
Complete Solution:
Follow the steps given below to find out which SWT file you have to change
- Open Siebel Tools
- Query for the Applet in which you want to add more columns
- Click on Applet Web Template icon in Object Explorer as show in picture below
- Select the Mode for which you want to add column
- Note down Value in Web Template Field in Applet Web template list applet
- Go to Web Template object in Object Explorer
(If you don’t see Web Template Object the follow the instruction in this post to add it to list) - Query with the value you had noted down in step 5
- Go to Web Template File section and note down the Value in Filename field in Web Template file Applet. This is the file that you need to edit.
- Go to Siebel installation\Siebel tools\WEBTEMPL folder and search for this file
- Open this file in any Text editor and search for code that is like code given below. (It might be a bit different than depending on which SWT file you are trying to edit)
<swe:for-each startValue="501" count="40" iteratorName="currentId">
<swe:control id="swe:currentId">
<td align="swe:this.TextAlignment" class="Row"><swe:this property="FormattedHtml" hintText="Field" hintMapType="ListItem"/></td>
</swe:control>
</swe:for-each> - Increment count attribute to with the number you columns you want to add. For example if you want to add 2 column then code after editing will look like
<swe:for-each startValue="501" count="42" iteratorName="currentId">
<swe:control id="swe:currentId">
<td align="swe:this.TextAlignment" class="Row"><swe:this property="FormattedHtml" hintText="Field" hintMapType="ListItem"/></td>
</swe:control>
</swe:for-each>
If you don’t find the above given code in the SWT file then you need to look for included files in that SWT. Look for a line like
<swe:include file="CCListBody.swt"/>
open the included SWT file and look for the above given code. You will need to move this SWT file to web client\ WEBTEMPL folder before you can see the changes in the application.
Let me know your feedback.

(9 votes, average: 4.67 out of 5)
11 Comments at "Siebel List Applet columns and SWT Files"
Hi Neel,
I have one suggestion and one question this time.
Suggestion :- If we will change the original swt file then changes will have a effect all over the application where same template is used. so good approach is to copy the same swt file and rename it and make the changes on that file and use that one for the requirement.
Question : The Question is from where can we know the meaning of this swe tags as in this case it seems little easy to change the value of count from 40 to 42.
If you can provide the meaning of this swe tags it will be great.
Once again thanks for such a good post
Hi Arnol Tandon,
all tags can be found in Bookshelf for Oracle’s Siebel Business Applications, book Siebel Developer’s Reference, chapter 5.
good one! I dont know much about configuration, but the post it good…. It can prove to be very useful at times
Thank
Neel for your Prompt reply.
and explanation is very clear and easy to understand.
Hi Neel,
I’m working on a form applet which is using “Applet Form Grid Layout” web template(Template file name:CCAppletFormGridLayout.swt).
I opend this in notepad, but unable to find the “swe:for-each startValue=”501″ count=”40″ iteratorName…….attribute.
i also checked the inlcuded swt files but still not getting the count value statement.
can u please help me on this.?
Hello Vivek,
Your applet is form type so there is different web template as in mr. neel’s article. You already have its name and you have already “drilled down” into other included files. So there is main CCAppletFormGridLayout.swt, inside is included file CCFormButtonsTop.swt and finally file CCButtons.swt. Just open it and examine rows like ““. These can be used for your custom buttons, controls, etc.
But I am not sure about using so many controls on one applet, maybe redesign would help more.
btw. sorry that I am not Neel.
hmm, sorry for empty parenthesis, it just don’t display correctly. There are tags starting with “swe:control” in that file.
Hi,
I believe even after changing the Web template and getting the placeholders in, we cant map more than 40 fields on the applet . Any such change has to go through siebel expert services.
Anyways, This is my understanding..To help myself I would like to know if anyone has ever mapped more than 40 fields ever on a List applet..?
NS
I believe that can be done.. I haven’t done this personally but that has been done in my project… Will try to get the swt file in which the change was made.
I opened the CCListBody SWT file mentioned in Post and it already has 80 columns as there are two loops for controls.. I believe that is because I am working on Siebel Vertical…
But will try personally now and update here
Ok,
I couldn’t resist replying to this after reading some of the stuff in this blog.
Firstly, It is not recommended to exceed the limitations of the list applet web template. Seriously if you need to expose 40+ columns on a list applet, there is something wrong in the solution design. The performance implications on doing this are very concerning!
I have been doing Siebel for over 8 years and I have never seen a requirement to expose that number of fields. The applet would extend well beyond the screen resolution resulting in poor look and feel for the users.
You should always balance the needs of the business against performance and look and feel. This is stated in Siebel best practice
Keith
I think it is not necessary ,but it is true to realize your idea.
I hope we can talk about it.
Comment Now!