siebel

An idle mind is Devil's workshop...an orphaned session is inefficient resource allocation... "SessionTimeout" is one of the parameters in the eapps.cfg that is more to do with competent usage rather performance. This specifies the time in seconds when the session times out in case of inactivity. The larger the value the longer it takes for the orphaned session to timeout. Orphaned sessions are undesirable beacuse they occupy AOM task slots preventing other users to use that slot. There are instances when session never times out despite setting this parameter. Following parameters should be kept in mind before setting SessionTimeout parameter. 1 - "Application Message Bar Update Interval" This parameter is used in Message Broadcasting feature. The value of this parameter should be set to greater than the SessionTimeout parameter. 2 - "Alarm Manager Load Frequency" The "Alarm Manager Load Frequency" system preference determines how frequently t

Statuary Warning: This is not for the old horses. My romantics with siebel goes on and so Siebel mysteries. Newbies better be careful while using "IS UPDATED" condition in the workflow policies. It can lead to undesirable/wrong results. Lets consider below problem statement. "Any service request which is not worked within 2 hours of assignment, i.e. Assigned status , should be escalated." The obvious solution which comes in mind is to configure workflow policy with duration and Owner Id update condition. Unfortunately it didn't work for me. The issue when using "IS UPDATED" criteria in combination with Workflow duration is that criteria is considered only at the time of the first update by the user. Until the configured policy duration has completed, all subsequent updates to the record are discarded by Workflow Policy Manager. As a result at any point of time only one record is available in "S_ESCL_STATE" table for this policy. At the end

Recently we encountered a scenario which involved certain validations on drilldown. The go to solution was to invoke DVM on drilldown method. Lets consider a basic example of SR list applet where we need to perform certain validations when user clicks on SR-Number. Following steps are required to achieve desirable. 1 - Create a DVM rule set with name "Test Orchestration". Add desired rules as per validation requirement. 2 - Create User Property on the SR business component with following values: Name: Named Method 1 Value:"SRDrill", "INVOKESVC", "Service Request", "Data Validation Manager", "Validate", "'Rule Set Name'", "'Test Orchestration'", "'Enable Log'", "'Y'", "'Object Id'", "[Id]" 3 - Navigate to SR list applet and edit server side script. Add following code in PreInvokeMethod event : if (MethodName == "Drilldown&q