Link love

12
Jun/09
2

I’m not sure if this blog has some loyal reader yet, but if you are one, or just passing by, and you are working wiht Siebel, this post is written for you.

Do you have a blog or website about Siebel? Do you want to share your knowledge with others? Just drop the link in the comments and I’ll put it in my blogroll. No questions asked.

The only thing I would like in return is a link on your blog/website to siebelconsultant.net.

VN:F [1.8.2_1042]
Rating: 4.0/5 (1 vote cast)
VN:F [1.8.2_1042]
Rating: 0 (from 0 votes)
Tagged as: , ,
408 views

RaiseError()

2
Oct/08
1

A while ago I discovered the function RaiseError() in Siebel. To be honest, a colleague said that I could use that function in stead of RaiseErrorText().

Since we are implementing a multi-lingual application, all error messages should be multi-lingual. So whenever we wanted to throw an error message in eScript, we used the following code combining RaiseErrorText and LookupMessage in order to throw the error in the correct language.

TheApplication().RaiseErrorText(TheApplication().LookupMessage(“User Defined Errors”, “X_DISPATCH_REQUIRED_FIELDS”));

As you can see, this requires a lot of typing and this was also the opinion of a colleague. He then suggested me to use the RaiseError function instead. This is actually the same, but you just have to pass the name of the error you want to throw as an argument.

TheApplication().RaiseError(“X_BARCODE_NOT_NUMERIC”);

Off course you have to create the error message first in Tools in Message Category -> User Defined Errors and not in User Defined Strings as I tried.

The RaiseError function saves you time on typing code, so be sure to use it next time you want to throw an error in you script when running a multi lingual application.

VN:F [1.8.2_1042]
Rating: 4.0/5 (2 votes cast)
VN:F [1.8.2_1042]
Rating: +1 (from 1 vote)