In Siebel vanilla there is an undocumented BS named Read CSV File.
This BS is very useful especially for testing. Using this BS you can read a file based on Integration Object and you can use it for unit testting purposes. Also i can be an alternative to load data into Siebel. You can find detail information about this BS below,
http://blogs.oracle.com/siebelessentials/2008/10/encounter_with_the_read_csv_fi.html
You can find basic information about How Regular expressions can be used in Siebel in below links,
http://siebeldev.blogspot.com/2009/04/regular-expression-validation.html
http://download.oracle.com/docs/cd/B40099_02/books/eScript/eScript_JSReference252.html
For the Non English character set support, RexExp pattern should be writed with Unicode characters.
You can get information about Unicode below link,
You can find a simple pattern about Turkish First Name validation below,
“^[\u0041-\u005A]{1}\u002E?[\u0041-\u005A|\u0061-\u007A|\u0130|\u0131|\u00D6|\u00F6|\u00DC|\u00FC|\u00C7|\u00E7|\u011E|\u011F|\u015E|\u015F]*$”
Pattern explanation:
First character should be Upper Case(\u0041-\u005A]{1})
Second character could be “.” (\u002E?)
Other characters can be anything in Turkish Alphabet([\u0041-\u005A|\u0061-\u007A|\u0130|\u0131|\u00D6|\u00F6|\u00DC|\u00FC|\u00C7|\u00E7|\u011E|\u011F|\u015E|\u015F])
Hi,
In theory, there is no difference between object and project compile in Siebel but in fact sometimes there is. I crashed a Siebel bug which is related object compile and i wasted lots of time to find the problem 
This is not very common, most of times object compile is working pretty good but in this case below, it doesn’t.
My suggestion is if you are compiling your changes via Object compile and they are not working, please compile your changes via project compile(compile all projects you change) and test it again. It can be related object compile problem.
Regards.
Hi,
“What happens if the Applet visibility Type Is Null” is very common question which is has an answer in Bookshelf. I am just copied it below,
Visibility Settings
A view not set up with visibility settings (the properties Visibility Applet and Visibility Applet Type are
blank) means the following:
When navigating from another view to this view without visibility settings using the Show drop-down
list, the queries context and record focus are kept from the previous view, assuming that the same
business components and search specifications are relevant.
However, when navigating to a view without visibility settings using the Site Map or the Screen Tabs,
the view behaves as if the most restrictive visibility would apply to this view. (Normally this means
Personal or Sales Rep visibility, depending on the corresponding visibility settings of the business
component of the view’s Thread Applet property.)
Resource: Siebel 7.8 Bookshelf Object Type Reference Document, Page 306.
Regards.
Let’s thing you have a requirement that if Login name is DUMMY, show only records in which name field equal to “3Com” otherwise show all the records which means you don’t want to make a filtering if Login Name is not equal to DUMMY.
You can not use “IIf” function without else part like below becasue of it is giving syntax error.
IIf((LoginName() = “DUMMY”), [Name]=”3Com”)
But you can not use “IIf” function like this below which is giving syntax error.
Instead of this you can do a trick this using “Id” column which is always not null and active.
IIf((LoginName() = “DUMMY”), [Name]=”3Com”,[Id] IS NOT NULL)
Sure, it has some performance impact but i can not find better way 
What about you?
Merhaba,
Cumartesi günü akrabalar arasındaki bir tören ile nişanlandım. Vurulacağım tarih ise Ağustos ya da Ekim olacak gibi gözüküyor. Kesinleştiğinde sizlere haber veriyor olacağım.
Sağlıcakla.
http://en.wikipedia.org/wiki/FPGA adresindeki İngilizce makelenin Türkçeye çevirdiğim hali için tıklayınız. İyi çevrilmediğini düşünüyorsanız bir de siz çevirin de görelim
FPGA konusunda hazırlamış olduğum sunum için tıklayınız.
Not : Sunum makeledeki konu başlıklarına ve içeriklerine sadık kalınarak hazırlandı. Bu nedenle içerik her zaman başlık ile ilişkili olamayabiliyor, bu durum makaleden kaynaklanıyor.
Outer join kullanırken dikkat edilmesi gereken basit ancak fazla bilinmediğini düşündüğüm bir nokta var.
Bir SELECT cümlesinde outer join kullanıldığında, kullanılan tablo üzerinde başka where conditionları varsa sorgu outer join yokmuş gibi çalışıyor.
Bu nedenle aynı tablo üzerindeki kolonlarla ilgili diğer where conditionlarına da outer join(+) eklenmesi gerekiyor.
Aşağıdaki script incelenirse konu daha iyi anlaşılacaktır diye düşünüyorum.
DROP TABLE OUTER_DENEME
/
DROP TABLE OUTER_DENEME2
/
CREATE TABLE OUTER_DENEME(NO NUMBER,AD VARCHAR2(10))
/
CREATE TABLE OUTER_DENEME2(NO NUMBER,AD VARCHAR2(10))
/
BEGIN
INSERT INTO OUTER_DENEME VALUES (1,’ERSIN’);
INSERT INTO OUTER_DENEME VALUES (2,’SELAMİ’);
INSERT INTO OUTER_DENEME VALUES (3,’VELİ’);
INSERT INTO OUTER_DENEME2 VALUES (1,’ERSIN’);
INSERT INTO OUTER_DENEME2 VALUES (2,’SELAMİ’);
COMMIT;
END;
/
SELECT * FROM OUTER_DENEME A, OUTER_DENEME2 B
WHERE A.NO=B.NO (+)
/
SELECT * FROM OUTER_DENEME A, OUTER_DENEME2 B
WHERE A.NO=B.NO (+)
AND B.AD IS NOT NULL
/
SELECT * FROM OUTER_DENEME A, OUTER_DENEME2 B
WHERE A.NO=B.NO (+)
AND B.AD (+) IS NOT NULL
/
Bir çok programlama dili ile ilgili kullanım örneği bulabileceğiniz güzel bir site. Çok fazla google reklamı var ama siz onlara aldırış etmeyin
