Release/Unrelease SmartScripts in batch
Jun/090
In the most recent release on the project I’m currently working on, the customer wanted to work with SmartScripts. Very soon we had over 40 SmartScripts.
The problem with SmartScripts however is that they all need to be released whenever they are created. And since the customer is working with 3 different languages, this means a lot of manual labour.
Therefore, I’ve come up with a simple but clever solution. I’ve added to extra buttons on the top applet called Unrelease All and Release All.

To (un)release all SmartScripts at once, the user simply has to query in the bottom applet for the correct language and click on the Unrelease All or Release all button. The script behind the buttons then performs the action for all SmartScripts for the specified language.
In the customer’s case, you have to perform this action 3 times (for languages ENU, NLD and FRA) in stead of around 100 times for each SmartScript individually.
New start
Jun/091
A new WordPress theme and a new hosting company. It seems that I’m ready for a new start with this blog.
You might have noticed that no new posts were put here for some time. The reason was that I was a bit too lazy to do so.
But now I’ve found somenew energy so this is a fresh start. The purpose is now not only to blog about Siebel but also a bit more about my personal life. Of course, the main topic will remain Siebel, but still, some personal blogpostswill spice up this blog.
So get ready and join me in this new Diary of a Siebel Consultant.
Dec/081
Wanted: Siebel developers who are using twitter.
I’ve using twitter for about a year now and most people I follow are Belgian people who are strongly linked to the web (web designers, web architects, students, …). Until now I haven’t found any Siebel developers in Belgium that are using twitter.
That’s why I’m writing this post. If you are a Siebel developer and you are using twitter, feel free to follow me or give me a link to your twitter-profile so I can follow you. I think twitter is a great and easy way to find a quick solution when facing small problems and I’m looking to expand my network with fellow Siebel developers.
So please feel free to visit my profile or leave a comment if you are using twitter yourself.
Debugging in another language
Sep/083
Today we were facing an issue in the French and Dutch version of our application. Strangely enough, the issue was not occurring in the English application.
Since I thought it was related to eScript, I wanted to debug the code.
So I opened the Options windows and entered the path to the config file for the Dutch application. For some reason, the application was using the srf file in the ENU folder in stead of the NLD folder.
At first I thought something was wrong with the config file but it seemed ok. Then I checked the options for debugging again but they were all filled in correctly.
Being confused about it, I asked a colleague for help and he found on Supportweb Metalink that I had to pass the parameter for the language in the argument field. Adding /L NLD finally fixed the issue and I could start debugging our Dutch application

JIRA
Feb/081
On my current project, we use JIRA to keep a track of all bugs found in the application. At first, it was a bit difficult using the tool – before we worked with an excel-file – but now it became a second nature. If I can fix my bugs on time, it will be a complete victory.
This is my list that has to be finished by tonight:
![]()
Looks possible, doesn’t it?
Importing/Exporting workflows
Feb/083
Today I ran into a very strange Siebel bug in Tools.
I modified a workflow on our development environment and because we’re in the last week of our UAT phase I wanted to deploy it immediately on the UAT server.
So I connected with Tools to UAT and after doing an export of the workflow from Dev, I tried to import it into UAT.
After selecting the project I wanted the workflow to add to, Siebel gave me the following error which seemed a bit strange:’Cannot perform UpdateRecord on the Business Component Repository WorkflowProcess (SBL-EAI-04421)’

After trying several things, I asked a more experience colleague for help. As it turned out, the solutions was very simple. There where already 11 versions of this workflow and for importing a workflow, this was to much.
So if you run into this error, first delete all obsolete versions of your workflow and retry importing the new workflow. It should work like a charm.

