Showing posts from November, 2012

Deploying Integration Object at Runtime (Siebel)

Feature:Starting with Siebel 8.1, Integration Objects can be deployed at runtime just like workflows to the runtime database. Modifications to the IO can be deployed to the server without having to recompile the changes to SRF, shutting down the server and then moving the changes.
Steps to follow:
1.Open a Dedicated connection to the server database(Works on local db too) 2.Go to the IO in the Object Manager 3.Select the IO that needs to be modified and deploy 4.Right Click on the IO and select “Deploy to Runtime Database”
5.Log into Siebel Web Client 6.Go to Site Map ->Administration – Web Services >Deploy Integration Object
7.The IO will now be available 8.In order to un-deploy the IO, go to Siebel Tools ->Integration Objects > Right Click on the IO and select “UnDeploy” 9.Clear the cache every time before deploying/un-deploying(Administration – Web Services > Inbound/Outbound Web Service > Clear Cache)
Note: 1.Undeploy the Older version before deploying a new one 2.This approa…

"SOUNDSLIKE" operator in siebel

Requirement:End users use different spellings when they write down the names of Contacts. In our case, it’s really difficult to find the duplicate Contacts that are created with different Spellings. For Example, Tracey can also be spelled as Tracy , Traecey, etc. 
Solution: In order to find the records that are duplicate, we can use SOUNDSLIKE operator in Siebel. Before creating a contact we can use the Soundslike operator to check whether the desired contact is already existing in the application or not and then we can continue further.
Below Screenshot depicts the usage:
Output generated after using the operator : Siebel maps the SOUNDSLIKE operator to the SOUNDEX function at the database level and the same can be viewed by performing a spool.

Drill down in siebel form applet

Requirement: Create a drill down in Service Request Detail Applet(Form Applet)This is a tweak and not a siebel provided functionality 
Steps to do(explained by an example):1. In Service Request Detail Applet(applet of your requirement) create new Drill down object Property ValueName: GotoSR Hyperlink Field: SR Number View: Service Request Detail View
2. Create new Control object on that Applet Property ValueName: SR Drill down Caption – String Override: Go To SR HTML Type: Link Field: SR Number
Method Invoke Drill Down 3. Remove the label for the SR Number field in the applet web layout. 4. Place the new configured control adjacent to the SR number field. 4. Compile and test
Notes• The hyperlink will show the value entered in the control Caption and not the field value • If there is no record returned by query, hyperlink is still active and drilling down on it results in error message "This operation is not allowed when there are no records displayed".