PickList In Siebel

-

 


















Comments

Post a Comment

Popular posts from this blog

Siebel Administration Explored

-
  SQL Query to List All Active RCR jobs in Siebel As with any Siebel implementation, one of the day-to-day monitoring tasks for an Administrator are the Siebel components. And the RCR jobs running on the servers tend to be an integral part of the Workflow Process Manager and Workflow Process Batch Manager component requests. So, tracking them becomes useful in situations where there are component issues or some critical job failure. This SQL can be a reference to list all the RCR jobs by their Execution Server name which is very helpful if you are not assigning any Server Name to the job upon submitting. SELECT     PAR_REQ_ID "Job Id",     rpt_interval||' '||rpt_uom "Frequency",     STATUS,     ACTL_START_DT,     EXEC_SRVR_NAME FROM     SIEBEL.S_SRM_REQUEST WHERE     REQ_TYPE_CD = 'RPT_INSTANCE'     AND STATUS = 'ACTIVE'     AND PAR_REQ_ID in ( select     par.row_...
Read more

Siebel Web Service session management

-
  Siebel Web Service session management Using sessions can improve the performance of the web service calls as the session is kept open for subsequent requests.There is no need to login and logoff for each request. There are 4 different session types: None : A new session is opened for each request and then closed after a response is sent out. This is the default. Stateless : A new session is opened for an initial request and the session remains open for subsequent requests. Relogin occurs automatically (transparent to the user) if the session is closed. Stateful : A new, dedicated session is opened for an initial request and the session remains open for subsequent requests. Relogin does not occur automatically if the session is closed. To enable the session management you need to change the following: 1) Add "&WSSOAP=1" to the URL and remove the "UserName" and "Password" arguments from it as well as shown below: Original URL: http:/...
Read more

Siebel escripting Best Practice recommendation

-
  Why escripting is not recommended   1.) As Scripting is more error prone approach and costlier approach while dealing with Solution. 2.) It takes high CPU and RAM utilization. 3.) It is compiled at runtime which makes difficult to maintain the server whereas the existing srf are precompiled and executed which makes it fast. what are alternative for not going to scripting and build it . They are : 1.) Audit Trail 2.) DVM , 3.) State Model 4.) Assignment Manager 5.)Task UI 6.) Personalization 7.) BC user Property, Calculated Field and Validation Message on BC 8.) Use built WF's   Best Practices for Scripting are: 1.) Use exception handling 2.) Garbage nullification 3.) Quality Assurance and Proper Unit Integration Testing 4.) Headers and well commented code
Read more