function trim(source)
{
var beginOfString = 0;
var endOfString = 0;

for(var index = 0; index < source.length; index++)
{
if(source.charAt(index) != " ")
if(beginOfString == 0)
beginOfString = index;
else
endOfString = index;
}

return(source.substring(beginOfString, endOfString + 1));
}

At first, it looked like the code did what it had to do, remove trailing spaces. But then I noticed that when there are no leading spaces, the code also removes the first letter in the string. Since this is unacceptable, I tried to wrote my own code and it turned out to be very simple.

My code looks like this:

function trim(source)
{
while(source.charAt(0) == ” “)
{
source = source.substring(1);
}
return(source);
}

Just a few lines of code but it does the work without removing letters if they are not spaces. Feel free to use the code whenever you need it.

When the users chooses ‘Export’ from the menu and saves the file to the harddrive, the hourglass symbol doesn’t change back to the mouse pointer. Strangely enough this only happens when doing a save and not when you open the csv file.

The solution to this problem is very simple. To change the hourglass back to the mousepointer just use the combination ctrl+8 or ctrl+shift+8 (use the 8 on the alphanumeric part of the keyboard, not on the numeric part).

After opening an SR on Support Web, we where told that our version of Acrobat Reader is not supported by Siebel. We are using version 7.0.1 but Siebel is only supporint version 6.0.1. Although Acrobat recently launched version 8 of there PDF read software, Siebel still supports version 6.

When asking if they know when Acrobat Reader 7.0.1 will be supported, the support guy respond to me that he couldn’t tell and that even Siebel 8 is only supporting version 6.

So if you are facing a simular problem, you best downgrade your Acrobat Reader to version 6.0 (which can be found here) or try the workaround solution. Maybe – with a lot of luck – printing reports might work with version 8, but that is still something I need to test.

I had to change the spelling of a word in the entire application. Since we used symbolic strings for this, I thought it was enough to change the symbolic string and everywhere in the application the correct spelling would be applied.

But no, apparently, you have to compile every object where you use the symbolic string. For me, this comes as a chock. I thought the purpose of symbolic strings was to simplify the use of titles and such in Siebel. But I guess I was wrong.

A look at the logfile learned me that those attachments could not be found. After a closer look, it seemed that all the attachment had special characters in the filename. With special characters I mean characters like é, è, à % and so on.

After comparing some of the attachments I noticed that Siebel converts these characters in other characters. So far I made this list of converts. The list is not yet complete but maybe it can be helpful:

ô –> (
é –> T
è –> F
ï –> n
û –> v
à –> a
ê –> O
î –> á
² –> ¦
ö –> ÷
ç –> t
% –> blank
€ –> Ç
’ –> Æ
« –> ½
» — > +